From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: How about making `set-minibuffer-window' obsolete?
Date: Wed, 17 Mar 2021 14:57:19 +0200 [thread overview]
Message-ID: <83y2emc500.fsf@gnu.org> (raw)
In-Reply-To: <YFEaCS5wghO7Vz+z@ACM> (message from Alan Mackenzie on Tue, 16 Mar 2021 20:50:17 +0000)
> Date: Tue, 16 Mar 2021 20:50:17 +0000
> Cc: emacs-devel@gnu.org
> From: Alan Mackenzie <acm@muc.de>
>
> > I'd object to obsoleting a command just because it can be dangerous
> > when used unwisely.
>
> Every use of this command is unwise. It cannot possibly do anything
> useful. It can only cause problems.
I don't think I agree, not in this general form anyway. The C code
assigns values to minibuf_window in several places; this function is
the Lisp counterpart of that. If the C code can assign that variable,
why cannot Lisp code do the same if it needs to? With the current
tendency to move stuff from C to Lisp, it is even less understandable
why would you think this function's use in unwise. If you have
specific reasons for that, please describe them in more detail.
> Could I ask you, please, to reconsider?
I might -- if I see some specific reasoning. I didn't see that yet.
next prev parent reply other threads:[~2021-03-17 12:57 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 [this message]
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
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=83y2emc500.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.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 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.