unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Heime <heimeborgia@protonmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Making new files
Date: Sun, 05 May 2024 14:03:39 -0400	[thread overview]
Message-ID: <jwvfruwqhcw.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <H0PU4EDZHZXO18guzx_RAFXE1AaXpG2UcpUFh28CCskwyyU5xoatqhEIY2pS5KLwJiwbYN4SXWjrlUMEtZfiKDytD0nRa41O_arNUy4ITDM=@protonmail.com> (Heime's message of "Sun, 05 May 2024 16:37:22 +0000")

> Will do things a different way, disregarding the existence of "Visit
> New File".

I think before treating people of stupid, I'd advise to understand why
we do things differently from what you're used to, and I get the
impression that you don't understand that yet.

Basically, in Emacs we don't distinguish whether you're opening an
existing file or a new file.  You just `C-x C-f` and then put the name
of the file.  The name of the file tells Emacs where to save backups,
which mode to use, which project it belongs to, etc...

If the user just says "give me a new file buffer", we can't provide
a very good experience because we don't know where this file will be
saved, which project it will belong to, and most importantly which mode
it should use.  LibreOffice has a similar problem so when you ask for
a "new document" it has to prompt you back to choose the kind of
document, which is akin to our major modes, except we have many more
major modes.  Choosing a file name is usually not harder for you than
choosing a major mode, and it gives Emacs more information.


        Stefan




  reply	other threads:[~2024-05-05 18:03 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
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 [this message]
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=jwvfruwqhcw.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=heimeborgia@protonmail.com \
    --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).