unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Omission in tutorial
Date: Mon, 08 May 2006 19:03:11 +0200	[thread overview]
Message-ID: <85vesge9f4.fsf@lola.goethe.zz> (raw)
In-Reply-To: <49263.128.165.123.132.1147106263.squirrel@webmail.lanl.gov> (Stuart D. Herring's message of "Mon, 8 May 2006 09:37:43 -0700 (PDT)")

"Stuart D. Herring" <herring@lanl.gov> writes:

>> That's what I was worried about as well, in particular because of
>> the translations.  Still, I find the absence of this particular
>> help (which in contrast to other online helps can't be found in
>> menus or tooltips or supplementary messages or the basic C-h menu,
>> for obvious reasons) disturbing: I don't have a good answer to "how
>> was I supposed to know that?".
>
> *Note (emacs)Misc Help::.

I can tell people to read and work through the tutorial for getting
the hang of Emacs' basic operation.  To ask that for the whole manual
for something as basic in the "self-documenting" feature set of Emacs
is not likely to go down well...

The question is whether the functionality is basic and helpful and
non-obvious enough to warrant putting into the tutorial, not whether
there is documentation _anywhere_.  I remain of the opinion that it
would be a good idea, at least after the release, to mention this in
the tutorial.  Feel free to convince me otherwise.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2006-05-08 17:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-07 14:19 Omission in tutorial David Kastrup
2006-05-07 16:12 ` Burton Samograd
2006-05-07 21:47 ` Kim F. Storm
2006-05-08  7:36 ` Richard Stallman
2006-05-08  7:55   ` David Kastrup
2006-05-08 14:29     ` Luc Teirlinck
2006-05-08 16:37     ` Stuart D. Herring
2006-05-08 17:03       ` David Kastrup [this message]
2006-05-08 19:12         ` Lennart Borgman
2006-05-08 20:16         ` Stuart D. Herring
2006-05-08 20:24           ` David Kastrup
2006-05-08  8:41   ` Burton Samograd

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=85vesge9f4.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --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).