Re: cygpath 3.3.4 : incorrect windows to unix path conversions

Hello, Thank you for the information, this helped me formulate a solution. Best, - TTimo On Tue, Jun 28, 2022 at 10:20 AM Andrey Repin wrote: > Greetings, Timothee Besset! > > > Hello, > > > We are seeing some odd behavior from cygpath.exe when it is copied and > used > > outside the normal

Re: cygpath 3.3.4 : incorrect windows to unix path conversions

On Tue, Jun 28, 2022 at 1:46 AM Timothee Besset wrote: > > Hello, > > We are seeing some odd behavior from cygpath.exe when it is copied and used > outside the normal cygwin installation directory: > Don't do this if you just need to convert Linux style file paths to windows file paths. Use the

Re: cygpath 3.3.4 : incorrect windows to unix path conversions

On Tue, 28 Jun 2022 09:44:56 +0200 Timothee Besset wrote: > We are seeing some odd behavior from cygpath.exe when it is copied and used > outside the normal cygwin installation directory: > > PS C:\Users\ttimo> C:\cygwin64\bin\cygpath.exe -a -u "C:" > /cygdrive/c > > After copying cygpath.exe

Re: cygpath 3.3.4 : incorrect windows to unix path conversions

Greetings, Timothee Besset! > Hello, > We are seeing some odd behavior from cygpath.exe when it is copied and used > outside the normal cygwin installation directory: > PS C:\Users\ttimo> C:\cygwin64\bin\cygpath.exe -a -u "C:" > /cygdrive/c To begin with, "C:" means "current working directory

Re: cygpath gives no output, cygwin 3.3.4

Il giorno mer 11 mag 2022 alle ore 09:54 Daniel Krumlinde Lundvall via Cygwin ha scritto: > So far everything seems o be working except for cygpath, which gives us no > ouput. > > I had a similar problem and the real problem was SentinelOne that broke cygpath and other binaries. Did you try

Re: cygpath not doing anything on a fresh install

