GNU bug report logs - #70725
29.3; dired-do-touch completion

Previous Next

Full log

View this message in rfc822 format

From: Thierry Volpiatto <thievol <at> posteo.net>
To: Andreas Schwab <schwab <at> linux-m68k.org>
Cc: christopher <at> librehacker.com, Eli Zaretskii <eliz <at> gnu.org>, 70725 <at> debbugs.gnu.org, Juri Linkov <juri <at> linkov.net>
Subject: bug#70725: 29.3; dired-do-touch completion
Date: Mon, 06 May 2024 12:25:16 +0000

[Message part 1 (text/plain, inline)]

Andreas Schwab <schwab <at> linux-m68k.org> writes:

> On Mai 06 2024, Thierry Volpiatto wrote:
>
>> The timestamp will be set to a few milliseconds in the past, yes, but is
>> this really a problem?
>
> You can touch a file that you don't own, if you have write permission.
> But you cannot set the time of such a file to an arbitrary value (even
> if that value happens to be the current time).

Thanks.  However this doesn't explain why dired-do-touch uses a
completing-read to complete 0 files, uses a default argument which is
not used with an empty prompt and doesn't fit with the info in prompt
even if the prompt is indeed right because finally the command exit with
current-time.
Also IIUC (I rarely use dired) when touching marked files the last file
will not have the same timestamp as the first.
Currently DEFAULT (if user press M-n) is only useful if one want to
modify timestamp of marked files to same timestamp as current.

All this seems incoherent and confusing.

I have now disabled dired-do-touch in Helm.

-- 
Thierry

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.