* bug#50670: 28.0.50; Conflict on minibuffer indicator overlays
@ 2021-09-19 5:31 Gabriel
2021-09-19 5:53 ` Eli Zaretskii
0 siblings, 1 reply; 5+ messages in thread
From: Gabriel @ 2021-09-19 5:31 UTC (permalink / raw)
To: 50670
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#50670: 28.0.50; Conflict on minibuffer indicator overlays
2021-09-19 5:31 bug#50670: 28.0.50; Conflict on minibuffer indicator overlays Gabriel
@ 2021-09-19 5:53 ` Eli Zaretskii
2021-09-19 5:59 ` Gabriel
0 siblings, 1 reply; 5+ messages in thread
From: Eli Zaretskii @ 2021-09-19 5:53 UTC (permalink / raw)
To: Gabriel; +Cc: 50670
> From: Gabriel <gabriel376@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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#50670: 28.0.50; Conflict on minibuffer indicator overlays
2021-09-19 5:53 ` Eli Zaretskii
@ 2021-09-19 5:59 ` Gabriel
2021-09-19 6:25 ` Eli Zaretskii
2021-09-19 6:36 ` Eli Zaretskii
0 siblings, 2 replies; 5+ messages in thread
From: Gabriel @ 2021-09-19 5:59 UTC (permalink / raw)
To: 50670
Eli Zaretskii <eliz@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
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#50670: 28.0.50; Conflict on minibuffer indicator overlays
2021-09-19 5:59 ` Gabriel
@ 2021-09-19 6:25 ` Eli Zaretskii
2021-09-19 6:36 ` Eli Zaretskii
1 sibling, 0 replies; 5+ messages in thread
From: Eli Zaretskii @ 2021-09-19 6:25 UTC (permalink / raw)
To: Gabriel; +Cc: 50670
> From: Gabriel <gabriel376@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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#50670: 28.0.50; Conflict on minibuffer indicator overlays
2021-09-19 5:59 ` Gabriel
2021-09-19 6:25 ` Eli Zaretskii
@ 2021-09-19 6:36 ` Eli Zaretskii
1 sibling, 0 replies; 5+ messages in thread
From: Eli Zaretskii @ 2021-09-19 6:36 UTC (permalink / raw)
To: Gabriel; +Cc: 50670
> From: Gabriel <gabriel376@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?
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2021-09-19 6:36 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-09-19 5:31 bug#50670: 28.0.50; Conflict on minibuffer indicator overlays Gabriel
2021-09-19 5:53 ` Eli Zaretskii
2021-09-19 5:59 ` Gabriel
2021-09-19 6:25 ` Eli Zaretskii
2021-09-19 6:36 ` Eli Zaretskii
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).