all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 18083@debbugs.gnu.org
Subject: bug#18083: 24.4.50; (emacs) Arguments and (elisp) Prefix Command Arguments
Date: Fri, 29 Apr 2016 16:01:41 -0700 (PDT)	[thread overview]
Message-ID: <75d42f7e-707b-44e9-90b1-9b5d04207961@default> (raw)
In-Reply-To: <87oa8sm596.fsf@gnus.org>

> > Both of these nodes speak of `M--', `M-3', etc.  They should also
> > mention the equivalent `C--', `C-3', etc.
> 
> I wonder whether the reason they aren't mentioned is that they're
> deprecated or something?  Anybody know?

No, they are not deprecated.  Presumably they are not mentioned
because they are not available in some Emacs terminal sessions.

That doesn't mean we shouldn't mention them - we should just
point out that they might not be available in some contexts.

They are particularly handy if you are using prefix args
a lot or repetitively, as they use the same modifier as `C-u'.
And they are somewhat easier for some people to type on some
(common) keyboards.





  reply	other threads:[~2016-04-29 23:01 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 [this message]
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
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=75d42f7e-707b-44e9-90b1-9b5d04207961@default \
    --to=drew.adams@oracle.com \
    --cc=18083@debbugs.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.