Subject: Re: bug#74208: 31.0.50; minibuffer read-file-name-default mutates global value of default-directory incorrectly

From: Madhu <[email-masked]>
Date: Sat, 23 Nov 2024 20:26:10 +0530 (IST)

*  Eli Zaretskii <[email-masked]> <[email-masked]>
Wrote on Sat, 23 Nov 2024 14:25:42 +0200

> Ping! How should we make progress with this issue?

I haven't had a chance to use Stefan's url history code yet to see how
it works, but hopefully i'll get around to it soon.  But I don't think
it is acceptable for call process to fail just because
default-directory is bound to a url. (There are other problems like
bogus invalid entries in file-name-history -- resulting from a merging
a relative pathname to a url) which also argue against setting the
default-url in general (it may make sense in a specific use case)