GNU bug report logs - #50670
28.0.50; Conflict on minibuffer indicator overlays

Previous Next

To reply to this bug, email your comments to 50670 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Gabriel <gabriel376 <at> hotmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 28.0.50; Conflict on minibuffer indicator overlays
Date: Sun, 19 Sep 2021 02:31:08 -0300

Message #8 received at 50670 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Gabriel <gabriel376 <at> hotmail.com>
Cc: 50670 <at> debbugs.gnu.org
Subject: Re: bug#50670: 28.0.50; Conflict on minibuffer indicator overlays
Date: Sun, 19 Sep 2021 08:53:04 +0300

> From: Gabriel <gabriel376 <at> hotmail.com>
> Description: Apparently, there is a conflict between the overlays of
>  'minibuffer-depth-indicate-mode' and 'icomplete-mode' when inside
>  recursive minibuffers.
> Date: Sun, 19 Sep 2021 02:31:08 -0300

The body of the message came in empty.  Please re-send your full
report, including the details of your configuration collected by
"M-x report-emacs-bug", and if possible also a recipe for reproducing
the issue starting from "emacs -Q".

Thanks.

Message #11 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Gabriel <gabriel376 <at> hotmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Re: bug#50670: 28.0.50; Conflict on minibuffer indicator overlays
Date: Sun, 19 Sep 2021 02:59:19 -0300

Eli Zaretskii <eliz <at> gnu.org> writes:

>
> The body of the message came in empty.  Please re-send your full
> report, including the details of your configuration collected by
> "M-x report-emacs-bug", and if possible also a recipe for reproducing
> the issue starting from "emacs -Q".
>
> Thanks.

Hi Eli,

Thank you. Strange, I did sent a body. I guess it's something I messed
up in my init.el. Anyway, here is the information of this bug report:

Description:
Apparently, there is a conflict between the overlays of
'minibuffer-depth-indicate-mode' and 'icomplete-mode' when inside
recursive minibuffers.

Steps
1) emacs -Q from master branch
2) eval:
    (setq enable-recursive-minibuffers t)
    (minibuffer-depth-indicate-mode 1)
    (setq icomplete-scroll t
          icomplete-show-matches-on-no-input nil)
    (icomplete-vertical-mode 1)
3) C-x f multiple times to go into recursive minibuffers

The 'minibuffer-depth-indicate-mode' overlay "[%s]" is rendered on
the right side of 'icomplete-mode' overlay "%s/%s" momentarily, and then
it moves to the left side (the correct position). The problem can also
be reproduced when the minibuffer input changes, e.g., by typing
'C-x f' + 'backspace'.

--
        Gabriel

Message #14 received at 50670 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Gabriel <gabriel376 <at> hotmail.com>
Cc: 50670 <at> debbugs.gnu.org
Subject: Re: bug#50670: 28.0.50; Conflict on minibuffer indicator overlays
Date: Sun, 19 Sep 2021 09:25:00 +0300

> From: Gabriel <gabriel376 <at> hotmail.com>
> Date: Sun, 19 Sep 2021 02:59:19 -0300
> 
> Apparently, there is a conflict between the overlays of
> 'minibuffer-depth-indicate-mode' and 'icomplete-mode' when inside
> recursive minibuffers.
> 
> Steps
> 1) emacs -Q from master branch
> 2) eval:
>     (setq enable-recursive-minibuffers t)
>     (minibuffer-depth-indicate-mode 1)
>     (setq icomplete-scroll t
>           icomplete-show-matches-on-no-input nil)
>     (icomplete-vertical-mode 1)
> 3) C-x f multiple times to go into recursive minibuffers
> 
> The 'minibuffer-depth-indicate-mode' overlay "[%s]" is rendered on
> the right side of 'icomplete-mode' overlay "%s/%s" momentarily, and then
> it moves to the left side (the correct position). The problem can also
> be reproduced when the minibuffer input changes, e.g., by typing
> 'C-x f' + 'backspace'.

FWIW, I see only the latter, when I type Backspace.

Message #17 received at 50670 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Gabriel <gabriel376 <at> hotmail.com>
Cc: 50670 <at> debbugs.gnu.org
Subject: Re: bug#50670: 28.0.50; Conflict on minibuffer indicator overlays
Date: Sun, 19 Sep 2021 09:36:50 +0300

> From: Gabriel <gabriel376 <at> hotmail.com>
> Date: Sun, 19 Sep 2021 02:59:19 -0300
> 
> Apparently, there is a conflict between the overlays of
> 'minibuffer-depth-indicate-mode' and 'icomplete-mode' when inside
> recursive minibuffers.
> 
> Steps
> 1) emacs -Q from master branch
> 2) eval:
>     (setq enable-recursive-minibuffers t)
>     (minibuffer-depth-indicate-mode 1)
>     (setq icomplete-scroll t
>           icomplete-show-matches-on-no-input nil)
>     (icomplete-vertical-mode 1)
> 3) C-x f multiple times to go into recursive minibuffers
> 
> The 'minibuffer-depth-indicate-mode' overlay "[%s]" is rendered on
> the right side of 'icomplete-mode' overlay "%s/%s" momentarily, and then
> it moves to the left side (the correct position). The problem can also
> be reproduced when the minibuffer input changes, e.g., by typing
> 'C-x f' + 'backspace'.

FWIW, I see only the latter, when I type Backspace.

Doesn't this happen because both mb-depth.el and icomplete.el put
overlays with before-string on the same position, minibuffer's BOB?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.