unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31020@debbugs.gnu.org
Subject: bug#31020: 27.0; Please provide a way to know about menu-bar wrapping
Date: Mon, 2 Apr 2018 06:25:30 -0700 (PDT)	[thread overview]
Message-ID: <e0817e5d-0209-4c63-8e76-79da5faa483b@default> (raw)
In-Reply-To: <<837epq6sxx.fsf@gnu.org>>

> > 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.

I think it's helpful to distinguish (1) the actual,
current number of lines used, reflecting any possible
wrapping, from (2) the user's setting of how many
lines should be used for the menu-bar.

How those are distinguished doesn't matter to me so
much.

And if you decide that there is no sense in such a
distinction, and that the parameter value should be
automatically changed, dynamically, as a frame's
width is changed (e.g. to force or remove wrapping),
then that would probably be OK too.

The problem, at least on MS Windows, is that the
menu-bar wraps, and there is no way (AFAIK) to know
from Lisp who many actual lines are currently used
to show the menu-bar.

This is an old problem, as you know.  It would be
really good to finally put it to bed, if possible.





       reply	other threads:[~2018-04-02 13:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<37c99926-a5e5-4fa8-b734-6f9c146740e9@default>
     [not found] ` <<837epq6sxx.fsf@gnu.org>
2018-04-02 13:25   ` Drew Adams [this message]
2018-04-03  6:49     ` bug#31020: 27.0; Please provide a way to know about menu-bar wrapping martin rudalics
2018-04-03 14:28       ` Drew Adams
2018-04-04  7:49         ` martin rudalics
2018-04-02  3:03 Drew Adams
2018-04-02  6:08 ` Eli Zaretskii
2018-04-02  8:54   ` martin rudalics
2018-04-02 13:32     ` Drew Adams
2019-09-28 18:42 ` Stefan Kangas

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=e0817e5d-0209-4c63-8e76-79da5faa483b@default \
    --to=drew.adams@oracle.com \
    --cc=31020@debbugs.gnu.org \
    --cc=eliz@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).