unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Vladimir Nikishkin <lockywolf@gmail.com>
Cc: 47493@debbugs.gnu.org
Subject: bug#47493: 27.1; auto-save-file-name-transforms with uniquify should not create invalid filenames
Date: Tue, 30 Mar 2021 09:55:26 +0200	[thread overview]
Message-ID: <87ft0d3wk1.fsf@gmx.de> (raw)
In-Reply-To: <877dlpqloo.fsf@delllaptop.lockywolf.net> (Vladimir Nikishkin's message of "Tue, 30 Mar 2021 13:06:40 +0800")

Vladimir Nikishkin <lockywolf@gmail.com> writes:

> Dear Emacs developers,

Hi Vladimir,

> In order to avoid littering my file system with autosaves, I have the
> following setting in my .emacs:
>
> #+begin_src
> (setq auto-save-file-name-transforms '((".*" "~/.emacs.d/autosave/" t)))
> #+end_src
>
> The t flag is the 'uniquify' flag, which roughly means "replace all
> slashes by exclamation marks".
>
> However, this way it is possible to create a file name that is invalid
> for use in the file system tree, especially if the file you are editing
> is deeply nested.

Could you pls show an example of such invalid file name?

> Would it be possible, to, maybe, add a flag "ensure-filesystem-correctness"?

Maybe we could have a flag which means "convert the directory part of a
file name into sha1" (or whatever `secure-hash' provides).

> Your sincerely,
> Vladimir

Best regards, Michael.





  reply	other threads:[~2021-03-30  7:55 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 [this message]
2021-04-06 18:40   ` Michael Albinus
2021-04-06 20:57     ` Glenn Morris
2021-04-07  8:24       ` Michael Albinus
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

  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=87ft0d3wk1.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=47493@debbugs.gnu.org \
    --cc=lockywolf@gmail.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 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).