Re: auto-save-file-name-transforms too simple?

[Stefan Monnier]

> "Eli Zaretskii" <address@hidden> writes:
> 
> > Btw, since this explicitly targets remote files, I think it should run
> > the result of expand-file-name through convert-standard-filename.  The
> > latter is a no-op on Unix and GNU systems, but on Windows and DOS it
> > replaces characters that the underlying filesystem disallows.  Remote
> > file names are likely to suffer from this problem.
> 
> Well, I think the nonstandard filenames are more likely to sit in the
> "\\2" part, and that's only known until much later.
> 
> So maybe the places that _use_ auto-save-file-name-transforms should
> be changed, not the place that _sets_ it.

That's also the case for temporary-file-directory which the
user might want to change.  So I agree that putting it into
auto-save-file-name-transforms is not the right answer unless
we allow an expression on the right-hand side (rather than
just a string passed to replace-match).


        Stefan