GNU bug report logs -
#48669
Inconsistent overlay placement between minibuffer-message and set-minibuffer-message
Previous Next
Reported by: João Guerra <joca.bt <at> gmail.com>
Date: Wed, 26 May 2021 12:52:02 UTC
Severity: normal
Tags: fixed, patch
Fixed in version 28.0.50
Done: Juri Linkov <juri <at> linkov.net>
Bug is archived. No further changes may be made.
Full log
Message #16 received at 48669 <at> debbugs.gnu.org (full text, mbox):
> From: Juri Linkov <juri <at> linkov.net>
> Date: Sun, 06 Jun 2021 00:43:54 +0300
> Cc: 48669 <at> debbugs.gnu.org
>
>
> [1:text/plain Hide]
>
> > Would it make sense to change this behaviour (i.e. overlay
> > configuration) so that it is consistent in both functions?
>
> Thanks for the very useful suggestion. This could be fixed
> with the following patch where I tried to sync everything
> overlay-related from set-minibuffer-message to minibuffer-message:
>
>
> [2:text/x-diff Hide]
>
> diff --git a/lisp/minibuffer.el b/lisp/minibuffer.el
> index ffb74235e8..cb12226c07 100644
> --- a/lisp/minibuffer.el
> +++ b/lisp/minibuffer.el
> @@ -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.
> - (put-text-property 0 1 'cursor t message))
> + (put-text-property 0 1 'cursor 1 message))
Why this change?
This bug report was last modified 3 years and 345 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.