* Re: emacs-27 027da65: Fix display of minibuffer prompt in ido.el [not found] ` <20200212194123.6158D20B80@vcs0.savannah.gnu.org> @ 2020-02-13 23:19 ` Dmitry Gutov 2020-02-13 23:39 ` Stefan Monnier 0 siblings, 1 reply; 4+ messages in thread From: Dmitry Gutov @ 2020-02-13 23:19 UTC (permalink / raw) To: emacs-devel, Eli Zaretskii Hi Eli, On 12.02.2020 21:41, Eli Zaretskii wrote: > +@item minibuffer-message > +@kindex minibuffer-message @r{(text property)} > +This text property tells where to display temporary messages in an > +active minibuffer. TBH, I'm wary of documenting this variable in the manual, since we might prefer to do away with it later, if a sufficiently stable fix for the overlay-based solution is found. ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: emacs-27 027da65: Fix display of minibuffer prompt in ido.el 2020-02-13 23:19 ` emacs-27 027da65: Fix display of minibuffer prompt in ido.el Dmitry Gutov @ 2020-02-13 23:39 ` Stefan Monnier 2020-02-14 8:08 ` Eli Zaretskii 0 siblings, 1 reply; 4+ messages in thread From: Stefan Monnier @ 2020-02-13 23:39 UTC (permalink / raw) To: Dmitry Gutov; +Cc: Eli Zaretskii, emacs-devel >> +@item minibuffer-message >> +@kindex minibuffer-message @r{(text property)} >> +This text property tells where to display temporary messages in an >> +active minibuffer. > > TBH, I'm wary of documenting this variable in the manual, since we might > prefer to do away with it later, if a sufficiently stable fix for the > overlay-based solution is found. I tend to agree. This also suggests it should be renamed to `minibuffer--message`. Stefan ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: emacs-27 027da65: Fix display of minibuffer prompt in ido.el 2020-02-13 23:39 ` Stefan Monnier @ 2020-02-14 8:08 ` Eli Zaretskii 2020-02-14 11:00 ` Dmitry Gutov 0 siblings, 1 reply; 4+ messages in thread From: Eli Zaretskii @ 2020-02-14 8:08 UTC (permalink / raw) To: Stefan Monnier; +Cc: emacs-devel, dgutov > From: Stefan Monnier <monnier@iro.umontreal.ca> > Cc: emacs-devel@gnu.org, Eli Zaretskii <eliz@gnu.org> > Date: Thu, 13 Feb 2020 18:39:40 -0500 > > >> +@item minibuffer-message > >> +@kindex minibuffer-message @r{(text property)} > >> +This text property tells where to display temporary messages in an > >> +active minibuffer. > > > > TBH, I'm wary of documenting this variable in the manual, since we might > > prefer to do away with it later, if a sufficiently stable fix for the > > overlay-based solution is found. > > I tend to agree. I don't, at least not for the reasons described by Dmitry. Display of overlay strings is quite messy, especially at EOB; it already causes quite a few complex and sometimes inelegant code fragments in the display engine, in particular related to cursor positioning. So anything that allows us to avoid using overlay strings, and simply insert text into a buffer, is a win from my POV. And using a special text property to guide display (and other important features) is a technique we use elsewhere in Emacs. Granted, we don't always document such text properties, but in this case, we are talking about an area where quite a few external packages tend to offer all kinds of add-ons and improvements, so I thought it was important to document it, so that they could play well with the new set-message-function feature. That said, if you (or someone else) have other good reasons we would like not to publish this property, which are stronger than the considerations that led me to document it, I'm all ears. Thanks. ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: emacs-27 027da65: Fix display of minibuffer prompt in ido.el 2020-02-14 8:08 ` Eli Zaretskii @ 2020-02-14 11:00 ` Dmitry Gutov 0 siblings, 0 replies; 4+ messages in thread From: Dmitry Gutov @ 2020-02-14 11:00 UTC (permalink / raw) To: Eli Zaretskii, Stefan Monnier; +Cc: emacs-devel On 14.02.2020 10:08, Eli Zaretskii wrote: > That said, if you (or someone else) have other good reasons we would > like not to publish this property, which are stronger than the > considerations that led me to document it, I'm all ears. I don't think there are many external packages left to worry about, especially if we take care of Ivy, from a recent bug report (which might be entirely unrelated to minibuffer-message). But continuing to support the new text property only takes a few lines, so it's not the end of the world either. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-02-14 11:00 UTC | newest] Thread overview: 4+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- [not found] <20200212194122.31240.58820@vcs0.savannah.gnu.org> [not found] ` <20200212194123.6158D20B80@vcs0.savannah.gnu.org> 2020-02-13 23:19 ` emacs-27 027da65: Fix display of minibuffer prompt in ido.el Dmitry Gutov 2020-02-13 23:39 ` Stefan Monnier 2020-02-14 8:08 ` Eli Zaretskii 2020-02-14 11:00 ` Dmitry Gutov
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.