all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org, dgutov@yandex.ru
Subject: Re: emacs-27 027da65: Fix display of minibuffer prompt in ido.el
Date: Fri, 14 Feb 2020 10:08:17 +0200	[thread overview]
Message-ID: <83v9o9pp5a.fsf@gnu.org> (raw)
In-Reply-To: <jwvk14qm50l.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Thu, 13 Feb 2020 18:39:40 -0500)

> 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.



  reply	other threads:[~2020-02-14  8:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2020-02-14 11:00         ` Dmitry Gutov

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=83v9o9pp5a.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.