unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Heime <heimeborgia@protonmail.com>
To: "జిందం వాఐి" <jindam.vani@disroot.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Making new files
Date: Sun, 05 May 2024 02:28:42 +0000	[thread overview]
Message-ID: <6QTomH9xqgDUMC7MxpjZ5DXmbUAV93KdYUfHGO1uTEtXmKDf1RGgvDziuTnsLo5DUNsJjt-3hG1XzS3pUQh_1kNMuNEAN4i8obW3gOjX7N8=@protonmail.com> (raw)
In-Reply-To: <6be36d13834911de93abf7f8b71d0154@disroot.org>


On Sunday, May 5th, 2024 at 2:09 PM, జిందం వాఐి <jindam.vani@disroot.org> wrote:

> On 2024-05-04 21:38, Heime wrote:
> 
> > Sent with Proton Mail secure email.
> > 
> > On Saturday, May 4th, 2024 at 8:16 PM, Eli Zaretskii eliz@gnu.org
> > wrote:
> > 
> > > > 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".
> > 
> > That's what your stupid minds decided.
> 
> 
> * in opensource packages, its quite
> common, which tests your nerve or
> you are in complete disagreement
> * i didnt remember package name,
> however, on the package website,
> its clearly indicated what and
> what not features they can implement
> * in other words, they are subjective
> * i too felt same way ;)
> * however, once i forced myself
> completely dependant on emacs, i
> fully appreciate benefits of choice
> made by emacs devs about "making
> new file"

Does that mean that you interpret "Find File" as a request to enter the name
of a new file that you want to create ?  How many emacs users interpret things 
this way ?
 
> > One does "Visit New File", to
> > get "Find File" to show up in the "Title Bar". Find file on something
> > that does not exist. "Visiting something that does not exist" !!!
> > I suggest going back to school and relearn the englrish language
> > properly.
> > 
> > "Make New File", not "Visit New File" or any other nonsense you
> > decided.
> > You are creating confusion for benefits of convenience. People do not
> > work like that. Confusion brings more confusion and more confusion.
> > One can get fundamental mode, and a user can change it. Or reload the
> > file and get the mode chosen automatically.
> 
> 
> --
> regards,
> జిందం వాఐి [ jindam, vani ]
> 
> web_ jindam.neocities.org
> [matrix]_ @jindam:oikei.net



  reply	other threads:[~2024-05-05  2:28 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 [this message]
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='6QTomH9xqgDUMC7MxpjZ5DXmbUAV93KdYUfHGO1uTEtXmKDf1RGgvDziuTnsLo5DUNsJjt-3hG1XzS3pUQh_1kNMuNEAN4i8obW3gOjX7N8=@protonmail.com' \
    --to=heimeborgia@protonmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=jindam.vani@disroot.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).