Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: on Good Net-Keeping Seal
Date: 22 Apr 1996 02:48:17 +0200	[thread overview]
Message-ID: <x6d951hyni.fsf@eyesore.no> (raw)
In-Reply-To: <199604112212.AAA00488@bombur2.uio.no>

Hallvard B Furuseth <h.b.furuseth@usit.uio.no> writes:

> - Strive for a distinction between between "novice" and "expert" config
>   variables.  It should be difficult or impossible to diddle a "novice"
>   config variable so that Gnus can post illegal articles.

Isn't that something that's rather difficult to achieve?  
`(setq user-mail-address "god@heaven.org")'?  

Ok, that wouldn't result in an illegal article, just a somewhat
annoying article.  

>   So you might have a variable with the list of headers that are always
>   inserted and/or verified *in addition* to the standard ones, but
>   if you want to remove/deform a standard header you must go via
>   an "advanced" variable, a hook or an fset.

Hm.  Aren't the header generation variables rather "advanced" already,
in a way?  `message-required-news-headers' does the insertion while
`message-header-syntax-checks' does the checking...  

I agree with you in principle (I think), but do you have any specific
examples?

> - Error messages should either contain enough help to let a novice
>   correct the error, or it should tell him where to read about how to
>   fix it.
> 
>   Error messages that refer to other text, could be put in a separate
>   info file, and the message would pop up in a new Info buffer, with
>   menu entries pointing to further reading. 

That's a very good idea.  Definitely.  So if the From header is
totally invalid, an info node explaining how the From header should
look like is popped up with plenty of references to documentation on
the relevant variables.  Sounds like quite a lot of writing, though.

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."


  reply	other threads:[~1996-04-22  0:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-04-11 22:12 Hallvard B Furuseth
1996-04-22  0:48 ` Lars Magne Ingebrigtsen [this message]
1996-04-22  7:50   ` Hallvard B Furuseth
1996-04-22 19:39     ` Lars Magne Ingebrigtsen
1996-04-24 12:30       ` Hallvard B Furuseth
1996-04-28  9:02         ` Lars Magne Ingebrigtsen

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=x6d951hyni.fsf@eyesore.no \
    --to=larsi@ifi.uio.no \
    /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).