Greetings, Peter Rosin!
As you are apparently using the cmd shell, the correct way to quote
arguments in order to preserve spaces etc, is to use double quotes
and escape all backslashes with an extra backslash.
Ok, please explain, how could I escape backslashes in, say, Explorer?
It could
Den 2011-06-27 15:38 skrev Andrey Repin:
Greetings, Peter Rosin!
As you are apparently using the cmd shell, the correct way to quote
arguments in order to preserve spaces etc, is to use double quotes
and escape all backslashes with an extra backslash.
Ok, please explain, how could I
On 6/27/2011 9:38 AM, Andrey Repin wrote:
As you are apparently using the cmd shell, the correct way to quote
arguments in order to preserve spaces etc, is to use double quotes
and escape all backslashes with an extra backslash.
Ok, please explain, how could I escape backslashes in, say,
Greetings, Marco atzeri!
On Win XP cmd.exe, is not always true that the
two forms are equivalent (we are not anymore on CP/M, DOS age):
C:\Tempcd c:/Temp
The system cannot find the path specified.
This has been fixed for Vista and Win7 to my knowledge.
At least last time I ran into issue
Greetings, Peter Rosin!
cygpath, at its core, calls some form of the cygwin_conv_path API. That
function takes either a POSIX path or a Win32 path and converts to the
other form. Anything interesting or useful that's happening when feeding
it a Win32 path and requesting it to convert from
Den 2011-06-26 17:57 skrev Andrey Repin:
Greetings, Peter Rosin!
cygpath, at its core, calls some form of the cygwin_conv_path API. That
function takes either a POSIX path or a Win32 path and converts to the
other form. Anything interesting or useful that's happening when feeding
it a Win32
Den 2011-06-23 20:06 skrev Andrey Repin:
Greetings, Marco atzeri!
On 6/23/2011 5:05 PM, Andrey Repin wrote:
Greetings, Marco atzeri!
Cygwin, to my best understanding, is supposed to transparently accept native
Windows paths.
No, cygwin expects to receive POSIX/Unix paths
$ cygpath -h
On 6/23/2011 8:06 PM, Andrey Repin wrote:
Greetings, Marco atzeri!
On 6/23/2011 5:05 PM, Andrey Repin wrote:
Greetings, Marco atzeri!
Cygwin, to my best understanding, is supposed to transparently accept native
Windows paths.
No, cygwin expects to receive POSIX/Unix paths
$ cygpath -h
Marco atzeri wrote:
you are right, but it is not very useful to translate a windows path in a
windows path ...
On the contrary, it is exceedingly useful to be able to transform long names
(with spaces) into short-form names without spaces.
$ cygpath -sm $PROGRAMFILES
--
Problem reports:
On 2011-06-24 11:44, Fahlgren, Eric wrote:
Marco atzeri wrote:
you are right, but it is not very useful to translate a windows path in a
windows path ...
On the contrary, it is exceedingly useful to be able to transform long names
(with spaces) into short-form names without spaces.
$
On 6/23/2011 10:12 AM, Corinna Vinschen wrote:
I don't know what the difference in your settings is, though. Something
with readline, maybe.
Despite the APPEARANCE (*) of invoking cygpath from within a cygwin
shell, it seems the OP is actually invoking cygpath directly from a
regular cmd.exe
Sorry, wrong list. Redirected.
On 6/23/2011 12:44 PM, Charles Wilson wrote:
On 6/23/2011 10:12 AM, Corinna Vinschen wrote:
I don't know what the difference in your settings is, though. Something
with readline, maybe.
Despite the APPEARANCE (*) of invoking cygpath from within a cygwin
Greetings, Peter Rosin!
I'm facing an unacceptable cygpath behavior related to the network shares.
Unacceptable?
Exactly.
Perhaps your quoting skills and expectations fall
into that category...
The testcase is:
[\\DAEMON1\anrdaemon]$cygpath -u \\DAEMON1\anrdaemon\.profile
On Jun 21 09:23, Andrey Repin wrote:
Greetings, All!
I'm facing an unacceptable cygpath behavior related to the network shares.
The testcase is:
Here's what happens on my machine:
[\\DAEMON1\anrdaemon]$cygpath -u \\DAEMON1\anrdaemon\.profile
//DAEMON1/anrdaemon/.profile
On 6/23/2011 2:52 PM, Andrey Repin wrote:
Greetings, Peter Rosin!
I'm facing an unacceptable cygpath behavior related to the network shares.
Unacceptable?
Exactly.
Unacceptable seems a moral judgement, for this reason
I guess Peter is perplexed.
Perhaps your quoting skills and
Greetings, Marco atzeri!
I'm facing an unacceptable cygpath behavior related to the network shares.
Unacceptable?
Exactly.
Unacceptable seems a moral judgement, for this reason
I guess Peter is perplexed.
Perhaps your quoting skills and expectations fall
into that category...
The
* Andrey Repin (Thu, 23 Jun 2011 19:05:34 +0400)
Try it yourself, as well as what Peter tried to suggest (or correct
me).
Neither is working straight.
Just for example:
$ cygpath -u DAEMON1\\anrdaemon\\.profile
/c/DAEMON1/anrdaemon/.profile
$ cygpath -u DAEMON1\\anrdaemon\\.profile
On 6/23/2011 5:05 PM, Andrey Repin wrote:
Greetings, Marco atzeri!
Cygwin, to my best understanding, is supposed to transparently accept native
Windows paths.
No, cygwin expects to receive POSIX/Unix paths
$ cygpath -h
[cut]
-u, --unix(default) print Unix form of NAMEs
Greetings, Corinna Vinschen!
There's something weird in your bash settings.
My apology. I forgot to mention, it wasn't executed from bash. I've tried it
from 4NT command prompt and from native Windows CMD prompt.
Under both, cygpath exhibited the same behavior, as well as other programs
(diff,
Sorry, wrong list. Redirected.
On 6/23/2011 12:44 PM, Charles Wilson wrote:
On 6/23/2011 10:12 AM, Corinna Vinschen wrote:
I don't know what the difference in your settings is, though. Something
with readline, maybe.
Despite the APPEARANCE (*) of invoking cygpath from within a cygwin
Greetings, Marco atzeri!
On 6/23/2011 5:05 PM, Andrey Repin wrote:
Greetings, Marco atzeri!
Cygwin, to my best understanding, is supposed to transparently accept native
Windows paths.
No, cygwin expects to receive POSIX/Unix paths
$ cygpath -h
[cut]
-u, --unix(default)
Greetings, Charles Wilson!
I don't know what the difference in your settings is, though. Something
with readline, maybe.
Despite the APPEARANCE (*) of invoking cygpath from within a cygwin
shell, it seems the OP is actually invoking cygpath directly from a
regular cmd.exe console:
On my
* Andrey Repin (Thu, 23 Jun 2011 22:06:05 +0400)
To tell you, that was actually a good idea for me. I don't have an
eternity to type /cygwhatever every time I want to address another
drive.
Ever heard of tab completion?
So the idea to map cygdrive to / was actually very handy, thanks to
Greetings, Thorsten Kampe!
To tell you, that was actually a good idea for me. I don't have an
eternity to type /cygwhatever every time I want to address another
drive.
Ever heard of tab completion?
In editor? ...
There are more things in heaven and earth, Horatio,
Than are dreamt of in your
Greetings, All!
I'm facing an unacceptable cygpath behavior related to the network shares.
The testcase is:
[\\DAEMON1\anrdaemon]$cygpath -u \\DAEMON1\anrdaemon\.profile
//DAEMON1/anrdaemon/.profile
[\\DAEMON1\anrdaemon]$cygpath -m \\DAEMON1\anrdaemon\.profile
//DAEMON1/anrdaemon/.profile
Den 2011-06-21 07:23 skrev Andrey Repin:
Greetings, All!
Hi!
I'm facing an unacceptable cygpath behavior related to the network shares.
Unacceptable? Perhaps your quoting skills and expectations fall
into that category...
The testcase is:
[\\DAEMON1\anrdaemon]$cygpath -u
26 matches
Mail list logo
