From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 45806-done@debbugs.gnu.org
Subject: bug#45806: 26.3; `menu-bar-separator'
Date: Tue, 12 Jan 2021 19:03:40 +0200 [thread overview]
Message-ID: <835z42dr4j.fsf@gnu.org> (raw)
In-Reply-To: <4313a39b-5d20-4fff-ab14-fb9be0a43a78@default> (message from Drew Adams on Tue, 12 Jan 2021 08:34:04 -0800 (PST))
> Date: Tue, 12 Jan 2021 08:34:04 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 45806@debbugs.gnu.org
>
> > Sorry, this name is with us for too long to rename it now.
>
> Not a great reason not to rename and alias.
Why am I not surprised that you don't accept the judgment of the
project maintainers?
> > > 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.
>
> I already looked at all occurrences in the Lisp sources.
Then I really wonder why are you asking all these questions.
> AFAICT, _none_ of those occurrences show how it's used
> in the sense of explaining its effect.
You see the effect as soon as you look at the menus which use it.
> I'm looking for info about its implementation and what
> it actually does - info presumably available in some C
> code. HOW it does what it does.
The HOW is always in the code, so filing a bug about the documentation
is not going to reveal that: we won't describe the implementation in
the documentation.
So I'm closing this bug report.
> See also the question about whether it's used only by
> toolkits. In GUI Emacs on MS Windows, for instance,
> the effect of a separator is a continuous separator
> line, while the effect with `emacs -nw' seems to be a
> pair of hyphen chars.
Each toolkit/UI variant produces its particular visual, but they all
do, and the effect is the same: to visually separate between groups of
menu items.
> > See above. If you really want to see the effect of changing it
> > (why?), I think you will need to rebuild Emacs.
>
> You think so? How about having the doc specify that,
> or whatever the actual behavior is.
I see no reason. You are looking for the kind of internal details
that are always found in the code.
> FWIW, this bug report is a result of seeing this user
> question:
>
> "Is it possible to change the menu separator?"
>
> https://emacs.stackexchange.com/q/62717/105
Not every question means something is wrong with our documentation.
Sometimes the answer is "use the source, Luc".
next prev parent reply other threads:[~2021-01-12 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<73e90890-b70a-4eb8-aa9e-d40959d1e1ec@default>
[not found] ` <<83pn2adwn1.fsf@gnu.org>
2021-01-12 16:34 ` bug#45806: 26.3; `menu-bar-separator' Drew Adams
2021-01-12 17:03 ` Eli Zaretskii [this message]
2021-01-12 18:09 ` Drew Adams
2021-01-12 18:22 ` Eli Zaretskii
2021-01-12 18:23 ` Eli Zaretskii
2021-01-12 0:32 Drew Adams
2021-01-12 15:04 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=835z42dr4j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45806-done@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.