From: Heime <heimeborgia@protonmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Making new files
Date: Sun, 05 May 2024 18:54:42 +0000 [thread overview]
Message-ID: <soc2UwBGlI-97QQXXesD7C9ufpv__GQaaH-w4wVT3Z3AKk8-Qwu0D2hCYfplD7728hjAkMMagfEVK0klJ88v5K5lmVtSTQy9xU2gQ6NnwEs=@protonmail.com> (raw)
In-Reply-To: <jwvfruwqhcw.fsf-monnier+emacs@gnu.org>
On Monday, May 6th, 2024 at 6:03 AM, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> > 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.
You are correct, eventually you can continue with whatever you want.
And I do whatever I want to, some other way.
> 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.
I agree. There must be a misunderstanding because I have not been referring
to "give me a new file buffer". But "give me a new file" which distinguishes
that you are saving a new one (as with "Save As") rather than opening an
existing one.
> 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
next prev parent reply other threads:[~2024-05-05 18:54 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
2024-05-05 18:54 ` Heime [this message]
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='soc2UwBGlI-97QQXXesD7C9ufpv__GQaaH-w4wVT3Z3AKk8-Qwu0D2hCYfplD7728hjAkMMagfEVK0klJ88v5K5lmVtSTQy9xU2gQ6NnwEs=@protonmail.com' \
--to=heimeborgia@protonmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).