From: jhbrown@ai.mit.edu (Jeremy H. Brown)
Cc: ding@gnus.org
Subject: Re: finding the article buffer when splitting
Date: 15 Sep 2002 14:21:02 -0400 [thread overview]
Message-ID: <uv6r8fvm7w1.fsf@suspiria.ai.mit.edu> (raw)
In-Reply-To: <873csdrhhi.fsf_-_@emacswiki.org>
Alex Schroeder <alex@emacswiki.org> writes:
> jhbrown@ai.mit.edu (Jeremy H. Brown) writes:
>
> > (defadvice nnmail-article-group (around name-article-buffer (&rest args))
> > "name the article buffer for use in fancy splits"
> > (let ((the-article-buffer (current-buffer)))
> > ad-do-it))
> >
> > (ad-activate-regexp "name-article-buffer")
>
> Is anything like that going to be in Gnus? This seems to be really
> easy to implement. Otherwise, we might consider adding the following
> macro:
>
[snip]
Having thought about this more, I think what we really want is not a
variable gnus-the-article-buffer, but a function
(gnus-current-article-buffer) which returns a buffer containing the
current article. We want a function because if you're using the imap
backend, normal splitting functions don't download the whole article,
just the headers; this function can download the article body if
necessary, and otherwise just immediately return the buffer with the
body in it.
Jeremy
next prev parent reply other threads:[~2002-09-15 18:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 12:01 Splitting on mail contents? (using spam-stat.el) Oystein Viggen
2002-09-04 14:00 ` Kai Großjohann
2002-09-04 14:16 ` Oystein Viggen
2002-09-04 14:56 ` Kai Großjohann
2002-09-04 15:16 ` Oystein Viggen
2002-09-04 15:23 ` Jeremy H. Brown
2002-09-04 17:00 ` Oystein Viggen
2002-09-13 16:18 ` finding the article buffer when splitting Alex Schroeder
2002-09-13 23:56 ` Oystein Viggen
2002-09-14 1:18 ` Alex Schroeder
2002-09-14 10:01 ` Oystein Viggen
2002-09-15 18:21 ` Jeremy H. Brown [this message]
2002-09-23 14:11 ` Alex Schroeder
2002-09-23 18:49 ` Oystein Viggen
2002-09-06 15:55 ` Splitting on mail contents? (using spam-stat.el) Alex Schroeder
2002-09-07 12:30 ` Alex Schroeder
2002-09-07 17:17 ` Simon Josefsson
2002-09-07 19:05 ` Kai Großjohann
2002-09-07 19:05 ` Kai Großjohann
2002-09-12 16:07 ` Paul Jarc
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=uv6r8fvm7w1.fsf@suspiria.ai.mit.edu \
--to=jhbrown@ai.mit.edu \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).