Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [PATCH] fixed crasher when refining search and updated keybinding
Date: Sat, 02 Feb 2008 18:35:28 -0800	[thread overview]
Message-ID: <1202006046-sup-3057@south> (raw)
In-Reply-To: <1201453197-sup-1113@tangerine.lanl.gov>

Reformatted excerpts from John Bent's message of 2008-01-27:
> Refine search is very nice.  Something else which might be nice would
> be a persistent search history which could be scrolled through with
> the up and down arrow keys.  That feature would then include refine
> search.

There is a non-persistent (but contextually-aware!) search history
accessible via up and down keys now. Persisting that to disk wouldn't be
very hard at all.

-- 
William <wmorgan-sup at masanjin.net>


  reply	other threads:[~2008-02-03  2:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-26  5:32 Christopher Warrington
2008-01-27 17:01 ` John Bent
2008-02-03  2:35   ` William Morgan [this message]
2008-02-03  2:34 ` William Morgan
2008-02-03  3:49   ` [sup-talk] [PATCH] fixed crasher when refining search Christopher Warrington
2008-02-03  3:49   ` [sup-talk] [PATCH] tweaked Refine Search keybinding Christopher Warrington
2008-02-03  5:09     ` William Morgan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1202006046-sup-3057@south \
    --to=wmorgan-sup@masanjin.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox