From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/6009 Path: main.gmane.org!not-for-mail From: Lars Magne Ingebrigtsen Newsgroups: gmane.emacs.gnus.general Subject: Re: on Good Net-Keeping Seal Date: 22 Apr 1996 02:48:17 +0200 Message-ID: References: <199604112212.AAA00488@bombur2.uio.no> NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035146529 2182 80.91.224.250 (20 Oct 2002 20:42:09 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 20:42:09 +0000 (UTC) Return-Path: ding-request@ifi.uio.no Original-Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by deanna.miranova.com (8.7.5/8.6.9) with SMTP id SAA05235 for ; Sun, 21 Apr 1996 18:54:50 -0700 Original-Received: from trym.ifi.uio.no (4867@trym.ifi.uio.no [129.240.94.30]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Mon, 22 Apr 1996 03:20:06 +0200 Original-Received: (from larsi@localhost) by trym.ifi.uio.no ; Mon, 22 Apr 1996 03:20:04 +0200 Original-To: ding@ifi.uio.no Original-Lines: 40 X-Mailer: September Gnus v0.77/Emacs 19.30 Xref: main.gmane.org gmane.emacs.gnus.general:6009 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:6009 Hallvard B Furuseth 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."