This way, you're testing command interpreter, not WinApi.
The command interpreter has its own ideas about what you can and can not use
with it.
Yes, after I saw it works with "-literal" I convinced my self it is a
bug in PowerShell (I guess they strip the trailing \, but who knows).
But then
Greetings, Federico Kircheis!
>>> 1)
>>> root path, like C:\ , because for whatever reason \\?\C:\ is not valid, it
>>> has to be a subfolder (and trying to trick it with \\?\C:\\ does not work
>>> either).
>> > In which scenario? \\?\C:\ is just the same as \??\C:\ in NT speak, and
>> that's a p
On Dec 6 13:23, Federico Kircheis via Cygwin wrote:
> Hello,
>
> was it considered to add a flag to cygpath to output a path in unc format?
>
>
> For example, the folder
>
> C:\test.
>
> cannot be accessed from many Windows applications (powershell and cmd
> included) because of the trailing
On Dec 9 14:48, Federico Kircheis via Cygwin wrote:
> On 09/12/2024 14.17, Corinna Vinschen via Cygwin wrote:
> > On Dec 9 13:47, Federico Kircheis via Cygwin wrote:
> > > 1)
> > > root path, like C:\ , because for whatever reason \\?\C:\ is not valid, it
> > > has to be a subfolder (and trying t
On 09/12/2024 14.17, Corinna Vinschen via Cygwin wrote:
On Dec 9 13:47, Federico Kircheis via Cygwin wrote:
On 09/12/2024 12.46, Corinna Vinschen via Cygwin wrote:
On Dec 6 13:23, Federico Kircheis via Cygwin wrote:
Hello,
was it considered to add a flag to cygpath to output a path in unc f
On Dec 9 13:47, Federico Kircheis via Cygwin wrote:
> On 09/12/2024 12.46, Corinna Vinschen via Cygwin wrote:
> > On Dec 6 13:23, Federico Kircheis via Cygwin wrote:
> > > Hello,
> > >
> > > was it considered to add a flag to cygpath to output a path in unc format?
> >
> > No. But it wouldn't
On 09/12/2024 12.46, Corinna Vinschen via Cygwin wrote:
On Dec 6 13:23, Federico Kircheis via Cygwin wrote:
Hello,
was it considered to add a flag to cygpath to output a path in unc format?
No. But it wouldn't be much work.
It would be very nice if it ever happens.
For example, the fold
On Dec 6 13:23, Federico Kircheis via Cygwin wrote:
> Hello,
>
> was it considered to add a flag to cygpath to output a path in unc format?
No. But it wouldn't be much work.
>
>
> For example, the folder
>
> C:\test.
>
> cannot be accessed from many Windows applications (powershell and cmd
Greetings, Soren!
> Hello users. I have a reasonably recently installed Cygwin that I've kept
> updated with setup. I am just now seeing that the provided `cygpath`
> command no longer works the way it ought to. Could someone(s) confirm or
> deny this? And fix it, because it is an important facil
Thank you, Dimitry, I understand now why it went wrong. I don't know what I
was thinking, trying to combine -u with -s.You example is useful.
Thank you also, Corinna.
--
Soren
On Fri, Nov 8, 2024 at 10:30 AM Dimitry Andric <
dimi...@unified-streaming.com> wrote:
> On 8 Nov 2024, at 16:20, Soren
On Nov 8 10:20, Soren via Cygwin wrote:
> Hello users. I have a reasonably recently installed Cygwin that I've kept
> updated with setup. I am just now seeing that the provided `cygpath`
> command no longer works the way it ought to. Could someone(s) confirm or
> deny this? And fix it, because it
On 8 Nov 2024, at 16:20, Soren via Cygwin wrote:
>
>
> Hello users. I have a reasonably recently installed Cygwin that I've kept
> updated with setup. I am just now seeing that the provided `cygpath`
> command no longer works the way it ought to. Could someone(s) confirm or
> deny this? And fix
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 cy
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
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 and
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 o
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 disab
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 it
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 /usr/bin/cy
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
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 cygpat
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 --he
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?
> > >
>
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
> > > does
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.
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.
--
Wit
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
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 C:\A
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
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
Wh
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 inte
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 lat
> 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
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 testin
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
path
Wednesday, 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 interoperab
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. In
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 p
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 was
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 convenien
[Date 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: sourcewar
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 th
m: Marco Atzeri [mailto:marco.atz...@gmail.com]
Sent: mercredi 10 mai 2017 09:14
To: cygwin@cygwin.com
Cc: Chevallier Yves
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 I cannot f
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. Changi
cygwin 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:
<0d835e9b9cd07f40a48423f80d3b5a704bc07...@usa7109mb022.na.xerox.net>
<7ddd6386-4463-ec7e-14b0-dc1b719c9
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
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.
https://untroubled.org/ezm
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
> https://www.cygwin.com/ml/cygwin/2017-04
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 c
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 a
> 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 sen
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 messag
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 (
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)
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) 20
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
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
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
Virtualization:
binD9fTojUuRq.bin
Description: PGP/MIME version identification
encrypted.asc
Description: OpenPGP encrypted message
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 v
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 m
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
>>
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 pathnam
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 sense?--b
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
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
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
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:
> $ cyg
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:
> > > ...
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 that,
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 characte
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 y
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 c
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 pr
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 o
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 directories.
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
> win
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 comp
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 ...
>
No
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: http://cygwin.com/prob
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 up
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 appea
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
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 ar
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
C:\cygwin64\bin\whatis.ex
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 touch
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 probab
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 "normal"
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 b
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 te
PM
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 a
*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
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
http://cygwin.com/cygwin-ug-net/using-specia
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
sy
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 converted.
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
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
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
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.
>
> ".
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 al
1 - 100 of 405 matches
Mail list logo
