unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: martin rudalics <rudalics@gmx.at>, 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:32:49 -0700 (PDT)	[thread overview]
Message-ID: <266400ad-5ec5-4bfb-9192-6e15aa0e25a2@default> (raw)
In-Reply-To: <5AC1EFC0.6020801@gmx.at>

> So what you can do is the following: Make a frame with a _visibly
> unwrapped_ menu bar, get the menu bar height via
> (cddr (assq 'menu-bar-size (frame-geometry)))
> 
> Do the same for a frame with a _visibly wrapped_ two-lines menu bar.
> You can now derive the height of the single-line and any additional
> menu bar line and use these values together with 'frame-geometry' for
> getting the actual number of lines.

That's good to know; thanks.  But I don't think it will
help code that has only a given frame to examine, e.g.,
code that doesn't want to bother some user by creating
or resizing frames to determine this.  And anyway, the
_code_ cannot, by itself, tell the _visibly wrapped_
condition.

IOW, that suggestion might help a user to determine,
by looking, what the situation is.  But I don't see how
I could use in from Lisp to know what the situation is.
Let me know, if I'm missing something simple.

> Obviously, this will work only as long as you do not change themes,
> the menu bar height of the current theme or the resolution of your
> screen or whatever else could affect this.  And since you have to
> visuallly check the "wrappedness" of the menu bar, this work cannot be
> reasonably done from within Emacs.

Ah, that's just what I meant above.  Thanks for confirming.





  reply	other threads:[~2018-04-02 13:32 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
2018-04-02  8:54   ` martin rudalics
2018-04-02 13:32     ` Drew Adams [this message]
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

  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=266400ad-5ec5-4bfb-9192-6e15aa0e25a2@default \
    --to=drew.adams@oracle.com \
    --cc=31020@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=rudalics@gmx.at \
    /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).