From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: yantar92@posteo.net, 64871@debbugs.gnu.org
Subject: bug#64871: 30.0.50; [FR] Add command and menu item to open user init file
Date: Thu, 27 Jul 2023 08:36:17 +0300 [thread overview]
Message-ID: <83sf99ncfi.fsf@gnu.org> (raw)
In-Reply-To: <871qguxirf.fsf@yahoo.com> (bug-gnu-emacs@gnu.org)
> Cc: 64871@debbugs.gnu.org
> Date: Thu, 27 Jul 2023 09:09:24 +0800
> From: Po Lu via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> Ihor Radchenko <yantar92@posteo.net> writes:
>
> > The command should obviously be available via M-x and maybe also via
> > menu
>
> The global menu bar is already overflowing, so let's not add any more
> items to the Edit, Options, Buffers or Tools menus.
Before concluding that this suggestion will cause trouble to the
over-crowded menu bar, we should talk about where this new items might
be placed. If we place it in an existing sub-menu, then the problems
it will cause might not be that grave. For example, how about the
Options->Customize Emacs sub-menu?
> The Emacs manual holds a description of the location of user
> initialization files.
In a 55-line subsection, plus another 54-line section in the
Appendices that describes the Windows-specific quirks!
> > and toolbar.
>
> No!
>
> Adding that item to the tool bar would increase its (limited) size and
> defeat its purpose of holding frequently used editing operations,
> relegating its role to that of a dumping ground for miscellany.
To be fair, the tool bar still has some free space on it. But I
actually wonder about something else: what other applications have a
tool-bar button to access the init file, or even just the
customization menu?
next prev parent reply other threads:[~2023-07-27 5:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 11:04 bug#64871: 30.0.50; [FR] Add command and menu item to open user init file Ihor Radchenko
2023-07-27 1:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-27 5:36 ` Eli Zaretskii [this message]
2023-07-27 5:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-27 6:19 ` Eli Zaretskii
2023-07-27 12:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-27 12:48 ` Eli Zaretskii
2023-07-27 8:32 ` Ihor Radchenko
2023-07-27 8:54 ` Eli Zaretskii
2023-07-27 9:08 ` Ihor Radchenko
2023-07-27 9:50 ` Eli Zaretskii
2023-07-28 8:09 ` Ihor Radchenko
2023-07-28 12:03 ` Eli Zaretskii
2023-07-28 12:24 ` Ihor Radchenko
2023-07-28 12:43 ` Eli Zaretskii
2023-07-28 12:47 ` Ihor Radchenko
2023-07-28 14:15 ` Drew Adams
2023-08-03 8:08 ` Eli Zaretskii
2023-08-03 8:36 ` Ihor Radchenko
2023-08-03 9:07 ` 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=83sf99ncfi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64871@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=yantar92@posteo.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).