Gnus development mailing list
 help / color / mirror / Atom feed
From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: newsgroup variables
Date: 26 Apr 2000 13:24:21 -0400	[thread overview]
Message-ID: <2nwvlkixmi.fsf@tiger.jia.vnet> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Wed, 26 Apr 2000 17:58:43 +0200"

>>>>> "KG" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:

KG> Shenghuo ZHU <zsh@cs.rochester.edu> writes:
>> Is it helpful to provide a simple mechanism to do this? I mean, what
>> you need to do is just (push 'the-variable gnus-newsgroup-variables).
>> You need not care which buffer it should be copied to.

KG> What you're proposing sounds way cool.  I think it could also
KG> replace message-clone-locals, the old mechanism (for copying
KG> variables from the summary buffer to a message buffer, I think).

I think the mechanism of message-clone-locals is too aggressive. At
least I found a bug because of message-clone-locals. I need a list of
variables that are used in message buffer, so that they can be
explicitly listed in the gnus-newsgroup-variables.

I also think whether those variables should be cloned. If only one
copy is kept in summary buffer, you can not get those value after
exiting the summary buffer. Sometimes, messages are sent after user
exits the current summary buffer. If this were a problem, we would
have got a big trouble to send emails from nndraft:drafts, where those
variables are not kept at all.

-- 
Shenghuo



  reply	other threads:[~2000-04-26 17:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-24 14:30 Shenghuo ZHU
2000-04-24 16:24 ` Kai Großjohann
2000-04-24 17:04   ` Shenghuo ZHU
2000-04-24 18:44     ` Kai Großjohann
2000-04-25 13:22     ` Per Abrahamsen
2000-04-26 12:31       ` Janne Rinta-Manty
2000-04-26 12:42         ` Kai Großjohann
2000-04-26 13:39           ` Shenghuo ZHU
2000-04-26 15:58             ` Kai Großjohann
2000-04-26 17:24               ` Shenghuo ZHU [this message]
2000-04-26 20:09                 ` Kai Großjohann

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=2nwvlkixmi.fsf@tiger.jia.vnet \
    --to=zsh@cs.rochester.edu \
    /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).