On 08.02.2022 17:04, Antonio Petrelli wrote: Il giorno mar 8 feb 2022 alle ore 15:57 Ken Brown ha scritto: I suspect that SentinelOne is interfering with Cygwin (see https://cygwin.com/faq/faq.html#faq.using.bloda). Can you disable it or at least exclude the Cygwin directory from whatever

Re: cygpath not doing anything on a fresh install

Il giorno mar 8 feb 2022 alle ore 15:57 Ken Brown ha scritto: > On 2/8/2022 9:37 AM, Antonio Petrelli wrote: > > Il giorno mar 8 feb 2022 alle ore 15:30 marco atzeri < > marco.atz...@gmail.com> > > ha scritto: > >> check if strace give some hints > >> > >>strace -o /tmp/strace.txt

Re: cygpath not doing anything on a fresh install

On 2/8/2022 9:37 AM, Antonio Petrelli wrote: Il giorno mar 8 feb 2022 alle ore 15:30 marco atzeri ha scritto: check if strace give some hints strace -o /tmp/strace.txt /usr/bin/cygpath --help The result is here: https://pastebin.com/n56RTAiu This looks suspicious: Process 2480 loaded

Re: cygpath not doing anything on a fresh install

Il giorno mar 8 feb 2022 alle ore 15:30 marco atzeri ha scritto: > On Tue, Feb 8, 2022 at 3:24 PM Antonio Petrelli wrote: > > > > Il giorno mar 8 feb 2022 alle ore 15:19 marco atzeri ha scritto: > >> > >> > > > I just installed cygwin on my Windows 10 laptop. > >> > > > I need to use the

Re: cygpath not doing anything on a fresh install

On Tue, Feb 8, 2022 at 3:24 PM Antonio Petrelli wrote: > > Il giorno mar 8 feb 2022 alle ore 15:19 marco atzeri ha scritto: >> >> > > > I just installed cygwin on my Windows 10 laptop. >> > > > I need to use the cygpath utility and it simply does not do anything, >> > > even >> > > > cygpath

Re: cygpath not doing anything on a fresh install

Il giorno mar 8 feb 2022 alle ore 15:19 marco atzeri ha scritto: > > > > I just installed cygwin on my Windows 10 laptop. > > > > I need to use the cygpath utility and it simply does not do anything, > > > even > > > > cygpath --help > > > > does anything. > > > > > > > What should I do? > > > >

Re: cygpath not doing anything on a fresh install

On Tue, Feb 8, 2022 at 3:06 PM Antonio Petrelli wrote: > > Il giorno mar 8 feb 2022 alle ore 13:35 Andrey Repin > ha scritto: > > > > I just installed cygwin on my Windows 10 laptop. > > > I need to use the cygpath utility and it simply does not do anything, > > even > > > cygpath --help > > >

Re: cygpath not doing anything on a fresh install

Il giorno mar 8 feb 2022 alle ore 13:35 Andrey Repin ha scritto: > > I just installed cygwin on my Windows 10 laptop. > > I need to use the cygpath utility and it simply does not do anything, > even > > cygpath --help > > does anything. > > > What should I do? > > Make sure cygwin1.dll is there.

Re: cygpath not doing anything on a fresh install

Greetings, Antonio Petrelli! > Hello > I just installed cygwin on my Windows 10 laptop. > I need to use the cygpath utility and it simply does not do anything, even > cygpath --help > does anything. > What should I do? Make sure cygwin1.dll is there. Some "antivirus" may have eaten it. --

Re: cygpath and star character

On Jul 14 15:26, Ken Brown via Cygwin wrote: > On 7/14/2021 4:10 AM, Tomas Jura via Cygwin wrote: > > Hi > > > > I found a strange behaviour of the program cygpath program > > > > 0 >cygpath -w "./*/*"   <--- IMHO wrong output > >  \ > > > > 0 >cygpath -w "./*/*"  | od -a   

Re: cygpath and star character

On 15/07/2021 00:07, Tomas Jura via Cygwin wrote: Hi My use case is building the CLASSPATH environment variable for java. Like: export CLASSPATH="${CLASSPATH}${PATH_SEPARATOR}$(cygpath -w 'my/java/jar/directory/*' )" CLASSPATH can contain the star character at the end on Windows. Example

Re: cygpath and star character

Hi My use case is building the CLASSPATH environment variable for java. Like: export CLASSPATH="${CLASSPATH}${PATH_SEPARATOR}$(cygpath -w 'my/java/jar/directory/*' )" CLASSPATH can contain the star character at the end on Windows. Example C:\Apps\java\lib\* , which means something different

Re: cygpath and star character

On 7/14/2021 4:10 AM, Tomas Jura via Cygwin wrote: Hi I found a strange behaviour of the program cygpath program 0 >cygpath -w "./*/*"   <--- IMHO wrong output  \ 0 >cygpath -w "./*/*"  | od -a   <--- a detailed dump 000   o nul   *   \   o nul   *  nl 010

Re: cygpath -w space becomes line breaks?

Greetings, 斟酌鵬兄! Please no top-posting in the list. > On Sun, Nov 1, 2020 at 11:39 PM Achim Gratz wrote: >> >> > Is this intended or am I misconfiguring something? >> >> You have to quote any arguments that may contain spaces in the shell, >> else they get parsed as separate words and later

Re: cygpath -w space becomes line breaks?

Ooooh thanks I do it like cygpath -w "`pwd`" and now it works now. On Sun, Nov 1, 2020 at 11:39 PM Achim Gratz wrote: > > > Is this intended or am I misconfiguring something? > > You have to quote any arguments that may contain spaces in the shell, > else they get parsed as separate words and

Re: cygpath -w space becomes line breaks?

> Is this intended or am I misconfiguring something? You have to quote any arguments that may contain spaces in the shell, else they get parsed as separate words and later interpreted as separate arguments to cygpath. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk

Re: cygpath -u converts quoted UNC paths to local

Greetings, Corinna Vinschen! > On Apr 3 19:20, Andrey Repin wrote: >> Greetings, All! >> >> This can be considered "working by design", but it really imposes some >> serious >> restrictions on interoperability with Cygwin, that I think can be avoided. >> >> ... >> >> After some further

Re: cygpath -u converts quoted UNC paths to local

On 2019-04-03 12:20 pm, Andrey Repin wrote: Greetings, All! This can be considered "working by design", but it really imposes some serious restrictions on interoperability with Cygwin, that I think can be avoided. ... After some further testing, this seems to be affecting IP-based UNC

RE: EXT: Re: cygpath -u converts quoted UNC paths to local

esday, April 03, 2019 1:12 PM > To: cygwin@cygwin.com > Subject: EXT: Re: cygpath -u converts quoted UNC paths to local > > Andrey Repin writes: > > This can be considered "working by design", but it really imposes some > > serious restrictions on interoperabi

Re: cygpath -u converts quoted UNC paths to local

Andrey Repin writes: > This can be considered "working by design", but it really imposes some serious > restrictions on interoperability with Cygwin, that I think can be avoided. But cygpath never sees the quotes, so whatever is done to the path that it gets is actually the work of your shell.

Re: cygpath -u converts quoted UNC paths to local

On Apr 3 19:20, Andrey Repin wrote: > Greetings, All! > > This can be considered "working by design", but it really imposes some serious > restrictions on interoperability with Cygwin, that I think can be avoided. > > ... > > After some further testing, this seems to be affecting IP-based UNC

RE: cygpath compatiblity break (v2.1 -> v2.7)

From: Chevallier Yves > ... > So two questions in this thread: > 1. How can I participate to the thread and use this mailing list properly? > ... > From: Brian Inglis > ... > Looks like the 207653 comes from the Return-Path header when > you view the raw message content. The answer

Re: cygpath compatiblity break (v2.1 -> v2.7)

On 10/05/2017 14:35, Chevallier Yves wrote: I don't want to suscribe to it, I just want to be able to post and reply not more. Or you subscribe or you use a NNTP gateway. https://cygwin.com/news.html There are no other way. There is no issue tracker for Cygwin. This is not very

Re: cygpath compatiblity break (v2.1 -> v2.7)

 Next] [Thread Prev] [Thread Next] Other format: [Raw text] Re: cygpath compatiblity break (v2.1 -> v2.7) . From: Marco Atzeri . To: cygwin at cygwin dot com . Date: Wed, 10 May 2017 11:29:32 +0200 . Subject: Re: cygpath compatiblity break (v2.1 -> v2.7) . Authentication-results: sourceware.org

