From: Clemens <clemera@posteo.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 45177@debbugs.gnu.org
Subject: bug#45177: 27.1; Access to invoking top level command in minibuffer
Date: Tue, 12 Jan 2021 09:46:40 +0100 [thread overview]
Message-ID: <408bda30-7089-877d-2294-b0b2d9389c69@posteo.net> (raw)
In-Reply-To: <377c1b01-0990-669e-9cc2-1e18a4508e93@posteo.de>
After some experiments, this isn't sufficient for our purposes. What we
would really need is identifying the call which invokes the minibuffer
session. Having access to the surrounding function call would help, in
combination with the prompt text and in some cases completion table data
this should work. I guess we need to use advice or would it be possible
to expose the surrounding function call of the current minibuffer session?
I think having the new variable is still an improvement as one just
hadn't access to this sate before and it can be used for other purposes
as minibuffer session configuration, too.
next prev parent reply other threads:[~2021-01-12 8:46 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
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 [this message]
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=408bda30-7089-877d-2294-b0b2d9389c69@posteo.net \
--to=clemera@posteo.net \
--cc=45177@debbugs.gnu.org \
--cc=larsi@gnus.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).