From: Noam Postavsky <npostavs@gmail.com>
To: "Francesco Potortì" <pot@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 25454@debbugs.gnu.org
Subject: bug#25454: 25.1; improvement ftoopy-from-above-command
Date: Sun, 01 Sep 2019 09:57:16 -0400 [thread overview]
Message-ID: <87imqcm85f.fsf@gmail.com> (raw)
In-Reply-To: <E1i42KK-0001zG-DP@tucano.isti.cnr.it> ("Francesco \=\?utf-8\?Q\?Potort\=C3\=AC\=22's\?\= message of "Sat, 31 Aug 2019 14:17:56 +0200")
Francesco Potortì <pot@gnu.org> writes:
>>>Lars:
>>>>Seems a bit small for a separate package. And the repeated call thing
>>>>could be useful in itself. Couldn't the increment behaviour be enabled
>>>>by a non-numeric argument instead?
>
>>Francesco Potortì <pot@gnu.org> writes:
>>> What do you suggest? Maybe M-3 M-p copies the next three characters,
>>> while C-u 3 M-p increments by three?
>
>>M-3 and C-u 3 do the same thing, I think?
>
> They normally do. And they do in this case. But it can be changed, and
> I was following up with your suggestion, with a proposal for a different
> user interface where M-3 and C-u 3 do different things.
No, both C-u 3 and M-3 will set the prefix argument to 3, so commands
cannot distinguish between them. I know I suggested the numeric vs
non-numeric thing, but I think I was just confused about it.
Non-numeric arguments are only good for a single toggle (increment vs no
increment), not control over a amount (increment by X). And you can't
express both at once (both increment and repeat).
prev parent reply other threads:[~2019-09-01 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-15 20:00 bug#25454: 25.1; improvement ftoopy-from-above-command Francesco Potortì
2019-07-27 10:35 ` Lars Ingebrigtsen
2019-07-27 11:29 ` Noam Postavsky
2019-07-27 11:32 ` Lars Ingebrigtsen
2019-07-28 20:50 ` Juri Linkov
[not found] ` <E1i3IDK-0007DM-JK@tucano.isti.cnr.it>
2019-08-30 9:52 ` Lars Ingebrigtsen
2019-08-31 12:17 ` Francesco Potortì
2019-09-01 13:57 ` Noam Postavsky [this message]
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=87imqcm85f.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=25454@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=pot@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).