From: "Clément Pit--Claudel" <clement.pit@gmail.com>
To: 24150@debbugs.gnu.org
Subject: bug#24150: 25.1.50; New command: dired-create-empty-file
Date: Thu, 4 Aug 2016 09:54:11 -0400 [thread overview]
Message-ID: <73fd10e8-726d-adbb-20e4-8bdbc52b021e@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1608042223340.11938@calancha-pc>
[-- Attachment #1.1: Type: text/plain, Size: 1840 bytes --]
On 2016-08-04 09:25, Tino Calancha wrote:
> Hi all,
Hi Tino,
> It might be useful having a Dired command creating
> an empty file with a name provided by the user; something
> like 'dired-create-directory' ('+') but for files.
Neat idea; that's like `touch', right?
> Following patch propose a new command 'dired-create-empty-file'
> bound to 'M-+'.
I've added comments inline below.
> +@kindex M-+ @r{(Dired)}
> +@findex dired-create-empty-file
> + The command @kbd{M-+} (@code{dired-create-empty-file}) reads a
> +file name, and creates an empty file with that name. It signals
> +an error if the file already exists.
Ah, so it's different from touch. Is there already a command in dired that sets the access and modification time of a file? If not, maybe this command could do it? I'm not sure it's useful to have the command fail if the file exists. If you go that, maybe renaming the command to eg dired-touch would be useful? Although I see the parallel with dired-create-directory, so maybe it's fine.
> +++
> +*** A new command 'dired-create-empty-file' similar as
> +'dired-create-directory' but it creates a new empty file;
> +bound to 'M-+'.
I think there's a slight problem with this sentence. Maybe
*** New command 'dired-create-empty-file' (similar to
'dired-create-directory') creates a new empty file;
bound to 'M-+'.
> +(defmacro dired--create-empty-file-or-directory (fname &optional create-file)
> + "Create an empty file or directory called FNAME.
> +If FNAME already exists, signal an error.
> +Optional arg CREATE-FILE if non-nil, then create a file. Otherwise create
> +a directory. "
Do you think this could be a defun instead of a macro?
> + (define-key map "\M-+" 'dired-create-empty-file)
Is there a convention on using (kbd "M-+") vs "\M-+"?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-04 13:54 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 [this message]
2016-08-04 16:29 ` Leo Liu
2016-08-04 17:13 ` Ted Zlatanov
2016-08-04 17:29 ` Drew Adams
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
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=73fd10e8-726d-adbb-20e4-8bdbc52b021e@gmail.com \
--to=clement.pit@gmail.com \
--cc=24150@debbugs.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).