From: "Richard M. Stallman" <rms@gnu.org>
Cc: lennart.borgman.073@student.lu.se, emacs-devel@gnu.org
Subject: Re: Faces customization group linked from mode groups
Date: Tue, 15 Nov 2005 18:21:11 -0500 [thread overview]
Message-ID: <E1EcA6x-0005a2-E3@fencepost.gnu.org> (raw)
In-Reply-To: <87u0eeam1d.fsf@jurta.org> (message from Juri Linkov on Tue, 15 Nov 2005 02:42:54 +0200)
>From all these link types only four are documented in the Emacs Lisp
manual in the node (info "(elisp)Common Keywords"): custom-manual,
info-link, url-link and emacs-commentary-link. What about documenting
remaining six types: custom-group-link, function-link, variable-link,
file-link, emacs-library-link and documentation-link?
In principle it sounds good. Please write a patch we could consider.
Maybe
Widget link types should be documented in the Widget manual, and
No, no, no! That idea comes from trying to organize things in the
most logical structure--which is the wrong approach to structuring
documentation. The main goal of the manual is _to be convenient_.
I put this info in the Emacs Lisp Manual because people need it for
writing ordinary Lisp programs well. To put it somewhere else would
be a more logical structure, but it would be less convenient.
Logical structuring of the documentation sometimes increases
convenience, and sometimes gets in the way. When it increases
convenience, it is good. When it gets in the way, it is bad.
next prev parent reply other threads:[~2005-11-15 23:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 22:03 Faces customization group linked from mode groups Lennart Borgman
2005-11-05 7:43 ` Juri Linkov
2005-11-05 19:59 ` Lennart Borgman
2005-11-06 17:35 ` Richard M. Stallman
2005-11-07 14:27 ` Juri Linkov
2005-11-07 21:56 ` Richard M. Stallman
2005-11-08 12:45 ` Juri Linkov
2005-11-11 7:42 ` Richard M. Stallman
2005-11-11 19:34 ` Juri Linkov
2005-11-12 17:50 ` Richard M. Stallman
2005-11-15 0:48 ` Juri Linkov
2005-11-15 23:21 ` Richard M. Stallman
2005-11-15 0:42 ` Juri Linkov
2005-11-15 23:21 ` Richard M. Stallman [this message]
2005-11-17 7:46 ` Juri Linkov
2005-11-18 16:57 ` Richard M. Stallman
2005-11-07 14:28 ` Juri Linkov
2005-11-05 14:35 ` Richard M. Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1EcA6x-0005a2-E3@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman.073@student.lu.se \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).