Re: Can I find where cygwin is installed (for automation purposes)

2020-04-15 Thread Paul Moore via Cygwin
On Wed, 15 Apr 2020 at 19:31, René Berber via Cygwin wrote: > > On 4/15/2020 1:10 PM, Paul Moore via Cygwin wrote: > > [snip] > > Thanks. Can you explain what the \?? prefix on the Installations > > values is about? I'm nervous that there's something going

Re: Can I find where cygwin is installed (for automation purposes)

2020-04-15 Thread Paul Moore via Cygwin
On Wed, 15 Apr 2020 at 16:54, Marco Atzeri via Cygwin wrote: > > Am 15.04.2020 um 15:29 schrieb Paul Moore via Cygwin: > > On Wed, 15 Apr 2020 at 11:54, Csaba Ráduly via Cygwin > > wrote: > > > >> On my machine, I have a > >> > >> HKEY_LOCAL

Re: Can I find where cygwin is installed (for automation purposes)

2020-04-15 Thread Paul Moore via Cygwin
On Wed, 15 Apr 2020 at 13:43, Thomas Wolff wrote: > >> There's HKCU\Software\Cygwin\Installations, but that seems to use \?? > >> prefixes on the PATH, which I'm not sure how to interpret > Running that script within cygwin? `mount | grep " / "` As I said, I'm trying to find cygwin, so I can't r

Re: Can I find where cygwin is installed (for automation purposes)

2020-04-15 Thread Paul Moore via Cygwin
On Wed, 15 Apr 2020 at 11:54, Csaba Ráduly via Cygwin wrote: > On my machine, I have a > > HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup > > key, which contains a string value named "rootdir" with the date > "C:\cygwin64". Thanks, that looks more useful. I didn't think to check there as I didn't rec

Can I find where cygwin is installed (for automation purposes)

2020-04-15 Thread Paul Moore via Cygwin
I'm trying to write an automation script that works on a number of machines. I know that on all machines Cygwin will be installed, but I cannot guarantee that (1) it will be in the same location on each PC, or (2) that it will be in PATH. There's HKCU\Software\Cygwin\Installations, but that seems

Re: shell expansion produces e.g. "ls: cannot access '*.pdf': No such file or directory" in Windows CMD shell, but works okay in bash

2020-03-22 Thread Paul Moore via Cygwin
Interesting. Maybe codepage-related issues, then. Sorry, I'm out of my depth now, I'll leave it to someone else to diagnose further. On Sun, 22 Mar 2020 at 19:54, Jay Libove wrote: > > Good suggestion, deleting files one by one. It's not just one file, but it > does seem to have something to do

Re: shell expansion produces e.g. "ls: cannot access '*.pdf': No such file or directory" in Windows CMD shell, but works okay in bash

2020-03-22 Thread Paul Moore via Cygwin
Have you tried deleting files one by one, to see if the issue is related to a single file (sorry if this is an obvious suggestion that you've already tried). In Cygwin bash, it's the shell that glob-expands wildcards before calling your program (e.g. ls), and in find, it's the find code that does

Re: shell expansion produces e.g. "ls: cannot access '*.pdf': No such file or directory" in Windows CMD shell, but works okay in bash

2020-03-22 Thread Paul Moore via Cygwin
On Sun, 22 Mar 2020 at 19:11, Marco Atzeri via Cygwin wrote: > any reason for NOT using a cygwin shell ? Many reasons. But that's not relevant to this thread, is it? (Note: I'm not the OP, just an interested contributor to the thread). I'm happy to elaborate if you want, but I suggest we do it

Re: shell expansion produces e.g. "ls: cannot access '*.pdf': No such file or directory" in Windows CMD shell, but works okay in bash

2020-03-22 Thread Paul Moore via Cygwin
Is this because cygwin globbing is (by default) case sensitive? You could set the CYGWIN environment variable to "glob:ignorecase" to get case-insensitive behaviour. Paul On Sun, 22 Mar 2020 at 17:52, Jay Libove via Cygwin wrote: > > I've never seen this before. > In a Windows CMD shell, Cygwin