unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Van Ly <van.ly@sdf.org>
Cc: 53188@debbugs.gnu.org
Subject: bug#53188: 28.0.90; if tooltip-mode is off, modeline context menu blocks minibuffer at column 36
Date: Wed, 12 Jan 2022 14:28:39 +0800	[thread overview]
Message-ID: <87ilupsc14.fsf@yahoo.com> (raw)
In-Reply-To: <7ea6e621-6d7b-7b2-2cd6-25da43551ed@SDF.ORG> (Van Ly's message of "Tue, 11 Jan 2022 13:59:23 +0000 (UTC)")

Van Ly <van.ly@sdf.org> writes:

> observed behavior
> * minibuffer's message line is blocked by modeline context menu at
>   column 36
>
> expected behavior
> * minibuffer's message line is readable for the length of the width of
>   the emacs frame, modeline context menu offsets appropriately and
>   does not block minibuffer message line

I'm not going to mess with GTK+ menu placement (and I don't recommend
anyone to try that either, especially with GTK 3, where GTK performing
size allocation a menu causes native input to stop working for a weird
reason), but patches would be welcome to fix that in the Xt builds.  If
it helps, Motif provides some feature to define custom areas of a screen
where XmMenuShells should avoid, but I don't remember what it is.

Thanks.





      parent reply	other threads:[~2022-01-12  6:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11 13:59 bug#53188: 28.0.90; if tooltip-mode is off, modeline context menu blocks minibuffer at column 36 Van Ly
2022-01-11 17:16 ` Eli Zaretskii
2022-01-13  8:26   ` Van Ly
2022-01-13  9:59     ` Eli Zaretskii
2022-01-13 11:16       ` Van Ly
2022-01-13 12:38         ` Eli Zaretskii
2022-01-13 13:24           ` Van Ly
2022-01-13 13:48             ` Eli Zaretskii
2022-01-14 10:30               ` Van Ly
2022-01-12  6:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [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

  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=87ilupsc14.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=53188@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=van.ly@sdf.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).