From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, drew.adams@oracle.com, juri@linkov.net
Subject: Re: Removal of facemenu preload - Text Properties menu
Date: Tue, 11 May 2021 21:15:10 +0200 [thread overview]
Message-ID: <87eeedkrpd.fsf@gnus.org> (raw)
In-Reply-To: <83mtt13xu1.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 11 May 2021 21:54:46 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Please don't move the Text Properties menu to Enriched -- it has
> nothing special to do with Enriched mode (although users of Enriched
> mode are supposed to use this menu). It is a separate feature that
> can be used independently of Enriched mode.
Sorry; didn't see this until after I moved it. But I think it makes a
lot more sense in the Text menu than in the Edit menu. (Except for the
few items that seem to have nothing to do with text property editing,
like "Display Faces" and "Display Colors", which should perhaps be moved
somewhere else.
> It is, of course, okay to disable/remove it when facemenu isn't
> loaded, provided that loading facemenu enables/adds it back to the
> Edit menu.
I think having it automatically in the Text menu (with enriched mode) is
more helpful than not having it at all in the menu bar -- unless the
user loads facemenu.el.
But I have no strong opinions here -- feel free to move this around as
you wish.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-05-11 19:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 15:27 Removal of facemenu preload - Text Properties menu Drew Adams
2021-05-10 20:57 ` Juri Linkov
2021-05-11 11:57 ` Lars Ingebrigtsen
2021-05-11 15:23 ` [External] : " Drew Adams
2021-05-11 18:12 ` Juri Linkov
2021-05-11 18:49 ` Lars Ingebrigtsen
2021-05-11 18:54 ` Eli Zaretskii
2021-05-11 19:15 ` Lars Ingebrigtsen [this message]
2021-05-11 20:19 ` 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=87eeedkrpd.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
/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).