From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: larsi@gnus.org, 18083@debbugs.gnu.org
Subject: bug#18083: 24.4.50; (emacs) Arguments and (elisp) Prefix Command Arguments
Date: Sat, 30 Apr 2016 09:12:01 -0800 (GMT-08:00) [thread overview]
Message-ID: <da236fd8-df74-4752-b701-833471d3edf4@default> (raw)
In-Reply-To: <<83y47vnlse.fsf@gnu.org>>
> > This should not be about choosing to document only this one
> > or only that one.
>
> Of course, it is.
Why? Why should we not document both?
> > And it should not be based on what you tend to use or I tend to use.
>
> Then how come you raise this, based on your experience?
I am not, like you, claiming that my experience or preference
should be the only thing documented. I'm for a big tent,
documenting what you prefer (M-) and what I prefer sometimes
(C-). Not because you or I prefer this or that, but because
Emacs lets you use either one, and each is useful.
> > It costs little to mention that C- also can be used, like M-.
>
> It's bloat we need to justify.
I've justified it. And it's not bloat, but useful info for
users.
next prev parent reply other threads:[~2016-04-30 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 19:51 bug#18083: 24.4.50; (emacs) Arguments and (elisp) Prefix Command Arguments Drew Adams
2016-04-29 22:15 ` Lars Ingebrigtsen
2016-04-29 23:01 ` Drew Adams
2016-04-30 5:33 ` Eli Zaretskii
[not found] ` <<75d42f7e-707b-44e9-90b1-9b5d04207961@default>
[not found] ` <<83oa8rvex3.fsf@gnu.org>
2016-04-30 15:16 ` Drew Adams
2016-04-30 15:44 ` Eli Zaretskii
[not found] ` <<<75d42f7e-707b-44e9-90b1-9b5d04207961@default>
[not found] ` <<<83oa8rvex3.fsf@gnu.org>
[not found] ` <<feb4e8f1-a5ac-4799-ba19-8ca9ae22bdd2@default>
[not found] ` <<83y47vnlse.fsf@gnu.org>
2016-04-30 17:12 ` Drew Adams [this message]
2016-04-30 17:25 ` Eli Zaretskii
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=da236fd8-df74-4752-b701-833471d3edf4@default \
--to=drew.adams@oracle.com \
--cc=18083@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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.