Re: Shell completion on w32 uses "/" instead of "\"

[Lennart Borgman]

Stefan Monnier wrote:
> > Anywhere.  The point is that those variables may change during the time
> > the interactive shell exists (or perhaps a non-interactive shell).
> > In this case I noticed it because the file completion code needs to know
> > the value of shell-file-name.
> >     
>
> Hmm... interesting, I didn't think of this case.
>
>   
> > If shell-file-name is set globally somewhere to something different from
> > that in the shell buffer things may fail (as they did here).  I hope I am
> > clear enough.
> >     
>
> Other than when the user changes the configuration (which shouldn't happen
> all the time), when/why would shell-file-name change during the lifetime of
> an interactive shell-mode buffer?
> Or alternatively, why would the user regularly change the global setting of
> shell-file-name?
>
>   

The user might be testing new configurations for example and thereby 
changing shell-file-name (which now has only a global value). Since w32 
is not that simple when it comes to shell that is a very likely 
situation, at least when the user has learned a bit more about emacs.

Another possibility is that you want to use Cygwin or MSYS for 
interactive inferior shells, but use the gnuwin32 tools with cmdproxy 
otherwise.

Of course there is no problem unless you changes shell-file-name, but if 
you there is definitively a problem today. I think a buffer local value 
is needed, but as I pointed out in another message another name is 
needed for the buffer local value (a make-variable-buffer-local var).