unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-devel@gnu.org>
Subject: RE: Why isn't C-m listed here?
Date: Mon, 16 Apr 2007 07:54:10 -0700	[thread overview]
Message-ID: <EIENLHALHGIMHGDOLMIMIEKLDAAA.drew.adams@oracle.com> (raw)
In-Reply-To: <87d524l7mx.fsf@catnip.gol.com>

> > As the topic says: Why isn't C-m listed here:
> > and if it was, what would its description be? Alias for <RET>?
>
> It's not an alias for RET, it _is_ RET.
>
> RET == C-m

It is good, but not enough, to teach others here (emacs-devel). Pointing
something out here cannot be an alternative to the manual teaching the same
thing or (in this case) facilitating access to the same information.

Precisely because this user was missing that knowledge, C-m (and C-i, C-j,
and so on) should appear explicitly in the index. And the index link should
target a manual section where the equivalence is pointed out.

In general (please don't follow up with "Where do you draw the line?"), when
there are multiple names for the same thing, an index should provide
corresponding multiple entries. That applies even for incorrect names and
faux amis. Users look things up under different names, and they don't always
think in terms of the standard terminology.

That is why "paste" belongs in the index, pointing to a section about
yanking, even though "paste" and "yank" are not exactly synonymous. It is
why "window, window-manager" and "window-manager window" could also be index
entries, pointing to a section that described Emacs frames and the term
"frame".

I'm sure (i.e. I hope) that I'm preaching to the choir on this, but it's
unfortunately too easy to just answer a question here and not follow up by
improving the manual.

I must say that Eli is very diligent in thinking about what needs to be done
to improve the manual. Practically every time a user mentions in
help-gnu-emacs that s?he couldn't find something in the manual, Eli inquires
about how to make manual lookup easier for that case. Kudos for that, Eli.

      parent reply	other threads:[~2007-04-16 14:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-16 14:15 Why isn't C-m listed here? Eric Lilja
2007-04-16 14:24 ` Miles Bader
2007-04-16 14:43   ` Eric Lilja
2007-04-16 18:43     ` Alan Mackenzie
2007-04-16 19:38       ` Eric Lilja
2007-04-16 14:54   ` Drew Adams [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

  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=EIENLHALHGIMHGDOLMIMIEKLDAAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    --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 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).