Re: cygpath compatiblity break (v2.1 -> v2.7)

On 10/05/2017 11:12, Chevallier Yves wrote: Unfortunately I haven't tried 2.8 because we've already validated 2.7 internally and I would need at least 3 months to access to 2.8. That said I searched for a release note with information about cygpath, but I haven't find any. Bottom Post in

RE: cygpath compatiblity break (v2.1 -> v2.7)

[mailto:marco.atz...@gmail.com] Sent: mercredi 10 mai 2017 09:14 To: cygwin@cygwin.com Cc: Chevallier Yves <ychevall...@etel.ch> Subject: Re: cygpath compatiblity break (v2.1 -> v2.7) On 10/05/2017 08:00, Chevallier Yves wrote: > Dear All, > > I tried to understand how the mailing list work, but

Re: cygpath compatiblity break (v2.1 -> v2.7)

On 10/05/2017 08:00, Chevallier Yves wrote: Dear All, I tried to understand how the mailing list work, but I cannot find any thread number or message number from the following. Moreover we haven't discussed my issue with `cygpath` which is a serious compatibility break in my toolchain.

Re: cygpath compatiblity break (v2.1 -> v2.7)

at cygwin dot com Date: Wed, 26 Apr 2017 10:37:34 -0600 Subject: Re: cygpath compatiblity break (v2.1 -> v2.7) Authentication-results: sourceware.org; auth=none References: <caa65n5wf9ri_igb1oscx9deg6rttytvhyukfq012dpqmbdz...@mail.gmail.com> <0d835e9b9cd07f40a48423f80d3b5a704bc07...@

Re: cygpath compatiblity break (v2.1 -> v2.7)

On 2017-04-26 09:20, cyg Simple wrote: > On 4/25/2017 9:51 PM, Brian Inglis wrote: >> On 2017-04-25 19:12, Brian Inglis wrote: >>> On 2017-04-25 03:16, Andrew Schulman wrote: > From: Yves Chevallier >> How can I use this mailing list to answer a mail that I >> only find from this link

RE: cygpath compatiblity break (v2.1 -> v2.7)

From: cyg Simple > I was going to state the same yesterday but I gave it a try first. The > resulting mail doesn't explain the use of cygwin-get.MSGID that I saw. > It mostly refers to the FAQ on cygwin.com. Well, there is the following. Not saying it is easy to find.

Re: cygpath compatiblity break (v2.1 -> v2.7)

On 4/25/2017 9:51 PM, Brian Inglis wrote: > On 2017-04-25 19:12, Brian Inglis wrote: >> On 2017-04-25 03:16, Andrew Schulman wrote: From: Yves Chevallier > How can I use this mailing list to answer a mail that I only > find from this link >

Re: cygpath compatiblity break (v2.1 -> v2.7)

On 2017-04-25 19:12, Brian Inglis wrote: > On 2017-04-25 03:16, Andrew Schulman wrote: >>> From: Yves Chevallier How can I use this mailing list to answer a mail that I only find from this link https://www.cygwin.com/ml/cygwin/2017-04/msg00156.html? >>> Send a plain-text e-mail to

