all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>, 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: Wed, 04 Apr 2018 09:49:48 +0200	[thread overview]
Message-ID: <5AC4839C.3030501@gmx.at> (raw)
In-Reply-To: <5ab23eb3-9744-4175-b15c-b3feee653876@default>

 > Yes.  But you'll perhaps tell me to do things another
 > way (e.g., pixelwise). ;-)

I'm afraid that both approaches might face similar problems.

 > If my code could know how many _effective_ (i.e.,
 > visual) `menu-bar-lines' were currently present then
 > it would just DTRT.

Why don't you try to divide the value of

(cddr (assq 'menu-bar-size (frame-geometry)))

by 'frame-char-height'?  IIUC the character height used by a toolkit
for drawing the menu bar is of no use to you anyway.

But to fit a frame you (and the pixelwise fitter as well) would have
to be able to tell _in advance_ whether the menu bar will wrap.  And
this is impossible since at least on a proprietary system like Windows
you would have to know which algorithm it uses for aligning menu bar
elements.  Or am I missing something?

martin





  reply	other threads:[~2018-04-04  7:49 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   ` bug#31020: 27.0; Please provide a way to know about menu-bar wrapping Drew Adams
2018-04-03  6:49     ` martin rudalics
2018-04-03 14:28       ` Drew Adams
2018-04-04  7:49         ` martin rudalics [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5AC4839C.3030501@gmx.at \
    --to=rudalics@gmx.at \
    --cc=31020@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --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 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.