From: Richard Stallman <rms@gnu.org>
Cc: Lute.Kamstra@cwi.nl, emacs-devel@gnu.org
Subject: Re: Update of Mode Line Format in the Lisp Reference Manual.
Date: Sun, 28 Sep 2003 11:33:53 -0400 [thread overview]
Message-ID: <E1A3dYX-0006o4-5m@fencepost.gnu.org> (raw)
In-Reply-To: <2719-Sat27Sep2003134258+0300-eliz@elta.co.il>
I see that you've consistently replaced "mode-line" with "mode line"
in this and similar contexts. I'm not sure which variant is more
correct English; please note that the phrase "mode-line construct" can
be rephrased as "construct of the mode line". I tend to write the
dash in the former, but not in the latter.
You are doing it right in both cases.
Thus, I think that, ideally, every
variable here should have a @cindex entry as well. For example, the
variable mode-line-position might have these entries:
@cindex buffer position indication, in mode line
@cindex mode line, buffer position indication
I think that is too much; it will make the index too big. That makes
the index less useful and makes the manual more expensive to print.
Most of those index entries are not necessary.
This whole section is about the mode line. As long as people can
easily find this section when they look for "mode line", that is good
enough. It only needs one index entry about the mode line, for the
whole section. So `@cindex mode line, buffer position indication' is
clearly unnecessary.
It is not so clear that `@cindex buffer position indication, in mode
line' is unnecessary, but I think it is. If you want to find how to
display something in the mode line, you just need to find the section
about it.
prev parent reply other threads:[~2003-09-28 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 15:45 Update of Mode Line Format in the Lisp Reference Manual Lute Kamstra
2003-09-27 11:42 ` Eli Zaretskii
2003-09-28 15:33 ` Richard Stallman [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=E1A3dYX-0006o4-5m@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=Lute.Kamstra@cwi.nl \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.