From: Tim Cross <theophilusx@gmail.com>
To: "Andreas Röhler" <andreas.roehler@online.de>
Cc: Daniel Colascione <dan.colascione@gmail.com>,
Andreas Schwab <schwab@linux-m68k.org>,
Drew Adams <drew.adams@oracle.com>,
emacs-devel@gnu.org
Subject: Re: more than one prefix argument
Date: Wed, 27 Jul 2011 22:51:59 +1000 [thread overview]
Message-ID: <CAC=50j8V6ehnPdM_-8rf7mjHxQnynYF1nKmbALkH=iF-zdFM8Q@mail.gmail.com> (raw)
In-Reply-To: <4E2FFAA1.4090205@online.de>
On Wed, Jul 27, 2011 at 9:46 PM, Andreas Röhler
<andreas.roehler@online.de> wrote:
> Am 27.07.2011 13:21, schrieb Andreas Schwab:
>>
>> Andreas Röhler<andreas.roehler@online.de> writes:
>>
>>> We need a number or a boolean.
>>
>> You need to distinguish C-u and 4 as well.
>>
>
> C-u would send `t'
>
which means now your possible values are both numeric and non-numeric,
requiring extra tests and increasing code complexity.
> If the command needs a 4 too possibly, write "p\nP" than enabling both
> input
>
How would you distinguish between that and multiple c-u's as in
C-u C-u C-i C-u M-x command
which ones are p and which ones are P?
>>> "p" should send a number, 1 as default.
>>> "P" a boolean, nil as default.
>>
>> "P" is the raw prefix. "p" is what prefix-numeric-value returns from
>> it.
>
> double-wouble
>
> lets have sent at once whats needed.
>
>
The shiraz tonight was very nice - I don't know if its you or me, but
I can't follow! Sorry.
Tim
next prev parent reply other threads:[~2011-07-27 12:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 19:59 more than one prefix argument Andreas Röhler
2011-07-26 20:10 ` Daniel Colascione
2011-07-26 20:36 ` Andreas Röhler
2011-07-26 20:57 ` Drew Adams
2011-07-26 20:36 ` Drew Adams
2011-07-27 6:25 ` Andreas Röhler
2011-07-27 9:25 ` Tim Cross
2011-07-27 9:37 ` Andreas Röhler
2011-07-27 9:48 ` Tim Cross
2011-07-27 10:21 ` Andreas Röhler
2011-07-27 11:21 ` Andreas Schwab
2011-07-27 11:46 ` Andreas Röhler
2011-07-27 12:39 ` Andreas Schwab
2011-07-27 12:51 ` Tim Cross [this message]
2011-07-27 12:46 ` Tim Cross
2011-07-27 15:09 ` Drew Adams
2011-07-27 9:38 ` Tim Cross
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='CAC=50j8V6ehnPdM_-8rf7mjHxQnynYF1nKmbALkH=iF-zdFM8Q@mail.gmail.com' \
--to=theophilusx@gmail.com \
--cc=andreas.roehler@online.de \
--cc=dan.colascione@gmail.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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).