From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: luangruo@yahoo.com, 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 11:54:33 +0300 [thread overview]
Message-ID: <83bkfxn392.fsf@gnu.org> (raw)
In-Reply-To: <87ila57o10.fsf@localhost> (message from Ihor Radchenko on Thu, 27 Jul 2023 08:32:27 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: Po Lu <luangruo@yahoo.com>, 64871@debbugs.gnu.org
> Date: Thu, 27 Jul 2023 08:32:27 +0000
>
> My instincts from other GUI apps tell me that common places where
> customization staff is located is Options->Preferences,
> Edit->Preferences, or Tools->Preferences.
>
> Options->Customize sounds like something new users would be able to
> find.
"Preferences" would be a silly name in Emacs, because every
customization in Emacs is about "preferences".
> > 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?
>
> "Preferences" gear icon is something I have seen on toolbars.
That's a separate issue and a separate request, though.
> And for init file, it is not a common concept.
Exactly my point. The easy-on-newbies interface for customization is
not to present them with (a largely empty) init file, far from that.
> Another idea could be adding a button that will open init file right
> into customize interface (near "Apply").
Why?
> Side note: I now tried to look into Emacs "preferences" via menu and it
> feels a bit awkward. Options->Customize Emacs-> has "Top-level
> customization group" and "Browse customization groups" do not sound very
> different and I would never guess (even knowing Emacs) that "browse"
> implies short overview of all options.
Did you read the help-echo strings they display?
next prev parent reply other threads:[~2023-07-27 8:54 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
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 [this message]
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=83bkfxn392.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).