unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: clemera@posteo.net
Cc: 45177@debbugs.gnu.org
Subject: bug#45177: 27.1; Access to invoking top level command in minibuffer
Date: Fri, 11 Dec 2020 21:41:58 +0100	[thread overview]
Message-ID: <87czzg8489.fsf@gnus.org> (raw)
In-Reply-To: <ac9e6bcd-97ec-45d1-d518-09ac1ba84247@posteo.de> (clemera@posteo.net's message of "Fri, 11 Dec 2020 15:20:34 +0100")

clemera@posteo.net writes:

> For command based settings it would be nice to be able to have
> access to the top level command from which the current minibuffer
> session was invoked from. This should also work with multiple minibuffer
> invokations during a command. Using `minibuffer-setup-hook' to save
> `real-this-command' does not work, for example with:
>
> ```elisp
> (defun example-command ()
>   (interactive)
>   (read-string "Example: ")
>   (message "%s" real-this-command))
> ```
>
> `real-this-command' will be `exit-minibuffer' after the `read-string'
> so any minibuffer invokation within that command afterwards will no
> longer know about `example-command'.

Hm...  I'm not quite sure "the top level command" is a well-defined
concept?  You can enter a number of nested recursive edits, and I think
what you probably want is the innermost command that invoked a recursive
edit?

So perhaps it would make sense for Frecursive_edit (or some other handy
function when entering the minibuffer) to let-bind a new variable (say,
`this-recursive-command'?) to the value of `real-this-command'?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2020-12-11 20:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11 14:20 bug#45177: 27.1; Access to invoking top level command in minibuffer clemera
2020-12-11 17:35 ` Drew Adams
2020-12-12 13:28   ` Clemens
2020-12-12 13:39   ` clemera
2020-12-11 20:41 ` Lars Ingebrigtsen [this message]
2020-12-12 13:31   ` clemera
2020-12-13 12:29     ` Lars Ingebrigtsen
2020-12-13 13:29       ` clemera
2020-12-14 15:45         ` Lars Ingebrigtsen
2020-12-14 17:52           ` Clemens
2020-12-14 18:01           ` Clemens
2020-12-15  6:18             ` Lars Ingebrigtsen
2020-12-15 11:58               ` Clemens
     [not found]           ` <jwvk0l4ail0.fsf-monnier+emacs@gnu.org>
2021-08-02  4:04             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-04  5:49               ` Lars Ingebrigtsen
2020-12-13 13:39       ` clemera
2020-12-13 14:16       ` clemera
2021-01-12  8:46         ` Clemens
2020-12-12 20:14   ` Juri Linkov
2020-12-12 21:25     ` clemera
2020-12-13  8:47       ` Juri Linkov
2020-12-13 11:40         ` clemera
2020-12-13 11:45         ` clemera
     [not found] ` <jwvpmuwaj0o.fsf-monnier+emacs@gnu.org>
2021-08-02  4:03   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-04  5:51     ` 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

  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=87czzg8489.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=45177@debbugs.gnu.org \
    --cc=clemera@posteo.net \
    /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).