From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16054-done@debbugs.gnu.org, ture@lysator.liu.se
Subject: bug#16054: 24.3; Disabling menu bar when minibuffer is active causes cursor to be disconnected from point
Date: Mon, 30 Sep 2019 15:36:20 +0200 [thread overview]
Message-ID: <CADwFkmkkqPMCLFgbHM6BE693zm3Ds7KS3rJSyMPR3eDzEkoi6Q@mail.gmail.com> (raw)
In-Reply-To: <3632618d04a8382cf6f3f819c619a980.squirrel@webmail.lysator.liu.se>
Eli Zaretskii <eliz@gnu.org> writes:
>> * Start a new terminal-mode Emacs:
>>
>> emacs -nw -Q
>>
>> Emacs displays, with menu bar on top of screen.
>>
>> * Enable recursive minibuffers:
>>
>> M-: (setq enable-recursive-minibuffers t) RET
>>
>> * Type C-x C-f. The minibuffer activates, prompting for a file name.
>>
>> * Type C-u - 1 M-x menu-bar-mode RET. Menu bar goes away.
>>
>> * Type a file name and RET.
>>
>> * Editing now works, but the on-screen cursor does not reflect where
>> point is, but seems to move around somewhat unpredictably, and
>> screen layout is weird.
>>
>> Verified on
>>
>> * GNU Emacs 24.3.1 (i386-apple-darwin10.8.0, NS apple-appkit-1038.36)
>> * GNU Emacs 24.3.1 (sparc-sun-solaris2.10, X toolkit, Xaw scroll bars)
>> * GNU Emacs 21.4.1 (x86_64-redhat-linux-gnu, X toolkit, Xaw scroll bars)
>>
>> Terminal was Apple's Terminal.app from MacOS 10.7 or XTerm.
>
> FWIW, I cannot reproduce this with the current development trunk,
> neither on GNU/Linux nor on MS-Windows. So I guess it was already
> fixed in some way.
No more updates in close to 6 years, so I'm going to assume it's been
fixed and close this bug. If this is still an issue, please reopen the
bug report.
Best regards,
Stefan Kangas
prev parent reply other threads:[~2019-09-30 13:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 15:28 bug#16054: 24.3; Disabling menu bar when minibuffer is active causes cursor to be disconnected from point ture
2013-12-04 18:14 ` Eli Zaretskii
2019-09-30 13:36 ` Stefan Kangas [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmkkqPMCLFgbHM6BE693zm3Ds7KS3rJSyMPR3eDzEkoi6Q@mail.gmail.com \
--to=stefan@marxist.se \
--cc=16054-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=ture@lysator.liu.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.