unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Heime <heimeborgia@protonmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	Stephen Berman <stephen.berman@gmx.net>,
	Stefan Monnier via Users list for the GNU Emacs text editor
	<help-gnu-emacs@gnu.org>
Subject: Re: Making new files
Date: Mon, 06 May 2024 13:40:11 +0000	[thread overview]
Message-ID: <dSTdIqdKdD_oLG4WyLWwTiRW-ti4vtuLgPArQ608WBPDK-9KdkKJvP9rNO9lb-99615tsUDQvLAyrgAWLsTnuP4bDQ-2bgiqYjVS9LqTe44=@protonmail.com> (raw)
In-Reply-To: <87le4n3wsq.fsf@yahoo.com>






Sent with Proton Mail secure email.

On Tuesday, May 7th, 2024 at 1:16 AM, Po Lu <luangruo@yahoo.com> wrote:

> Stefan Monnier monnier@iro.umontreal.ca writes:
> 
> > > > Then, no we don't have a command specifically dedicated to creating new
> > > > empty files (contrary to the command line which has `touch` for that).
> > > 
> > > There's `dired-create-empty-file'...
> > 
> > Well, I'll be damned!
> > 
> > Thanks, Steve!
> 
> 
> There was always "M-! touch", as well.

To looks that it is useful for being included in dired,
but not directly in the File Menu.  Because somebody 
decided that is rarely used.  It is never used actually,
also I don't use it.  But mainly because such possibility
does not exist.




      parent reply	other threads:[~2024-05-06 13:40 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
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 [this message]

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='dSTdIqdKdD_oLG4WyLWwTiRW-ti4vtuLgPArQ608WBPDK-9KdkKJvP9rNO9lb-99615tsUDQvLAyrgAWLsTnuP4bDQ-2bgiqYjVS9LqTe44=@protonmail.com' \
    --to=heimeborgia@protonmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=stephen.berman@gmx.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.
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).