Re: cygpath compatiblity break (v2.1 -> v2.7)

On 2017-04-25 03:16, Andrew Schulman wrote: >> From: Yves Chevallier >>> How can I use this mailing list to answer a mail that I only >>> find from this link >>> https://www.cygwin.com/ml/cygwin/2017-04/msg00156.html? >> Send a plain-text e-mail to cygwin-get.207...@cygwin.com. No need >> to add

Re: cygpath compatiblity break (v2.1 -> v2.7)

> From: Yves Chevallier > > ... > > How can I use this mailing list to answer a mail that I only find from > > this [link](https://www.cygwin.com/ml/cygwin/2017-04/msg00156.html)? > > ... > > Send a plain-text e-mail to cygwin-get.207...@cygwin.com. No need to add > a subject or body. It will

RE: cygpath compatiblity break (v2.1 -> v2.7)

From: Yves Chevallier > ... > How can I use this mailing list to answer a mail that I only find from > this [link](https://www.cygwin.com/ml/cygwin/2017-04/msg00156.html)? > ... Send a plain-text e-mail to cygwin-get.207...@cygwin.com. No need to add a subject or body. It will send you the

Re: cygpath compatiblity break (v2.1 -> v2.7)

Well, I don't have the same behavior and I have the latest version of `cygpath.exe` according to my setup: $ cd / $ mkdir foo $ touch foo.exe $ cygpath -w foo foo $ cd foo $ touch foo.exe $ cygpath -w foo foo.exe $ cygpath --version cygpath (cygwin) 2.8.0 Path Conversion Utility Copyright

Re: cygpath compatiblity break (v2.1 -> v2.7)

On 13/04/2017 14:34, Chevallier Yves wrote: I get a very different behaviour with `cygpath` after I upgrade my version of Cygwin. Why? and how can I fix it? With Cygwin 2.7: ``` $ uname -a CYGWIN_NT-6.1-WOW CPT 2.7.0(0.306/5/3) 2017-02-12 13:13 i686 Cygwin $ cygpath --version cygpath (cygwin)

Re: cygpath compatiblity break (v2.1 -> v2.7)

On 13. 4. 2017 16:24, David Macek wrote: > On 13. 4. 2017 14:34, Chevallier Yves wrote: >> I get a very different behaviour with `cygpath` after I upgrade my version >> of Cygwin. Why? and how can I fix it? >> >> With Cygwin 2.7: >> >> ``` >> $ uname -a >> CYGWIN_NT-6.1-WOW CPT 2.7.0(0.306/5/3)

Re: cygpath compatiblity break (v2.1 -> v2.7)

On 13. 4. 2017 14:34, Chevallier Yves wrote: > I get a very different behaviour with `cygpath` after I upgrade my version of > Cygwin. Why? and how can I fix it? > > With Cygwin 2.7: > > ``` > $ uname -a > CYGWIN_NT-6.1-WOW CPT 2.7.0(0.306/5/3) 2017-02-12 13:13 i686 Cygwin > $ cygpath --version

Re: cygpath compatiblity break (v2.1 -> v2.7)

On 4/13/2017 10:02 AM, Eric Blake wrote: > On 04/13/2017 08:59 AM, cyg Simple wrote: > > [an unreadable encrypted message] > > You may want to fix your email settings; encrypted messages should > generally not be used when sending to a mailing list. > Sorry, Enigmail settings must have changed

Re: cygpath compatiblity break (v2.1 -> v2.7)

On 04/13/2017 08:59 AM, cyg Simple wrote: [an unreadable encrypted message] You may want to fix your email settings; encrypted messages should generally not be used when sending to a mailing list. -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266

Re: cygpath compatiblity break (v2.1 -> v2.7)

binD9fTojUuRq.bin Description: PGP/MIME version identification encrypted.asc Description: OpenPGP encrypted message

Re: cygpath (reprised)

On 3/1/2017 8:12 AM, Andrey Repin wrote: > Greetings, cyg Simple! > >> On 2/25/2017 8:13 PM, Andrey Repin wrote: >>> Greetings, cyg Simple! >>> Also a : isn't a valid character for a name in Windows. Cygwin uses some magic to represent it in UNICODE format though. >>> >>> It isn't a

Re: cygpath (reprised)

Greetings, cyg Simple! > On 2/25/2017 8:13 PM, Andrey Repin wrote: >> Greetings, cyg Simple! >> >>> Also a : isn't a valid character for a name in Windows. Cygwin uses >>> some magic to represent it in UNICODE format though. >> >> It isn't a valid file "name" character, yes, but it is still a

Re: cygpath (reprised)

On 2/27/2017 9:03 AM, Nellis, Kenneth (Conduent) wrote: > From: cyg Simple >> On 2/21/2017 1:22 PM, Nellis, Kenneth (Conduent) wrote: >>> I suppose one could argue that, by using -w, that cygpath might assume that >>> it >>> is converting *from* a POSIX path, and therefore the colon would not

Re: cygpath (reprised)

On 2/25/2017 8:13 PM, Andrey Repin wrote: > Greetings, cyg Simple! > >> Also a : isn't a valid character for a name in Windows. Cygwin uses >> some magic to represent it in UNICODE format though. > > It isn't a valid file "name" character, yes, but it is still a meaningful > character in

RE: cygpath (reprised)

From: cyg Simple > On 2/21/2017 1:22 PM, Nellis, Kenneth (Conduent) wrote: > > I suppose one could argue that, by using -w, that cygpath might assume that > > it > > is converting *from* a POSIX path, and therefore the colon would not > > indicate > > a drive letter--wouldn't that make

Re: cygpath (reprised)

Greetings, cyg Simple! > Also a : isn't a valid character for a name in Windows. Cygwin uses > some magic to represent it in UNICODE format though. It isn't a valid file "name" character, yes, but it is still a meaningful character in pathname under windows. Just the meaning of it is far from

Re: cygpath (reprised)

On 2/21/2017 1:22 PM, Nellis, Kenneth (Conduent) wrote: > From: Andrey Repin >>> But, consider the following: >> >>> $ cygpath -w a:b | od -An -tx1c >>> 41 3a 62 0a >>>A : b \n >>> $ >> >>> Instead of the special character colon (:), shouldn't cygpath be showing >>> something in the

RE: cygpath (reprised)

From: Andrey Repin > > But, consider the following: > > > $ cygpath -w a:b | od -An -tx1c > > 41 3a 62 0a > >A : b \n > > $ > > > Instead of the special character colon (:), shouldn't cygpath be showing > > something in the Unicode Private Use area? > > No, it shouldn't. > You've

Re: cygpath (reprised)

Greetings, Nellis, Kenneth (Conduent)! > I followed and understood the discussion to all the recent cygpath postings, > so I understand and expect the following: > $ cygpath -w 'a*b' | od -An -tx1c > 61 ef 80 aa 62 0a >a 357 200 252 b \n > $ > But, consider the following: > $

Re: cygpath

On Feb 15 14:41, Nellis, Kenneth (Conduent) wrote: > From: Corinna Vinschen > > On Feb 13 17:29, Nellis, Kenneth (Conduent) wrote: > > > From: Andrey Repin > > > > See > > > > http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-specialchars > > > > > > This reference says: > > > ...

RE: cygpath

From: Corinna Vinschen > On Feb 13 17:29, Nellis, Kenneth (Conduent) wrote: > > From: Andrey Repin > > > See > > > http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-specialchars > > > > This reference says: > > ... > > I propose the following: > > ... > > Patched. Thanx for

Re: cygpath

On Feb 13 17:29, Nellis, Kenneth (Conduent) wrote: > From: Andrey Repin > > See > > http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-specialchars > > This reference says: > > > All of the above characters, except for the backslash, are converted to > > special UNICODE

Re: cygpath -w converts relative paths to absolute windows paths

Am 13.02.2017 um 16:16 schrieb Corinna Vinschen: On Feb 12 18:38, Thomas Wolff wrote: Am 12.02.2017 um 12:23 schrieb Corinna Vinschen: On Feb 7 14:35, Roger Qiu wrote: Hi, I've found that `cygpath --windows '../` will give back an absolute windows path. I thought this would only happen if

RE: cygpath

From: Andrey Repin > See > http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-specialchars This reference says: > All of the above characters, except for the backslash, are converted to > special UNICODE characters in the range 0xf000 to 0xf0ff (the "Private > use area") when

Re: cygpath -w converts relative paths to absolute windows paths

On Feb 12 18:38, Thomas Wolff wrote: > Am 12.02.2017 um 12:23 schrieb Corinna Vinschen: > > On Feb 7 14:35, Roger Qiu wrote: > > > Hi, > > > > > > I've found that `cygpath --windows '../` will give back an absolute > > > windows > > > path. > > > > > > I thought this would only happen if you

Re: cygpath -w converts relative paths to absolute windows paths

Am 12.02.2017 um 12:23 schrieb Corinna Vinschen: On Feb 7 14:35, Roger Qiu wrote: Hi, I've found that `cygpath --windows '../` will give back an absolute windows path. I thought this would only happen if you provide the `--absolute` flag, or when the path is a special cygwin path. But this

Re: cygpath -w converts relative paths to absolute windows paths

On Feb 7 14:35, Roger Qiu wrote: > Hi, > > I've found that `cygpath --windows '../` will give back an absolute windows > path. > > I thought this would only happen if you provide the `--absolute` flag, or > when the path is a special cygwin path. > > But this occurs just for normal

Re: cygpath -w converts relative paths to absolute windows paths

On 2/8/2017 5:42 PM, Thomas Wolff wrote: > Hi Andrey, > > Am 08.02.2017 um 11:54 schrieb Andrey Repin: >> Greetings, Thomas Wolff! >> >>> Am 07.02.2017 um 16:30 schrieb Andrey Repin: Greetings, Roger Qiu! > I've found that `cygpath --windows '../` will give back an absolute >

Re: cygpath

On 2017-02-10 12:07, Gluszczak, Glenn wrote: > Isn’t this a defect in cygpath? Looks like memory corruption. > %%%cygpath -w /usr/tmp/* > C:\cygwin\usr\tmp\ > %%%cygpath -w /usr/non-existent/* > C:\cygwin\usr\non-existent\�[W�� For proper interpretation of a Unix path name, all but the last

Re: cygpath

On 11/02/2017 00:05, Eliot Moss wrote: > On 2/10/2017 6:50 PM, Sam Edge wrote: > >> Sorry, did anyone actually read Andrey's post? > > Yes, but I was going through the emails in order and responded > to the earlier one before I got to the later one. Sorry to have > added noise to the list ... >

Re: cygpath

On 2/10/2017 6:50 PM, Sam Edge wrote: Sorry, did anyone actually read Andrey's post? Yes, but I was going through the emails in order and responded to the earlier one before I got to the later one. Sorry to have added noise to the list ... EM -- Problem reports:

Re: cygpath

On 10/02/2017 23:17, Eliot Moss wrote: > On 2/10/2017 3:03 PM, Gluszczak, Glenn wrote: >> * is a legal character for ls but perhaps not cygpath? I don't know. >> No files or directories are using * in the name. >> >> Not sure about incorrect terminal settings as I never touched any. >> It shows

Re: cygpath

On 2/10/2017 3:03 PM, Gluszczak, Glenn wrote: * is a legal character for ls but perhaps not cygpath? I don't know. No files or directories are using * in the name. Not sure about incorrect terminal settings as I never touched any. It shows up in mintty and ssh equally. The characters that

Re: cygpath

On Fri, Feb 10, 2017 at 1:34 PM, Andrey Repin wrote: > Greetings, Gluszczak, Glenn! > >> * is a legal character for ls but perhaps not cygpath? > > "*" is not a legal path name character. And cygpath expects a path. AFAICT, '*' is a legal character in a filename or directory name on Posix systems

Re: cygpath

On Fri, Feb 10, 2017 at 1:46 PM, Gluszczak, Glenn wrote: > I suppose the glob explanation from Michael explains this behavior in sh. > Though unsupported, it seems to work (probably some side cases do not). It seems to me that the behavior is supported and working. Bash or sh takes an unescaped

RE: cygpath

I suppose the glob explanation from Michael explains this behavior in sh. Though unsupported, it seems to work (probably some side cases do not). $ cygpath -w /usr/bin/* C:\cygwin64\bin\[.exe C:\cygwin64\bin\2to3 C:\cygwin64\bin\addftinfo.exe C:\cygwin64\bin\addr2line.exe

Re: cygpath

Greetings, Gluszczak, Glenn! > * is a legal character for ls but perhaps not cygpath? "*" is not a legal path name character. And cygpath expects a path. > I don't know. > No files or directories are using * in the name. See above. > Not sure about incorrect terminal settings as I never

RE: cygpath

] On Behalf Of Michael Enright Sent: Friday, February 10, 2017 3:43 PM To: cygwin@cygwin.com Subject: Re: cygpath On Fri, Feb 10, 2017 at 12:31 PM, Gluszczak, Glenn wrote: > Sorry, I forgot the user I log in as is switching to cmd.exe. > > This doesn't happen in sh or tcsh, so it is probably a

Re: cygpath

On Fri, Feb 10, 2017 at 12:42 PM, Michael Enright wrote: > On Fri, Feb 10, 2017 at 12:31 PM, Gluszczak, Glenn wrote: >> Sorry, I forgot the user I log in as is switching to cmd.exe. >> >> This doesn't happen in sh or tcsh, so it is probably a non-issue. >> > > My results are from running a

Re: cygpath

On Fri, Feb 10, 2017 at 12:31 PM, Gluszczak, Glenn wrote: > Sorry, I forgot the user I log in as is switching to cmd.exe. > > This doesn't happen in sh or tcsh, so it is probably a non-issue. > My results are from running a "normal" bash-under-mintty setup. If I go to a cmd.exe window and start

Re: cygpath

On Fri, Feb 10, 2017 at 11:36 AM, Andrey Repin wrote: > Greetings, Gluszczak, Glenn! > >> Isn’t this a defect in cygpath? Looks like memory corruption. > >> %%%cygpath -w /usr/non-existent/* >> C:\cygwin\usr\non-existent\�[W�� > > Looks more like private character space combined with incorrect

RE: cygpath

To: cygwin@cygwin.com Subject: RE: cygpath * is a legal character for ls but perhaps not cygpath? I don't know. No files or directories are using * in the name. Not sure about incorrect terminal settings as I never touched any. It shows up in mintty and ssh equally. The characters that appear vary

RE: cygpath

*not* produce the gibberish. %%%cygpath -w /aaa/bbb/* C:\cygwin\aaa\bbb\ -Original Message- From: Andrey Repin [mailto:anrdae...@yandex.ru] Sent: Friday, February 10, 2017 2:36 PM To: Gluszczak, Glenn; cygwin@cygwin.com Subject: Re: cygpath Greetings, Gluszczak, Glenn! > Isn’t this a def

Re: cygpath

Greetings, Gluszczak, Glenn! > Isn’t this a defect in cygpath? Looks like memory corruption. > %%%cygpath -w /usr/non-existent/* > C:\cygwin\usr\non-existent\�[W�� Looks more like private character space combined with incorrect terminal setup. See

Re: cygpath -w converts relative paths to absolute windows paths

Hi Andrey, That was probably true in the past, but no longer! I just tested this: `mklink /D testlink "..\All Users"` in cmd and then I went to Cygwin ZSH, and ran `ll`. This showed me: `testlink -> '../All Users'/`. Up one directory relative links do work on Windows! This is a directory

Re: cygpath -w converts relative paths to absolute windows paths

Hi Andrey, Am 08.02.2017 um 11:54 schrieb Andrey Repin: Greetings, Thomas Wolff! Am 07.02.2017 um 16:30 schrieb Andrey Repin: Greetings, Roger Qiu! I've found that `cygpath --windows '../` will give back an absolute windows path. ... ".." is a special path, that can't be safely

Re: cygpath -w converts relative paths to absolute windows paths

Greetings, Thomas Wolff! > Am 07.02.2017 um 16:30 schrieb Andrey Repin: >> Greetings, Roger Qiu! >> >>> I've found that `cygpath --windows '../` will give back an absolute windows >>> path. >>> ... >> ".." is a special path, that can't be safely converted. > How is the special meaning of ".." so

Re: cygpath -w converts relative paths to absolute windows paths

On 2017-02-07 16:34, Thomas Wolff wrote: > Am 07.02.2017 um 16:30 schrieb Andrey Repin: >> Greetings, Roger Qiu! >>> I've found that `cygpath --windows '../` will give back an >>> absolute windows path. >>> ... >> ".." is a special path, that can't be safely converted. > How is the special meaning

Re: cygpath -w converts relative paths to absolute windows paths

Hi Andrey, Am 07.02.2017 um 16:30 schrieb Andrey Repin: Greetings, Roger Qiu! I've found that `cygpath --windows '../` will give back an absolute windows path. ... ".." is a special path, that can't be safely converted. How is the special meaning of ".." so much different in Windows than in

Re: cygpath -w converts relative paths to absolute windows paths

On 2/7/2017 10:30 AM, Andrey Repin wrote: > Greetings, Roger Qiu! > >> Hi, > >> I've found that `cygpath --windows '../` will give back an absolute >> windows path. > >> I thought this would only happen if you provide the `--absolute` flag, >> or when the path is a special cygwin path. > >

Re: cygpath -w converts relative paths to absolute windows paths

Greetings, Roger Qiu! > Hi, > I've found that `cygpath --windows '../` will give back an absolute > windows path. > I thought this would only happen if you provide the `--absolute` flag, > or when the path is a special cygwin path. ".." is a special path, that can't be safely converted. In

Re: cygpath 2.6.0: -m " C:" and garbled output

Just to clarify, " C:" is not the entire filepath I was giving to cygpath, it's more like " C:/Temp/a.txt", but I reduced to it when trying to isolate the difference between versions. On Thu, Oct 6, 2016 at 9:26 PM, Achim Gratz wrote: > A filename can legitimately start with a

Re: cygpath 2.6.0: -m " C:" and garbled output

Andre Maroneze writes: > I just noticed a difference in behavior between versions 2.5.2 and > 2.6.0 of cygpath (the ones I could test): if I run > > cygpath -m " C:" > > (notice the space before the C, inside the double quotes) A filename can legitimately start with a space and it is a relative

Re: cygpath 2.6.0: -m " C:" and garbled output

On 10/6/2016 8:38 AM, Andre Maroneze wrote: I just noticed a difference in behavior between versions 2.5.2 and 2.6.0 of cygpath (the ones I could test): if I run cygpath -m " C:" (notice the space before the C, inside the double quotes) In cygpath 2.6.0, this outputs C? (C followed by the

Re: cygpath -w and .exe magic

On 8/26/2016 10:58 AM, Nellis, Kenneth wrote: > $ cmd /c DIR $(cygpath -w hello) But $ cmd /c $(cygpath -w hello) will execute hello.exe The fact that you get file not found error tells me that cmd is doing what it does. The purpose of the .exe magic is for executing the file from the Cygwin

Re: cygpath -w and .exe magic

On Fri, Aug 26, 2016 at 10:58 AM, Nellis, Kenneth wrote: > Here is a contrived example: > > $ cmd /c DIR $(cygpath -w hello.exe) > Volume in drive C has no label. > Volume Serial Number is 6A15-FFB2 > > Directory of C:\cygwin\home\knellis\dev\c\hello > > 08/26/2016 10:4760,927

Re: cygpath -w and .exe magic

On 26.08.2016 15:08, Nellis, Kenneth wrote: Dear Cygwin Community, $ ls -l total 60 -rwxr-x--- 1 knellis Domain Users 60927 Aug 26 08:57 hello.exe $ ./hello Hello, world! $ cygpath -w hello hello $ The purpose of cygpath -w, it seems to me, is to provide to Windows a valid path given a Posix

RE: cygpath -w and .exe magic

From: cyg Simple > On 8/26/2016 10:35 AM, Nellis, Kenneth wrote: > > From: Herbert Stocker > >> On 26.08.2016 15:19, Lee Dilkie wrote: > >>> and break everyone who has existing code to take care of this? > >> > >> If it is done, it should be done as an additional option, i'd say. > > > > Of course

Re: cygpath -w and .exe magic

On 26 August 2016 at 07:08, Nellis, Kenneth wrote: > Dear Cygwin Community, > > $ ls -l > total 60 > -rwxr-x--- 1 knellis Domain Users 60927 Aug 26 08:57 hello.exe > $ ./hello > Hello, world! > $ cygpath -w hello > hello > $ > > The purpose of cygpath -w, it seems to me, is to provide > to

RE: cygpath -w and .exe magic

From: Herbert Stocker > On 26.08.2016 15:19, Lee Dilkie wrote: > > and break everyone who has existing code to take care of this? > > If it is done, it should be done as an additional option, i'd say. Of course a new option, duh! ☺ But my feeble brain is failing to imagine a case where this

Re: cygpath -w and .exe magic

On 8/26/2016 9:08 AM, Nellis, Kenneth wrote: > Dear Cygwin Community, > > $ ls -l > total 60 > -rwxr-x--- 1 knellis Domain Users 60927 Aug 26 08:57 hello.exe > $ ./hello > Hello, world! > $ cygpath -w hello > hello > $ > > The purpose of cygpath -w, it seems to me, is to provide > to Windows a

Re: cygpath -w and .exe magic

On 26.08.2016 15:19, Lee Dilkie wrote: On 8/26/2016 9:08 AM, Nellis, Kenneth wrote: Dear Cygwin Community, $ ls -l total 60 -rwxr-x--- 1 knellis Domain Users 60927 Aug 26 08:57 hello.exe $ ./hello Hello, world! $ cygpath -w hello hello $ The purpose of cygpath -w, it seems to me, is to

Re: cygpath -w and .exe magic

On 8/26/2016 9:08 AM, Nellis, Kenneth wrote: Dear Cygwin Community, $ ls -l total 60 -rwxr-x--- 1 knellis Domain Users 60927 Aug 26 08:57 hello.exe $ ./hello Hello, world! $ cygpath -w hello hello $ The purpose of cygpath -w, it seems to me, is to provide to Windows a valid path given a

  1   2   3   4   >