unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 20:29:48 +0800	[thread overview]
Message-ID: <87h6ppwn9f.fsf@yahoo.com> (raw)
In-Reply-To: <83lef1naev.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 27 Jul 2023 09:19:52 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> Are people who want to customize Emacs likely to use the
> Options->Customize Emacs menu?  If yes, why not have this one
> additional item there?  If no, why do we have that menu at all?

Users who need to customize Emacs don't necessarily need help to find
their initialization files.

> So we are now using a smartphone as the reference platform for making
> UI decisions?  Smartphones might need a whole new approach to the
> Emacs UI, and a bunch of very different UI decisions.  They should not
> dictate what our UI looks like on desktop and laptop machines.

Actually, the amount of horizontal display area available on smartphones
tends to reflect that of low-resolution desktop displays and computer
terminals.  Emacs UI currently works well on either.

> When did you last look at modern word processors and their tool bars?
> They are, in fact, much more crowded than ours.

Nevertheless, each of those items is used frequently enough to justify
their placement there.  ``Open the configuration file'' is not, at least
in Emacs.

> We decided it would be a good idea long ago, and are since waiting for
> Someone™ to actually make that happen.  IMNSHO, this is more important
> than having Emacs run on Android (hint, hint).

Well, I need the latter, but not the former.  So I'm currently more
inclined to make the latter happen, sorry :)





  reply	other threads:[~2023-07-27 12:29 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 [this message]
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=87h6ppwn9f.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).