From: Mark Lillibridge <mdl@alum.mit.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 13306@debbugs.gnu.org
Subject: bug#13306: clarification
Date: Sat, 29 Dec 2012 22:23:06 -0800 [thread overview]
Message-ID: <87bodcvz1x.fsf@foil.strangled.net> (raw)
In-Reply-To: <83wqw0jg5p.fsf@gnu.org> (message from Eli Zaretskii on Sun, 30 Dec 2012 06:52:02 +0200)
Eli Zaretskii <eliz@gnu.org> writes:
> > From: Mark Lillibridge <mdl@alum.mit.edu>
> > Date: Sat, 29 Dec 2012 15:02:36 -0800
> >
> >
> > In case it wasn't clear from the last message, occurs does not work
> > sanely with Rmail buffers currently even in version 24.2. It takes you
> > to the occurrence point but there is no way to narrow the buffer so you
> > can do things like forward the found message.
> >
> > Perhaps a way to narrow a widened Rmail buffer around point would be
> > a useful independent function. I'm wondering if such a function called
> > from the right occurs mode hook (assuming it exists) would suffice to
> > provide the functionality I'm asking for here.
> >
> > - Mark
> > PS, note that both grep and the proposed occurs search the raw mbox file
> > not the results of decoding the messages; if someone wanted to go for
> > extra awesomeness, they might try and make an special Rmail search
> > command that produces an occurs buffer but only searches the decoded
> > messages (e.g., ignore nontext parts, work on base 64/printable
> > representations correctly). This would be substantially slower, but
> > would avoid a lot of false positives.
>
> Mairix solves all this, since the results of the search are
> _messages_, not just lines of text, and these results are presented to
> Rmail that decodes and displays them as usual. Try it.
I already use Mairix; I want to use occurs on its results in order
to see the results in context. Presumably someone else agrees since
they implemented this functionality for the result of grep. Also, I
don't know a easy way to restrict Mairix's search to one Rmail file.
- Mark
next prev parent reply other threads:[~2012-12-30 6:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-29 22:43 bug#13306: 24.2; [WishList] rmail-next-error-move functionality for occurs mode Mark Lillibridge
2012-12-29 23:02 ` bug#13306: clarification Mark Lillibridge
2012-12-30 4:52 ` Eli Zaretskii
2012-12-30 6:23 ` Mark Lillibridge [this message]
2012-12-30 4:50 ` bug#13306: 24.2; [WishList] rmail-next-error-move functionality for occurs mode Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bodcvz1x.fsf@foil.strangled.net \
--to=mdl@alum.mit.edu \
--cc=13306@debbugs.gnu.org \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).