From: "Drew Adams" <drew.adams@oracle.com>
To: "'Lars Magne Ingebrigtsen'" <larsi@gnus.org>,
"'Kevin Rodgers'" <kevin.d.rodgers@gmail.com>
Cc: 1947@debbugs.gnu.org
Subject: bug#1947: 23.0.60; Please document use of `dired' with an explicit file list
Date: Sun, 10 Jul 2011 10:36:33 -0700 [thread overview]
Message-ID: <0D8BD9F7F323447A9E4083525EC00174@us.oracle.com> (raw)
In-Reply-To: <m37h7qchdu.fsf@quimbies.gnus.org>
> > It is explained in dired's doc string. Since the only way
> > to use this feature is via Lisp (not M-x), I think the Emacs Lisp
> > manual would be a better place to document it.
>
> However, the Emacs Lisp manual doesn't document dired at all,
> so I think the current solution is best -- leave the
> documentation in the doc string of the `dired' command.
No, that does not address the bug report at all. The goal should be to improve
Emacs for users, not simply to close bugs willy nilly without addressing them.
This should be documented in the _Emacs_ manual. Not everything that requires a
little Emacs Lisp is relegated to the Elisp manual.
This is something that ordinary users should be made aware of. Simply
mentioning it in the doc string of `dired' is not sufficient.
Time has proven this to be the case. Although this is a very useful and very
easy to use feature, few users are aware of it.
next prev parent reply other threads:[~2011-07-10 17:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 18:44 bug#1947: 23.0.60; Please document use of `dired' with an explicit file list Drew Adams
2009-01-20 3:20 ` Kevin Rodgers
2011-07-10 14:58 ` Lars Magne Ingebrigtsen
2011-07-10 17:36 ` Drew Adams [this message]
2011-07-10 17:47 ` Eli Zaretskii
2011-07-10 18:30 ` Drew Adams
2011-07-10 18:44 ` Eli Zaretskii
2011-07-10 20:07 ` Drew Adams
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=0D8BD9F7F323447A9E4083525EC00174@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=1947@debbugs.gnu.org \
--cc=kevin.d.rodgers@gmail.com \
--cc=larsi@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.
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.