From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 31020@debbugs.gnu.org
Subject: bug#31020: 27.0; Please provide a way to know about menu-bar wrapping
Date: Mon, 02 Apr 2018 09:08:58 +0300 [thread overview]
Message-ID: <837epq6sxx.fsf@gnu.org> (raw)
In-Reply-To: <37c99926-a5e5-4fa8-b734-6f9c146740e9@default> (message from Drew Adams on Sun, 1 Apr 2018 20:03:00 -0700 (PDT))
> Date: Sun, 1 Apr 2018 20:03:00 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
>
> When a frame is narrower than the text in the
> menu-bar, that text is wrapped. And yet the value of frame parameter
> `menu-bar-lines' is not increased (which is good).
>
> It would be good to be able to know (from Elisp) how many "visual"
> (effective) menu-bar lines there are currently, that is, how many times
> the menu-bar text is wrapped. (It is typically wrapped zero or one
> time, producing text that appears visually to be two lines.)
I don't understand why you think that the menu-bar-lines parameter
should not be it. AFAIU, the problem with setting it (or any other
frame parameter) to the actual value is that with many toolkits Emacs
simply doesn't know the correct value. But maybe Martin will have
some trick up his sleeves.
next prev parent reply other threads:[~2018-04-02 6:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 3:03 bug#31020: 27.0; Please provide a way to know about menu-bar wrapping Drew Adams
2018-04-02 6:08 ` Eli Zaretskii [this message]
2018-04-02 8:54 ` martin rudalics
2018-04-02 13:32 ` Drew Adams
2019-09-28 18:42 ` Stefan Kangas
[not found] <<37c99926-a5e5-4fa8-b734-6f9c146740e9@default>
[not found] ` <<837epq6sxx.fsf@gnu.org>
2018-04-02 13:25 ` Drew Adams
2018-04-03 6:49 ` martin rudalics
2018-04-03 14:28 ` Drew Adams
2018-04-04 7:49 ` martin rudalics
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=837epq6sxx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31020@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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.