From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: acm@muc.de, emacs-devel@gnu.org
Subject: Re: How about making `set-minibuffer-window' obsolete?
Date: Wed, 17 Mar 2021 15:17:33 +0200 [thread overview]
Message-ID: <83sg4tdimq.fsf@gnu.org> (raw)
In-Reply-To: <98c16576-39b8-2f34-e9f5-4f5c04c28dcd@gmx.at> (message from martin rudalics on Wed, 17 Mar 2021 09:44:37 +0100)
> From: martin rudalics <rudalics@gmx.at>
> Date: Wed, 17 Mar 2021 09:44:37 +0100
>
> Rather `set-minibuffer-window' should take as argument a frame to set
> the 'minibuffer-window' parameter of that frame. This way it would
> become the counterpart of `minibuffer-window' which takes as argument a
> frame and returns that frame's minibuffer window.
I'm okay with extending this function that way (assuming the
additional parameter is made &optional).
> The current semantics of `set-minibuffer-window' is of no practical use.
Why not? how is it different from the C code doing the same?
> Lisp code should never deal with minibuf_window directly.
This seems to contradict what you propose above, doesn't it? Or what
am I missing?
> However, every minibuffer interaction should be aware of the fact
> that any frame's minibuffer window might change via
> fset_minibuffer_window under its feet.
Yes, using these facilities is not for the faint at heart. But that
doesn't mean it can never be useful, IMO.
next prev parent reply other threads:[~2021-03-17 13:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 18:16 How about making `set-minibuffer-window' obsolete? Alan Mackenzie
2021-03-16 18:42 ` Eli Zaretskii
2021-03-16 20:50 ` Alan Mackenzie
2021-03-17 12:57 ` Eli Zaretskii
2021-03-18 11:46 ` Alan Mackenzie
2021-03-18 12:01 ` Eli Zaretskii
2021-03-16 19:42 ` [External] : " Drew Adams
2021-03-16 23:04 ` Alan Mackenzie
2021-03-16 23:00 ` Stefan Monnier
2021-03-16 23:24 ` Alan Mackenzie
2021-03-17 3:31 ` Eli Zaretskii
2021-03-17 8:44 ` martin rudalics
2021-03-16 23:17 ` Dmitry Gutov
2021-03-16 23:28 ` Stefan Monnier
2021-03-17 8:44 ` martin rudalics
2021-03-17 13:17 ` Eli Zaretskii [this message]
2021-03-17 15:36 ` martin rudalics
2021-03-17 15:45 ` Eli Zaretskii
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=83sg4tdimq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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.