From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Gnus initialization file in the manual (was: [gnus.commits] Changes committed gnus/texi (ChangeLog gnus.texi))
Date: Mon, 07 May 2007 20:02:53 +0200 [thread overview]
Message-ID: <v9odkwjyuq.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <muxwszk7osx.fsf@uzeb.lrde.epita.fr>
On Mon, May 07 2007, Didier Verna wrote:
>> +2007-05-03 Reiner Steib <Reiner.Steib@gmx.de>
>> +
>> + * gnus.texi (Running NNDiary): Use ~/.gnus.el instead of gnusrc.
>> +
[...]
> Actually, I had used intentionally "gnusrc" as a generic term for the
> Gnus initialization file,
I think it's confusing to use "gnusrc". The term "gnusrc" is not
common—at least I have never seen it before.
> because this file is customizable, so ~/gnus.el is not very
> accurate[1].
[ You meant ~/.gnus.el, I suppose. ] If the user know how to change
`gnus-init-file', (s)he should be aware that the manual describes the
default name. The same holds for `.newsrc', ~/News/, ~/Mail/,
~/.authinfo, key bindings etc.
> If you don't like "gnusrc", maybe we could use something like "gnus
> init file" throughout the manual, possibly with an xref to the "Gnus
> Startup Files" section of the manual ?
It will clutter the manual and I don't think this will help the user.
> By default, it can also be just ".gnus".
I'd recommend ".el" because (X)Emacs will automatically open it in
Lisp mode. "~/" makes it more clear that it in HOME. The dot is easy
to miss (at least for Unix-Newbies): There was actually a user who
edited lisp/gnus.el!
In 2003, I've changed the manual to use ~/.gnus.el throughout (and
fixed the markup) to avoid confusion.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
prev parent reply other threads:[~2007-05-07 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 13:20 [gnus.commits] Changes committed gnus/texi (ChangeLog gnus.texi) Didier Verna
2007-05-07 18:02 ` Reiner Steib [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=v9odkwjyuq.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.org \
/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).