Gnus development mailing list
 help / color / mirror / Atom feed
From: Sean Neakums <sneakums@zork.net>
Subject: Re: setting message-use-mail-followup-to for some groups only
Date: Thu, 15 Nov 2001 16:48:10 +0000	[thread overview]
Message-ID: <6uwv0sj7zp.fsf@zork.zork.net> (raw)
In-Reply-To: <vafpu6kc7kk.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Thu, 15 Nov 2001 17:39:07 +0100")

begin  Kai Grossjohann quotation:

> Sean Neakums <bastard@zork.net> writes:
>> It seems like it should, but it doesn't.  Or else I'm setting it
>> incorrectly.  What I did was add "(message-use-followup-to 'use)" to
>> the group parameters, and set gnus-newsgroup-variables as follows:
>> 
>> (setq gnus-newsgroup-variables '(message-use-followup-to))
>> 
>> In the summary buffer, message-use-followup-to has the local value
>> `use', but when I hit `f', Mail-Followup-To is not honoured, and the
>> message-use-followup-to variable is nil in the followup buffer.
> 
> Maybe Gnus has a bug?

As it turns out, the bug was internal to Neakums.  (See my
self-followup).

However, gnus-newsgroup-variables could probably do with having a
documentation string.  Some thing along the lines of:

  gnus-newsgroup-variables: A list of summary-buffer-local variables
  that should be made global while the summary buffer exists.  This
  variable can be used to set variables in the group parameters while
  still allowing them to affect operations done in other buffers.

Probably needs better wording, but I think that's the gist of it.

-- 
 /////////////////  |                  | The spark of a pin
<sneakums@zork.net> |  (require 'gnu)  | dropping, falling feather-like.
 \\\\\\\\\\\\\\\\\  |                  | There is too much noise.



  reply	other threads:[~2001-11-15 16:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-15 14:08 Sean Neakums
2001-11-15 15:21 ` Kai Großjohann
2001-11-15 16:03   ` Sean Neakums
2001-11-15 16:08     ` Paul Jarc
2001-11-15 16:20       ` Sean Neakums
2001-11-15 16:31         ` Sean Neakums
2001-11-15 16:39     ` Kai Großjohann
2001-11-15 16:48       ` Sean Neakums [this message]
2001-11-15 19:10         ` ShengHuo ZHU
2001-11-16  8:15         ` Kai Großjohann
2001-11-15 19:47 ` Matt Armstrong
2001-11-16  8:36   ` Sean Neakums
2001-11-16 16:05     ` Matt Armstrong
2001-11-16 18:09       ` Josh Huber
2001-11-16 20:20         ` Paul Jarc
2001-11-16 20:45           ` Josh Huber
2001-11-16 21:26           ` Matt Armstrong
2001-11-16 21:33             ` Paul Jarc
2001-11-16 23:56               ` Matt Armstrong
2001-11-17  1:20                 ` 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=6uwv0sj7zp.fsf@zork.zork.net \
    --to=sneakums@zork.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;
as well as URLs for NNTP newsgroup(s).