Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: eyal.oren@deri.org (Eyal Oren)
Subject: [sup-talk] searching current buffer
Date: Mon, 05 Nov 2007 21:37:07 +0100	[thread overview]
Message-ID: <1194294948-sup-4269@timmy> (raw)
In-Reply-To: <1194287462-sup-9734@south>

Excerpts from William Morgan's message of Mon Nov 05 19:37:17 +0100 2007:
> Excerpts from Ian Taylor's message of Mon Nov 05 10:26:24 -0800 2007:
> > I find myself wanting to search emails and the current buffer all the
> > time. Is there a way to do this?
> 
> Definitely on the near-term TODO. There was a patch to do this in a
> limited way a few weeks back from Eyal Oren. I'm not sure if he's
> planning on further work or not. Doing it "right" is a little
> complicated.
I went back to mutt for a couple of weeks, but couldn't resist. So I'm back at 
sup again now, and I might continue my very simple first attempts in the near 
future with the tips you gave me.

 -eyal


  reply	other threads:[~2007-11-05 20:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-05 18:26 Ian Taylor
2007-11-05 18:37 ` William Morgan
2007-11-05 20:37   ` Eyal Oren [this message]
2007-11-06  0:24     ` 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=1194294948-sup-4269@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