Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Splitting on mail contents?  (using spam-stat.el)
Date: Sat, 07 Sep 2002 21:05:23 +0200	[thread overview]
Message-ID: <vafofb9ei30.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <ilu1y8567ow.fsf@latte.josefsson.org> (Simon Josefsson's message of "Sat, 07 Sep 2002 19:17:03 +0200")

Simon Josefsson <jas@extundo.com> writes:

> Yes.  The buffer name should probably be stored in a variable.  Only
> problem would be that people are already using the two hard coded
> buffer names... having two variables and keeping the two buffer names
> seems like a possibility but perhaps it is not that important?  Having
> one buffer name would be better.

The variable could be updated to contain the right value at the right
times...

kai
-- 
A large number of young women don't trust men with beards.  (BFBS Radio)



  reply	other threads:[~2002-09-07 19:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-04 12:01 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
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 [this message]
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=vafofb9ei30.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --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).