From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Making new files
Date: Sat, 04 May 2024 11:16:02 +0300 [thread overview]
Message-ID: <86jzkagfgd.fsf@gnu.org> (raw)
In-Reply-To: <CAP_d_8VafMfAnOUhgnt2T5m90UXCK8NY9rpsVqjrY3Ex-9Adfw@mail.gmail.com> (message from Yuri Khan on Sat, 4 May 2024 14:41:50 +0700)
> From: Yuri Khan <yuri.v.khan@gmail.com>
> Date: Sat, 4 May 2024 14:41:50 +0700
> Cc: Heime <heimeborgia@protonmail.com>,
> Heime via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
>
> On Sat, 4 May 2024 at 07:16, Po Lu <luangruo@yahoo.com> wrote:
>
> > > I always struggle in emacs because there is no way to make a new file
> > > from the "File" menu. Can "New File" be added please.
> >
> > "Visit New File."
>
> That’s not exactly what Users New To Emacs™ expect from a File → New command.
But that's what we decided to have instead of "File->New". There were
a lot of discussions about it quite a few years ago, and we ended up
implementing that, for reasons that you can find in the discussion
(there's more here than meets the eye, as usually with Emacs).
So we are not going to change that any time soon. The "New" in "Visit
New File" should tell the user this is what they want, and the
help-echo tooltip should help some more.
> The standard behavior of File → New is to create a blank buffer, no
> questions asked. The decision as to the name and location of the file
> is deferred to the first explicit save. Emacs, on the other hand, asks
> for the name up front.
Emacs is not like "other apps" out there, it has its own logic and
paradigms, which are usually well-thought. Users of Emacs should
realize the value of the Emacs behavior (for example, the fact that in
this case Emacs automatically choses the correct modes for the new
file), and appreciate it, rather than look for the inferior behavior
characteristic of "other apps".
next prev parent reply other threads:[~2024-05-04 8:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 23:57 Making new files Heime
2024-05-04 0:15 ` Po Lu
2024-05-04 7:41 ` Yuri Khan
2024-05-04 8:16 ` Eli Zaretskii [this message]
2024-05-04 16:08 ` Heime
2024-05-04 16:23 ` Eli Zaretskii
2024-05-04 16:40 ` Heime
2024-05-05 2:09 ` జిందం వాఐి
2024-05-05 2:28 ` Heime
2024-05-05 2:53 ` Po Lu
2024-05-05 3:07 ` Heime
2024-05-05 3:18 ` Heime
2024-05-04 22:37 ` Heime
2024-05-05 13:49 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-05-05 16:37 ` Heime
2024-05-05 18:03 ` Stefan Monnier
2024-05-05 18:54 ` Heime
2024-05-05 19:03 ` Heime
2024-05-06 3:12 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-05-06 7:05 ` Stephen Berman
2024-05-06 13:11 ` Stefan Monnier
2024-05-06 13:16 ` Po Lu
2024-05-06 13:34 ` Heime
2024-05-06 14:44 ` Stephen Berman
2024-05-06 16:43 ` Heime
2024-05-06 16:54 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-05-06 17:00 ` Stephen Berman
2024-05-06 13:40 ` Heime
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=86jzkagfgd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).