GNU bug report logs - #47493
27.1; auto-save-file-name-transforms with uniquify should not create invalid filenames

Previous Next

Full log

Message #22 received at 47493 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: Vladimir Nikishkin <lockywolf <at> gmail.com>, 47493 <at> debbugs.gnu.org
Subject: Re: bug#47493: 27.1; auto-save-file-name-transforms with uniquify
 should not create invalid filenames
Date: Sat, 08 May 2021 14:34:14 +0200

Michael Albinus <michael.albinus <at> gmx.de> writes:

>> Maybe we could have a flag which means "convert the directory part of a
>> file name into sha1" (or whatever `secure-hash' provides).
>
> Nobody has commented. Well, in a couple of days I will push the appended
> patch, unless there are objections.

As far as I can tell, the patch wasn't pushed?

> + If the optional element UNIQUIFY is a symbol returned by function
> + `secure-hash-algorithms', the auto-save file name is constructed
> + by taking the directory part of the replaced file-name,
> + concatenated with the buffer file name run through `secure-hash'
> + instead.  This returns a valid name for your filesystem any way.

Vladimir didn't have any examples for invalid file names, apparently,
but it looks like a good change to me.  (I.e., being able to opt in to
using a hash instead of !!-ing.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

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