From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
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 13:44:39 +0800 [thread overview]
Message-ID: <87tttpx60o.fsf@yahoo.com> (raw)
In-Reply-To: <83sf99ncfi.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 27 Jul 2023 08:36:17 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> 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?
I don't think that the people who need help finding their initialization
files are likely to look there.
Maybe the tutorial could mention the locations where Emacs searches for
initialization files, or we could put a link to the init files on the
splash screen.
> To be fair, the tool bar still has some free space on it.
Not on my phone, where the default tool-bar is about four items away
from wrapping. We certainly can't afford to waste that space on these
items.
> 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?
Other applications don't treat their tool bars as disposal areas for
anything they want to make prominent :-)
On a slightly unrelated note, I think Emacs would be well served by an
interactive tutorial, like the proverbial Clippy from MS Office. It
could be opened from a link on the splash screen.
next prev parent reply other threads:[~2023-07-27 5:44 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
2023-07-27 5:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=87tttpx60o.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=64871@debbugs.gnu.org \
--cc=eliz@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).