Re: substitute-in-file-name and "$"

[Michael Albinus]

address@hidden (Kim F. Storm) writes:

> Maybe substitute-in-file-name could put a `substitute-in-file-name'
> property on the return value and check for that property on its
> argument (and do nothing if it is present).
>
> A later call to substitute-in-file-name should then skip over parts of
> its argument string which has that property (and only substitute in
> parts which are not previously substituted.
>
> That is still not completely fool-proof if the result of
> substitute-in-file-name is manipulated in some way which removes the
> property and then later passed to substitute-in-file-name again.

A simpler approach would be: expand environment variables if
possible. Don't worry if you cannot expand.

The masquing with "$$" wouldn't be necessary this case. But I don't
know whether there are other drawbacks with this approach.

Best regards, Michael.