From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 45806@debbugs.gnu.org
Subject: bug#45806: 26.3; `menu-bar-separator'
Date: Tue, 12 Jan 2021 17:04:34 +0200 [thread overview]
Message-ID: <83pn2adwn1.fsf@gnu.org> (raw)
In-Reply-To: <73e90890-b70a-4eb8-aa9e-d40959d1e1ec@default> (message from Drew Adams on Mon, 11 Jan 2021 16:32:31 -0800 (PST))
> Date: Mon, 11 Jan 2021 16:32:31 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
>
> This variable (defconst) doesn't seem to be documented anywhere.
It has a doc string, and if you look at its usage, this is all you'll
ever need.
> It seems to be used for menus in general; it doesn't seem to be tied to
> the menu-bar in any way. And its only doc is the doc string, which says
> only "Separator for menus." Could it be renamed to remove any mention
> of the menu-bar (keeping the old name as alias)?
Sorry, this name is with us for too long to rename it now.
> How is it actually used? Is it used only in (some?) toolkits?
Look at menu-bar.el (obviously), it's used all over there. On all the
toolkits and also in no-toolkit builds.
> It's a defconst (why?), so presumably you shouldn't change it. But
> changing it doesn't seem to have any effect anyway, in MS Windows. If
> this is hard-coded then why is it even needed?
See above. If you really want to see the effect of changing it
(why?), I think you will need to rebuild Emacs.
next prev parent reply other threads:[~2021-01-12 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 0:32 bug#45806: 26.3; `menu-bar-separator' Drew Adams
2021-01-12 15:04 ` Eli Zaretskii [this message]
[not found] <<73e90890-b70a-4eb8-aa9e-d40959d1e1ec@default>
[not found] ` <<83pn2adwn1.fsf@gnu.org>
2021-01-12 16:34 ` Drew Adams
2021-01-12 17:03 ` Eli Zaretskii
2021-01-12 18:09 ` Drew Adams
2021-01-12 18:22 ` Eli Zaretskii
2021-01-12 18:23 ` Eli Zaretskii
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=83pn2adwn1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45806@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 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).