From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: newsgroup variables
Date: Wed, 26 Apr 2000 22:09:03 +0200 [thread overview]
Message-ID: <200004262009.WAA31528@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Shenghuo ZHU's message of "26 Apr 2000 13:24:21 -0400"
Shenghuo ZHU <zsh@cs.rochester.edu> writes:
> I think the mechanism of message-clone-locals is too aggressive.
_I_ think it isn't aggressive enough :-) But OTOH, I can't remember a
case where I was bit by this, so maybe I shouldn't be talking too
loudly.
I think your approach of having a list of variables to copy is a Good
Thing; this way people can control exactly what variables are copied.
But we should think about the interface for naive users. Suppose
somebody sets a variable local to a group via `G c'. Then that person
will surely expect this change to `just work', even if the variable is
actually used in the article buffer, say.
(Just to take an example -- what about fill-column? Presumably, `W w'
and `W Q' in summary mode take into account that variable (I haven't
checked), but the variable is used in the article buffer. Surely,
people will be surprised when they frob fill-column from the group
parameters and nothing changes.)
What can be done about this? Would it be enough to document this in
the buffer that appears after `G c'?
kai
--
Beware of flying birch trees.
prev parent reply other threads:[~2000-04-26 20:09 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
2000-04-26 20:09 ` Kai Großjohann [this message]
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=200004262009.WAA31528@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).