all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Ted Zlatanov <tzz@lifelogs.com>, Leo Liu <sdl.web@gmail.com>
Cc: 24150@debbugs.gnu.org
Subject: bug#24150: 25.1.50; New command: dired-create-empty-file
Date: Thu, 4 Aug 2016 10:29:21 -0700 (PDT)	[thread overview]
Message-ID: <10da683c-767f-40cf-bef9-ba7f6b6740ea@default> (raw)
In-Reply-To: <87d1locv97.fsf@lifelogs.com>

> I use dired+ and find `diredp-touch-this-file' useful sometimes. It
> might be handy to have that available, with filename prompting, in the
> core dired. But it's not a high-frequency command for me.

Vanilla Emacs has `dired-do-touch', which is bound to `T'
by default.

Dired+ defines `diredp-touch-this-file', which just does
`dired-do-touch' on the file of the current line:
(dired-do-touch 1).

Just `T', with no files marked, gives you the same behavior
as `diredp-touch-this-file'.  The latter is a separate command
because it lets you touch (just) the current file regardless of
whether some files are marked.

Wrt this thread: The Dired touch commands are useful mainly for
updating the file-modified date.  But they do not read a file
name, so they cannot be used to create a new, empty file.

I'm not sure what the use cases are for creating a new, empty file,
but I don't think that using a touch command on any file listed in
Dired has the effect of creating another, new file.  You can use
`M-!' to run a `touch' operating-system command, of course, but
Dired does not currently offer anything for this, AFAIK.





  reply	other threads:[~2016-08-04 17:29 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04 13:25 bug#24150: 25.1.50; New command: dired-create-empty-file Tino Calancha
2016-08-04 13:54 ` Clément Pit--Claudel
2016-08-04 16:29 ` Leo Liu
2016-08-04 17:13   ` Ted Zlatanov
2016-08-04 17:29     ` Drew Adams [this message]
2016-08-05  6:03 ` Tino Calancha
2016-08-05 14:48   ` Drew Adams
2016-08-06 12:38     ` Tino Calancha
2016-08-05  6:07 ` Tino Calancha
2017-05-03  8:23 ` Tino Calancha
2017-07-03  4:51 ` bug#24150: 26.0.50; " Tino Calancha
2017-07-03 14:24   ` Eli Zaretskii
2017-07-03 15:04     ` Tino Calancha
2017-07-03 16:33       ` Eli Zaretskii
2017-07-03 20:18         ` Thien-Thi Nguyen
2017-07-07 13:13         ` Ted Zlatanov
2017-07-07 13:17           ` Drew Adams
2017-07-07 13:31             ` Ted Zlatanov
2017-07-03 15:12     ` Drew Adams
2017-07-05 18:28   ` Eli Zaretskii
2017-07-05 19:34     ` Drew Adams
2017-07-07  5:36       ` Tino Calancha
2017-07-07 11:11         ` Drew Adams
2018-07-10  7:01           ` Tino Calancha
2018-07-10  7:42             ` Phil Sainty
2018-07-17  7:39               ` Tino Calancha
2018-07-20  9:03                 ` Eli Zaretskii
2018-07-23  3:57                   ` Tino Calancha
2018-07-27  8:39                     ` Eli Zaretskii
2018-07-31  4:47                       ` Tino Calancha
2018-07-31 16:20                         ` Eli Zaretskii
2018-08-01  5:16                           ` Tino Calancha
2018-08-01  6:24                             ` Eli Zaretskii
2018-08-01  7:13                               ` Tino Calancha
2018-08-01  8:56                                 ` Eli Zaretskii
2018-08-01  9:31                                   ` Tino Calancha
2018-08-01 11:45                                     ` Eli Zaretskii
2018-08-02  4:34                                       ` Tino Calancha

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=10da683c-767f-40cf-bef9-ba7f6b6740ea@default \
    --to=drew.adams@oracle.com \
    --cc=24150@debbugs.gnu.org \
    --cc=sdl.web@gmail.com \
    --cc=tzz@lifelogs.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.