Re: Cygwin is not passing arguments to Windows apps

2023-12-22 Thread Andrey Repin via Cygwin
Greetings, Karl Crary! > I have stumbled on to a fix, but I am still puzzled. The problem arises > when either of the following lines appears in my /etc/fstab: > c: /c ntfs binary,noacl,cygexec,user 0 0 > c: /home ntfs binary,noacl,cygexec,user 0 0 Note that C: is not the same as C:\ > I've

Re: Cygwin is not passing arguments to Windows apps

2023-12-17 Thread Eliot Moss via Cygwin
On 12/17/2023 8:45 AM, Karl Crary wrote: Thank you, but I guess I posted a bad example then. latex --version This is pdfTeX, Version 3.141592653-2.6-1.40.25 (MiKTeX 23.10.12) (preloaded fomat=latex.fmt)  restricted \write18 enabled. ** It should print version information, but instead that

Re: Cygwin is not passing arguments to Windows apps

2023-12-17 Thread Kevin Schnitzius via Cygwin
On Sunday, December 17, 2023 at 09:30:04 AM EST, Karl Crary via Cygwin wrote: > I have stumbled on to a fix, but I am still puzzled. The problem arises > when either of the following lines appears in my /etc/fstab: > > c: /c ntfs binary,noacl,cygexec,user 0 0 > c: /home ntfs

Re: Cygwin is not passing arguments to Windows apps

2023-12-17 Thread Brian Inglis via Cygwin
On 2023-12-17 07:29, Karl Crary via Cygwin wrote: On Sun, Dec 17, 2023 at 8:45 AM Karl Crary wrote: On 12/17/2023 7:29 AM, Eliot Moss wrote: On 12/16/2023 10:55 PM, Karl Crary via Cygwin wrote: I am encountering a bug wherein Cygwin is not passing arguments to most Windows programs (although

Re: Cygwin is not passing arguments to Windows apps

2023-12-17 Thread Karl Crary via Cygwin
I have stumbled on to a fix, but I am still puzzled. The problem arises when either of the following lines appears in my /etc/fstab: c: /c ntfs binary,noacl,cygexec,user 0 0 c: /home ntfs binary,noacl,cygexec,user 0 0 I've taken them out and it's working now, but I'm still puzzled by how those

Re: Cygwin is not passing arguments to Windows apps

2023-12-17 Thread Brian Inglis via Cygwin
On 2023-12-17 06:45, Karl Crary via Cygwin wrote: Thank you, but I guess I posted a bad example then. latex --version This is pdfTeX, Version 3.141592653-2.6-1.40.25 (MiKTeX 23.10.12) (preloaded fomat=latex.fmt)  restricted \write18 enabled. ** It should print version information, but instead

Re: Cygwin is not passing arguments to Windows apps

2023-12-17 Thread Brian Inglis via Cygwin
On 2023-12-17 06:45, Karl Crary via Cygwin wrote: Thank you, but I guess I posted a bad example then. latex --version This is pdfTeX, Version 3.141592653-2.6-1.40.25 (MiKTeX 23.10.12) (preloaded fomat=latex.fmt)  restricted \write18 enabled. ** It should print version information, but

Re: Cygwin is not passing arguments to Windows apps

2023-12-17 Thread Karl Crary via Cygwin
Thank you, but I guess I posted a bad example then. latex --version This is pdfTeX, Version 3.141592653-2.6-1.40.25 (MiKTeX 23.10.12) (preloaded fomat=latex.fmt) restricted \write18 enabled. ** It should print version information, but instead that is what I would expect to see if I ran

Re: Cygwin is not passing arguments to Windows apps

2023-12-17 Thread Eliot Moss via Cygwin
On 12/16/2023 10:55 PM, Karl Crary via Cygwin wrote: Dear all, I am encountering a bug wherein Cygwin is not passing arguments to most Windows programs (although Cygwin programs are doing fine). For example, the following command ought to be dumping a lot of usage information, but instead it

Re: Cygwin is not passing arguments to Windows apps

2023-12-17 Thread ASSI via Cygwin
Karl Crary via Cygwin writes: > I am encountering a bug wherein Cygwin is not passing arguments to > most Windows programs (although Cygwin programs are doing fine). What you are encountering is unlikely a bug in Cygwin. > For example, the following command ought to be dumping a lot of usage >

Cygwin is not passing arguments to Windows apps

2023-12-16 Thread Karl Crary via Cygwin
Dear all, I am encountering a bug wherein Cygwin is not passing arguments to most Windows programs (although Cygwin programs are doing fine). For example, the following command ought to be dumping a lot of usage information, but instead it starts a command prompt, which is what it does when