From: Lars Ingebrigtsen <larsi@gnus.org>
To: miha@kamnitnik.top
Cc: 48603@debbugs.gnu.org
Subject: bug#48603: 27.2; [PATCH] Quit minibuffers without aborting kmacros
Date: Tue, 25 May 2021 21:54:59 +0200 [thread overview]
Message-ID: <877djmegh8.fsf@gnus.org> (raw)
In-Reply-To: <86eedx7c0u.fsf@miha-pc> (miha@kamnitnik.top's message of "Sun, 23 May 2021 16:36:17 +0200")
miha@kamnitnik.top writes:
> Rationale: a user wants to copy a command from command history without
> executing it. Or user wants to complete a file name in C-x C-f and copy
> it without finding the file. I believe this should be possible in
> keyboard macros.
`C-g' is part of how one normally operates `M-x' (etc.) in some
circumstances, so it might make sense to have a special quit symbol for
that; yes.
Does anybody else have an opinion here?
> * src/data.c (syms_of_data): New error symbol `lite-quit'
But it should be called something more descriptive, like
`minibuffer-quit'.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-05-25 19:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 14:36 bug#48603: 27.2; [PATCH] Quit minibuffers without aborting kmacros miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-25 19:54 ` Lars Ingebrigtsen [this message]
2021-05-25 21:34 ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-20 12:37 ` Lars Ingebrigtsen
2021-08-17 22:45 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-18 14:55 ` Lars Ingebrigtsen
2021-09-01 6:58 ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-01 8:11 ` Lars Ingebrigtsen
2021-09-03 17:53 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-07 15:11 ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-08 7:40 ` Lars Ingebrigtsen
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=877djmegh8.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=48603@debbugs.gnu.org \
--cc=miha@kamnitnik.top \
/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.