Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: eyal.oren@deri.org (Eyal Oren)
Subject: [sup-talk] patch to search in buffer
Date: Thu, 11 Oct 2007 17:58:01 +0200	[thread overview]
Message-ID: <1192117720-sup-9850@timmy> (raw)

Hi,

Find attached a small patch to enable simple text search in a scroll-buffer.  
This means you can search (and jump) to a simple text or regular expression help 
screens, inbox list, or thread view. It's something that I, as a mutt user, 
missed in sup. I've bound the buffer search to '#' since '/' is already used for 
general search: please change to something more appropriate if you can think of 
it.

As this is my first contribution to sup, please tell me whatever I've done 
wrong. I wasn't sure where to put this behaviour (I put it in scroll-mode.rb) 
and some stuff needs fixing:
- it doesn't open text found in closed threads (patinas),
- it doesn't scroll to email text below the current page (I'm using jump-to-line 
  but it doesn't seem to work),
- it doesn't have an easy way of doing a repeated search (I know how to do it, 
  but I couldn't find how to tell ncurses that hitting the search button again 
without input should do a repeated search; alternatively, one could register a 
new keymap for a repeated search but it seemed like overkill to me).

I'm open to suggestions for improvement and for fixing the outstanding issues.

 -eyal
-------------- next part --------------
A non-text attachment was scrubbed...
Name: search-in-buffer.diff
Type: application/octet-stream
Size: 1465 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20071011/26215015/attachment.obj 


                 reply	other threads:[~2007-10-11 15:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1192117720-sup-9850@timmy \
    --to=eyal.oren@deri.org \
    /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