From: Ihor Radchenko <yantar92@posteo.net>
To: 64871@debbugs.gnu.org
Subject: bug#64871: 30.0.50; [FR] Add command and menu item to open user init file
Date: Wed, 26 Jul 2023 11:04:31 +0000 [thread overview]
Message-ID: <87jzun7x34.fsf@localhost> (raw)
Hello,
From my experience, many new Emacs users have difficulties adding
things to their init file. Especially on Windows.
I have seen people being stuck when asked to "add some Elisp snippet to
config". They do not fully understand how to open that "config".
In some instances, users just created init.el in some random directory,
modified it, and then got confused why the config is not affecting
anything.
I think that it would be nice to provide an easily accessible command
that opens init.el or creates a new one, if not exists yet.
The command should obviously be available via M-x and maybe also via
menu and toolbar.
WDYT?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next reply other threads:[~2023-07-26 11:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 11:04 Ihor Radchenko [this message]
2023-07-27 1:09 ` bug#64871: 30.0.50; [FR] Add command and menu item to open user init file 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
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=87jzun7x34.fsf@localhost \
--to=yantar92@posteo.net \
--cc=64871@debbugs.gnu.org \
/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).