From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: joca.bt@gmail.com, 48669@debbugs.gnu.org
Subject: bug#48669: Inconsistent overlay placement between minibuffer-message and set-minibuffer-message
Date: Sun, 06 Jun 2021 23:54:58 +0300 [thread overview]
Message-ID: <875yyqlnml.fsf@mail.linkov.net> (raw)
In-Reply-To: <83r1hfilfg.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 06 Jun 2021 08:58:27 +0300")
>> @@ -741,7 +741,8 @@ minibuffer-message
>> ;; Don't overwrite the face properties the caller has set
>> (text-properties-at 0 message))
>> (setq message (apply #'propertize message minibuffer-message-properties)))
>> - (let ((ol (make-overlay (point-max) (point-max) nil t t))
>> + (let* ((ovpos (minibuffer--message-overlay-pos))
>> + (ol (make-overlay ovpos ovpos nil t t))
>
> Doesn't this rely too much on the internal details of
> minibuffer--message-overlay-pos? At least, without any comments, this
> call looks like a riddle that isn't easy to unlock.
If minibuffer--message-overlay-pos serves its purpose for
set-minibuffer-message, it seems suitable for
minibuffer-message as well.
>> - (put-text-property 0 1 'cursor t message))
>> + (put-text-property 0 1 'cursor 1 message))
>
> Why this change?
Only to make minibuffer-message the identical copy of
set-minibuffer-message.
next prev parent reply other threads:[~2021-06-06 20:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 12:50 bug#48669: Inconsistent overlay placement between minibuffer-message and set-minibuffer-message João Guerra
2021-05-31 20:24 ` Juri Linkov
2021-06-05 21:43 ` Juri Linkov
2021-06-06 5:58 ` Eli Zaretskii
2021-06-06 20:54 ` Juri Linkov [this message]
2021-06-07 12:21 ` Eli Zaretskii
2021-06-08 16:52 ` Juri Linkov
2021-06-08 18:12 ` 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
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=875yyqlnml.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=48669@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=joca.bt@gmail.com \
/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).