From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] searching current buffer
Date: Mon, 05 Nov 2007 16:24:32 -0800 [thread overview]
Message-ID: <1194308588-sup-4298@south> (raw)
In-Reply-To: <1194294948-sup-4269@timmy>
Excerpts from Eyal Oren's message of Mon Nov 05 12:37:07 -0800 2007:
> 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.
Actually I got so excited by your patch that I started working on it. I
might be able to check something in today or tomorrow! Just a few
remaining tweaks. Stay tuned...
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2007-11-06 0:24 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
2007-11-06 0:24 ` William Morgan [this message]
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=1194308588-sup-4298@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