Neil Jerram <n...@ossau.homelinux.net> skribis: >> Eli Zaretskii <e...@gnu.org> skribis: >> >>>> From: l...@gnu.org (Ludovic Courtès) >>>> Cc: guile-devel@gnu.org >>>> Date: Thu, 12 Jun 2014 21:48:48 +0200 >>>> >>>> >> >> +(define %null-device >>>> >> >> + ;; On Windows (MinGW), /dev/null does not exist and we must >>>> >> >> instead >>>> >> >> + ;; use NUL. Note that file system procedures automatically >>>> >> >> translate >>>> >> >> + ;; /dev/null, so this variable is only useful for shell snippets. >>>> >> >> + (if (file-exists? "/dev/null") >>>> >> >> + "/dev/null" >>>> >> >> + "NUL")) >>>> >> > >>>> >> > Not sure this is a good idea: I can create a file /dev/null on >>>> >> > Windows, but that doesn't mean it is my null device. >>>> >> >>>> >> Yes, but using %host-type isn’t perfect either, no? What would you >>>> >> prefer? >>>> > >>>> > How about testing if the absolute name of the current directory starts >>>> > with a drive letter? >>>> >>>> Like (string-match "^[a-zA-Z]:[/\\]" (getcwd)) ? >>> >>> Yes. > > But my Git Bash shell on Windows (at work) gives me paths like /<drive > letter>/... > For example: > > nj@PC3946 /c/work/icp (master) > $ pwd > /c/work/icp > > I think that shell is provided by MinGW/MSYS - so does that mean that > the regexp check > above might not be correct in all contexts on Windows?
Isn’t it rather provided by Cygwin? I would think that (getcwd) on Cygwin would return /c/... whereas (getcwd) on MinGW would return C:\..., no? Thanks, Ludo’.
