unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Gabriel <gabriel376@hotmail.com>
To: 50670@debbugs.gnu.org
Subject: bug#50670: 28.0.50; Conflict on minibuffer indicator overlays
Date: Sun, 19 Sep 2021 02:59:19 -0300	[thread overview]
Message-ID: <CH2PR01MB58792C5AF98CFA6243408FA38BDF9@CH2PR01MB5879.prod.exchangelabs.com> (raw)
In-Reply-To: <83zgs93ydb.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 19 Sep 2021 08:53:04 +0300")

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





  reply	other threads:[~2021-09-19  5:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2021-09-19  6:25     ` Eli Zaretskii
2021-09-19  6:36     ` 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=CH2PR01MB58792C5AF98CFA6243408FA38BDF9@CH2PR01MB5879.prod.exchangelabs.com \
    --to=gabriel376@hotmail.com \
    --cc=50670@debbugs.gnu.org \
    /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).