|
From: | Lennart Borgman |
Subject: | Re: Shell completion on w32 uses "/" instead of "\" |
Date: | Fri, 22 Dec 2006 00:02:55 +0100 |
User-agent: | Thunderbird 1.5.0.9 (Windows/20061207) |
Stefan Monnier wrote:
Why not set (buffer-locally) a different variable (such as "shell-uses-backslashes") when starting the inferior process? That seems more inline with what we usually do, rather than make a global variable buffer-local because we later (re)compute something that depends on the value the global variable had when the buffer was created.Because we must check that value with for example w32-shell-dos-semantics.Huh? Which code uses w32-shell-dos-semantics?
For example the code for file name completion should IMO use this. But could there not be other situations too? That is why I argue to have w32-shell-dos-semantics check a buffer local variable.
I don't understand. I expected to use w32-shell-dos-semantics to set shell-uses-backslashes and then to use shell-uses-backslashes to decide whether completion should use / or \.
Yes, it is essentially the same thing as I tried to say in this case. Sorry if I was unclear.
[Prev in Thread] | Current Thread | [Next in Thread] |