From: Michael Albinus <michael.albinus@gmx.de>
To: Glenn Morris <rgm@gnu.org>
Cc: Vladimir Nikishkin <lockywolf@gmail.com>, 47493@debbugs.gnu.org
Subject: bug#47493: 27.1; auto-save-file-name-transforms with uniquify should not create invalid filenames
Date: Wed, 07 Apr 2021 10:24:16 +0200 [thread overview]
Message-ID: <877dley027.fsf@gmx.de> (raw)
In-Reply-To: <olsg433zcd.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue, 06 Apr 2021 16:57:54 -0400")
Glenn Morris <rgm@gnu.org> writes:
Hi Glenn,
>> Nobody has commented.
>
> You asked for an example of why this was needed; I was waiting to hear
> the answer.
Same here. However, the docstring of auto-save-file-name-transforms
speaks about the problem, so I believe it is a real one.
>> + 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.
>
> Grammar tweaks:
>
> If UNIQUIFY is one of the members of `secure-hash-algorithms',
> Emacs constructs the nondirectory part of the auto-save file name by
> applying that `secure-hash' to the buffer file name. This avoids any
> risk of excessively long file names.
Thanks!
Best regards, Michael.
next prev parent reply other threads:[~2021-04-07 8:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 5:06 bug#47493: 27.1; auto-save-file-name-transforms with uniquify should not create invalid filenames Vladimir Nikishkin
2021-03-30 7:55 ` Michael Albinus
2021-04-06 18:40 ` Michael Albinus
2021-04-06 20:57 ` Glenn Morris
2021-04-07 8:24 ` Michael Albinus [this message]
2021-05-08 12:34 ` Lars Ingebrigtsen
2021-05-08 12:42 ` Michael Albinus
2021-05-09 9:58 ` Lars Ingebrigtsen
2021-05-10 11:46 ` Michael Albinus
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=877dley027.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=47493@debbugs.gnu.org \
--cc=lockywolf@gmail.com \
--cc=rgm@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 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.