From: dalanicolai <dalanicolai@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: "Lars Ingebrigtsen" <larsi@gnus.org>,
45392@debbugs.gnu.org, "Daniel Martín" <mardani29@yahoo.es>
Subject: bug#45392: 28.0.50; read-from-minibuffer sets `this-command` variable to `exit-minibuffer`
Date: Fri, 29 Jan 2021 01:11:33 +0100 [thread overview]
Message-ID: <CACJP=3k5ZDim9wJvXtBoSksu7_B=Z1Kp1EyJBf4qxZ+Yt=ytDw@mail.gmail.com> (raw)
In-Reply-To: <87o8he4scs.fsf@mail.linkov.net>
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
Yes, that's it. Great, thanks!
On Mon, 25 Jan 2021 at 18:08, Juri Linkov <juri@linkov.net> wrote:
> >> Thanks for your bug report. I think it is expected that 'this-command'
> >> is 'exit-minibuffer' in this case, because 'this-command' is usually set
> >> only once *at the beginning* of the execution of a command. It keeps
> >> its value until a *new* command is executed by Emacs. This is not
> >> explicitly said in the docstring, but it is mentioned in the Elisp Info
> >> manual.
> >>
> >> I don't know if the docstring could be expressed more clearly; I prefer
> >> to leave those command loop details to the Info manuals.
> >
> > I think so, too, so there doesn't seem to be anything further to do in
> > this bug report, and I'm closing it. If there's more to be done here,
> > please respond to the debbugs address and we'll reopen.
>
> Is it what the recently added varible 'current-minibuffer-command'
> intended to do? Then OP could use it like
>
> (defun test ()
> (interactive)
> (print current-minibuffer-command)
> (read-from-minibuffer "test")
> (print current-minibuffer-command))
>
[-- Attachment #2: Type: text/html, Size: 1619 bytes --]
prev parent reply other threads:[~2021-01-29 0:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 13:11 bug#45392: 28.0.50; read-from-minibuffer sets `this-command` variable to `exit-minibuffer` dalanicolai
2021-01-07 23:35 ` Unknown
2021-01-23 22:49 ` Lars Ingebrigtsen
2021-01-25 17:05 ` Juri Linkov
2021-01-29 0:11 ` dalanicolai [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACJP=3k5ZDim9wJvXtBoSksu7_B=Z1Kp1EyJBf4qxZ+Yt=ytDw@mail.gmail.com' \
--to=dalanicolai@gmail.com \
--cc=45392@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
--cc=mardani29@yahoo.es \
/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.