If this change is what is desired by the majority, that is fine. BUT, it
should have been made clear that the fundamental behaviour of cygpath had
changed. I have many scripts that no longer work. Even the jakarata ant
tool's start-up script now mangles the classpath because of this chan
Igor Pechtchanski wrote:
> On Tue, 11 Feb 2003, Newton, Doug wrote:
>
>> If this change is what is desired by the majority, that is fine.
>> BUT, it should have been made clear that the fundamental behaviour
>> of cygpath had changed. I have many scripts that no longer wo
On Tue, Feb 11, 2003 at 11:57:45PM -, Max Bowsher wrote:
>Igor Pechtchanski wrote:
>> On Tue, 11 Feb 2003, Newton, Doug wrote:
>>
>>> If this change is what is desired by the majority, that is fine.
>>> BUT, it should have been made clear that the fundame
I have two almost identical build servers, but cygpath is not behaving as
expected on one of them. Here is the output from the “good” build server:
$ cygpath.exe —version | head -1
cygpath (cygwin) 2.11.2
$ cygpath -d 'E:\Program Files (x86)\IAR Systems'
E:\PROGRA~1\IARSYS~
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
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
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 o
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 outpu
Hi,
With cygwin1.ddl-1.5.18:
$ cygpath -H
/cygdrive/c/Documents and Settings
With cygwin1-20051106.dll:
$ cygpath -H
%SystemDrive%/Documents and Settings
bye,
R.M.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Rodrigo Medina wrote:
> Hi,
>
> The new cygpath 15.1.19-2 writes an additional line in the tty
>
> $ cygpath -H
> $ ** buf C:\WINDOWS\Profiles
> $ /cygdrive/c/WINDOWS/Profiles
>
> bye
>
> R.M.
Oops! Someone left some debug print in there!
[ U
I seem like an idiot. This is such a fundamental
command, it can't be broken, can it?
I have the following bash alias:
alias explr='explorer.exe `pwd | cygpath -w -f -`'
It used to work like a charm. No more.
Not sure when it stopped working. 1.5.19-2 maybe.
1.5.19-3 didn'
> To be useful, cygpath must fully resolve a pathname, not just the last
> component.
While I'm at it, it would be nice if cygwin exported resolvepath(2) - it is not
POSIX, but Solaris defines it as:
#include
int resolvepath(const char *path, char *buf, size_t bufsiz);
similar t
Original Message
>From: Eric Blake
>Sent: 04 April 2005 15:40
> While I'm at it, it would be nice if
http://cygwin.com/acronyms#PTC !
NB: Before cygwin can export a function, that function first has to
*exist* within cygwin
cheers,
DaveK
--
Can't think of a wit
When specify --windows or --mixed form, cygpath will append `/' to the
result path when it is a directory, this is unnecessary and
inconformity, for example:
cygpath -u some/dir
> some/dir
cygpath -m some/dir
> some/dir/
cygpath -w .
> x:\some\dir\
The ending `\&#
Hello.
I have a problem with the command "cygpath", she produces nothing with any
arguments. I have notice this problem since the new updates of my Windows XP SP2
and the update KB925902).
With the command strace cygpath ..., a popup raises with the message :
"The system DLL user
Hi,
is it possible to invoke cygpath as a key binding? For example, if my
current command line is
tar c:\temp
and my cursor is on c:\temp, then it would be nice to convert c:\temp
into a Windows path by pressing a certain key.
Thanks,
Jochen
--
Unsubscribe info: http
> At 08:02 AM 2/20/2004, Christian Matuszewski you wrote:
> >Hello,
> >
> >the following command crashes:
> Sent: 27 February 2004 10:43 From: Christian Matuszewski
..snip..
> >
> > Try the latest snapshot <http://cygwin.com/snapshots/>.
> >
> >
>
> Thank you very much, now cygpath doesn't crash anymore.
>
> But is it necessary, that cygpath gi
On Fri, Feb 27, 2004 at 11:22:38AM -, Hughes, Bill wrote:
>> Sent: 27 February 2004 10:43 From: Christian Matuszewski
>>cgf says:
>>>Try the latest snapshot <http://cygwin.com/snapshots/>.
>>
>>Thank you very much, now cygpath doesn't crash any
On Fri, Feb 27, 2004 at 11:22:38AM -, Hughes, Bill wrote:
>> Sent: 27 February 2004 10:43 From: Christian Matuszewski
>>cgf says:
>>>Try the latest snapshot <http://cygwin.com/snapshots/>.
>>
>>Thank you very much, now cygpath doesn't crash any
On Sat, 28 Feb 2004, Christian Matuszewski wrote:
> On Fri, Feb 27, 2004 at 11:22:38AM -, Hughes, Bill wrote:
> >> Sent: 27 February 2004 10:43 From: Christian Matuszewski
> >>cgf says:
> >>>Try the latest snapshot <http://cygwin.com/snapshots/>.
&g
Hi,
I'm trying to convert the following path name to a
unix specific format so that it could be passed as a
parameter to the Unix "open(..)" system call.
cygpath
"\\Device\\harddiskdmvolumes\\physicaldmvolumes\\rawvolume3
"
The converted path name is not accepted by the
&q
in http://sources.redhat.com/ml/cygwin/2003-01/msg01707.html I thought to
see how I should do this.
The example works fine. But if I create a script that does
the same
echo "$@" | cygpath -w -f -
and call it with
testscript `/bin/ls /bin/ch*`
I get
C:\cygwin\bin\checkgid.exe \bin
When you convert a relative path to absolute using cygpath.exe
and it has ".." (backup one dir) in it, it goofs up in a particular
"to Unix" case, but not the "to Windows" case. I checked the
FAQ, did a google and couldn't find any knowledge of this bug.
My Cygwin is installed under c:\cygwin and
[posted and mailed]
Hi! The ever-fascinating "cygpath" tool once again beckons to me to plumb
its depths ...
I am trying to finish a test script that uses ActivePerl to call `cygpath`
from itself (a system call, by open()-ing a pipe to capture the output of
the tool ...
[posted and mailed]
Hi! The ever-fascinating "cygpath" tool once again beckons to me to plumb
its depths ...
I am trying to finish a test script that uses ActivePerl to call `cygpath`
from itself (a system call, by open()-ing a pipe to capture the output of
the tool ...
On Wed, 22 Jan 2003, Kenji Yamashita wrote:
> Hello,
>
> I found that the behavior of cygpath was strange.
>
> kenji@ibm[88] cygcheck -c cygwin
> Cygwin Package Information
> Package Version
> cygwin 1.3.18-1
>
> Use -h to see hel
Hello, Igor.
>>>>> On Tue, 21 Jan 2003 23:35:01 -0500 (EST)
>>>>> [EMAIL PROTECTED](Igor Pechtchanski) said:
> Let me make sure I understand what you're trying to do:
> You're trying to translate a *Windows* path to a Windows path using
> cygpat
I believe I have found a bug in cygpath.exe version 1.25 (Which has been the
version included since at least cygwin version 1.3.17-1 and through cygwin
version 1.3.20-1).
Using installations from any release since 1.3.17-1 (the earliest full
installation that I had available), cygpath does work
whorfin wrote:
> I am experiencing a problem with 1.3.20 that seems to
> be cygpath related.
Already discussed, this month.
http://sources.redhat.com/ml/cygwin/2003-02/msg00722.html
Max.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:
> I am experiencing a problem with 1.3.20 that seems to
> be cygpath related. Previously, I was using 1.3.17,
> upgraded today, and I get errors when trying to run
> Ant 1.5.1 (it ran just fine before). After a little
> fiddling, it appears that cygpath is still having some
>
> > I am experiencing a problem with 1.3.20 that seems to
> > be cygpath related. Previously, I was using 1.3.17,
> > upgraded today, and I get errors when trying to run
> > Ant 1.5.1 (it ran just fine before). After a little
> > fiddling, it appears tha
> whorfin wrote:
>> I am experiencing a problem with 1.3.20 that seems
to
>> be cygpath related.
>
>Already discussed, this month.
>
>http://sources.redhat.com/ml/cygwin/2003-02/msg00722.html
>
>
>Max.
Many thanks to Max and everybody else who responded.
I&#x
whorfin wrote:
I'll toss this on Jakarta's doorstep (or, if I get
really ambitious, attempt to fix their script myself).
This would be the "ant" shell script, no? I've opened up bug 17212
(http://issues.apache.org/bugzilla/show_bug.cgi?id=17212) at
issues.apache.org.
--
Unsubscribe info:
On Tue, May 14, 2002 at 10:44:20AM -0400, Mark Blackburn wrote:
> In cygpath.cc there is a function that goes like this:
Thanks for the heads up. I've checked in a patch.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer
I forgot to mention that there are a total of 4 places where
GetShortPathName is used
Lines 92 110 131 144
The same problem appears in all places.
On Tue, 14 May 2002, Corinna Vinschen wrote:
> On Tue, May 14, 2002 at 10:44:20AM -0400, Mark Blackburn wrote:
> > In cygpath.cc there is a function
Hi Mark,
>The spot where it says:
> DWORD len = GetShortPathName (filename, NULL, 0);
> if (len == ERROR_INVALID_PARAMETER)
Ups.
:)
>By the way I noticed this while I was trying to add a -l
>option to cygpath
>which is similar to the -s option but it will convert a
>m
On Wed, May 15, 2002 at 11:44:51AM +0200, Schaible, Jorg wrote:
> The reason why I just implemented -s (in 1999) was that GetLongPathName is
> not available for Win95. If we have to be Win95-compatible still, you will
> have to load the function yourself directly form the DLL and use
> FindFirstFi
On Tue, May 14, 2002 at 03:08:12PM -0400, Mark Blackburn wrote:
> I forgot to mention that there are a total of 4 places where
> GetShortPathName is used
> Lines 92 110 131 144
> The same problem appears in all places.
Aaargh! Thanks again. I've applied the same patch in all places.
Corinna
-
u'd have to
> go the hard way...
Right, I remember. Since I developed the GetShortPathName option for cygpath
on NT4, I did not implement a counter part ... ;-)
> > you've seen my own patch for cygpath.cc in cygwin-apps ? Chris already
> > answered positivly and RH should have
Jorg Schaible wrote in
<[EMAIL PROTECTED]>
in gmane.os.cygwin on Wed, 15 May 2002 11:44:51 +0200:
> If we have to be Win95-compatible still
Please don't consider dropping 95 and NT4 support just yet! There are
still plenty of us running these OSes for all sorts of reasons.
--
Sam Edge
--
Unsu
On Wed, May 15, 2002 at 09:34:42PM +0100, Sam Edge wrote:
> Jorg Schaible wrote in
> <[EMAIL PROTECTED]>
> in gmane.os.cygwin on Wed, 15 May 2002 11:44:51 +0200:
>
> > If we have to be Win95-compatible still
>
> Please don't consider dropping 95 and NT4 support just yet! There are
> still plenty
On Wed, 15 May 2002, Joerg R. Schaible wrote:
> Hi Corinna,
>
> "Corinna Vinschen" <[EMAIL PROTECTED]> schrieb im Newsbeitrag
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > On Wed, May 15, 2002 at 11:44:51AM +0200, Schaible, Jorg wrote:
> > > The reason why I just implemented -s (in 1999)
On Thu, May 16, 2002 at 05:10:31PM -0400, Mark Blackburn wrote:
> Here's my patch but it its kinda
> half-assed (I don't think it restores 8.3 directories in the path, just
> the file) and flaky (it sometimes truncates the filename). Oh and sorry
> about the extraneous fprintf(stderr,...)'s.
Two
Hi Corinna,
> Two problems:
>
> - If it doesn't fix the 8.3 directories in path it's not really
> a patch.
> - This is a big change so we would need a copyright assignment
> from you (http://cygwin.com/contrib.html).
since Mark seems not to implement the necessary functionality, I've done it
On Tue, Oct 15, 2002 at 10:17:51AM -0700, Randall R Schulz wrote:
>Hello, Chris,
>
>Back in August, I sent this message:
>
>-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==-
>Hi,
>
>The "cygpath --help" outpu
Chris,
"Cygpath," not "cygcheck":
1018> cygpath --help
Usage: cygpath (-d|-m|-u|-w|-t TYPE) [-c HANDLE] [-f FILE] [options] NAME
cygpath [-ADHPSW]
Output type options:
-d, --dos print DOS (short) form of NAME (C:\PROGRA~1\)
-m, --mixed
On Tue, 15 Oct 2002, Randall R Schulz wrote:
> Hello, Chris,
>
> Back in August, I sent this message:
>
> -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==-
> Hi,
>
> The "cygpath --help" outpu
On Tue, Oct 15, 2002 at 10:48:01AM -0700, Randall R Schulz wrote:
>Chris,
>
>"Cygpath," not "cygcheck":
Sorry. I actually did check cygpath and then used the wrong program
in my example:
cgf
bash-2.05b$ cygpath --help
Usage: cygpath (-d|-m|-u|-w|-t TYPE) [-c HAN
Igor,
1021> cygpath --help | tail -1 | od -t x1 -c
000 20 20 2d 76 2c 20 2d 2d 76 65 72 73 69 6f 6e 09
- v , - - v e r s i o n \t
020 09 6f 75 74 70 75 74 20 76 65 72 73 69 6f 6e 20
\t o u t p u t v e r s
Chris, Igor,
I had a copy of cygpath in my $HOME/bin directory. It was one sent out by
Igor on Sep. 15th attached to this message to John Morrison :
>John,
>
>If you trace this thread back a bit, you'll see that the cygpath that was
>distributed with the current release of cy
At 05:05 PM 11/25/2003, Masoud Mansouri-Samani you wrote:
>Hi,
>
>In a script I am using cygpath for Cygwin version (1.5.5-1). It seems to have a bug:
>
> $ cygpath --path --windows "C:\foo"
> C;C:\cygwin\home\masoud\\foo
>
>Which is clearly wrong.
Actu
At 08:02 AM 2/20/2004, Christian Matuszewski you wrote:
>Hello,
>
>the following command crashes:
>
&g
On Fri, Feb 20, 2004 at 02:02:49PM +0100, Christian Matuszewski wrote:
>the following command crashes:
>
>cygp
In bash:
$ echo "\"`cygpath -w /c/temp`\""
"c:\temp"
But in Perl:
$a = `cygpath -w /c/temp`;
print "|$a|";
produces
|c:\temp
|
I.e., Perl sees an extra \n at the end of the string. I looked at
the source for cygpath and it doesn't seem t
>
>$ MODE=serious
>
>Looking at "sample use" in "info gdb" I see things that looks fairly
>straight forward and familiar. Now when I try "gdb --pid=" -
>when cygpath has hung - I end up with a situation that I don't recognise
>from that sampl
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf
> Of Christopher Faylor
> Sent: Wednesday, October 08, 2003 8:37 PM
> To: [EMAIL PROTECTED]
> Subject: Re: cygpath hang - using gdb
>
>
> On Wed, Oct 08, 2003 at 08:00:21PM +0200,
On Wed, Oct 08, 2003 at 08:53:45PM +0200, Hannu E K Nevalainen wrote:
>
>> -Original Message-
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf
>> Of Christopher Faylor
>> Sent: Wednesday, October 08, 2003 8:37 PM
>> To: [EMAIL PROTECTED]
>>
Any ideas how to work further on this?
> >Set breakpoints at "random" places in cygpath?
>
> Build a cygwin1.dll with --enable-debugging, install it, build
> cygpath.exe,
> install it. "set CYGWIN_DEBUG=cygpath" at the command prompt
> before running
> setup
> From: Christopher Faylor
> Sent: Wednesday, October 08, 2003 9:02 PM
Hannu:
> >Now; Any ideas how to work further on this?
> Build a cygwin1.dll with --enable-debugging, install it, build
> cygpath.exe,
> install it. "set CYGWIN_DEBUG=cygpath" at the
On Thu, Oct 09, 2003 at 08:07:14PM +0200, Hannu E K Nevalainen wrote:
>I'll leave this for a day or two now. Good evening.
Don't bother. Brian Ford is providing more than adequate feedback.
There's no need to strain your temper or subject the mailing list
to your frustration with building the too
On Jan 5 10:03, Buchbinder, Barry (NIH/NIAID) [E] wrote:
> Upgrading from 1.5 to 1.7 I started getting an error message from
> cygpath where I hadn't previously. This can be exemplified by the
> following.
>
> $ cmd /c dir /s /b o:\\ | cygpath -u -f - | wc
> cygpath:
Hi,
on latest
$ uname -v
20100114 15:57:50
$ cygpath -w /
C:\cygwin2
Aborted (core dumped)
no problems on the previous 20100101
Regards
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com
On Feb 12 17:38, Ilguiz Latypov wrote:
>
> This caused Cygwin to run dumper.exe which pointed to a bug in cygpath.cc.
>
> $ cygpath -p -w ''
>
>
>
> I am attaching a patch that see
n\.profile'
//DAEMON1/anrdaemon/.profile
So cygpath in backticks slaps a drive at the front, while otherwise it does
... well, what I expect.
Does anyone know why? Or know a thread where this is explained?
Many thanks!
Ivan
PS: I am running a fairly recent version of cygwin 1.7.27 ... and I
On 06/22/2013 08:39 AM, Matt D. wrote:
Maybe I've just had a long week but I can't seem to get this to work:
alias pathw='echo `cygpath -w "$@"`'
pathw "/cygdrive/g/"
I also tried:
alias pathw='echo $(cygpath -w "$@")'
cygpath
On Sat, Jun 22, 2013 at 11:39 AM, Matt D. wrote:
> Maybe I've just had a long week but I can't seem to get this to work:
>
> alias pathw='echo `cygpath -w "$@"`'
I think all you want is
alias pathw='cygpath -w'
> pathw "/cygdrive/g/"
AM, Andrew DeFaria wrote:
On 06/22/2013 08:39 AM, Matt D. wrote:
Maybe I've just had a long week but I can't seem to get this to work:
alias pathw='echo `cygpath -w "$@"`'
pathw "/cygdrive/g/"
I also tried:
alias pathw='echo $(cygpath -w "$@"
On Fri, Sep 13, 2013 at 11:55 AM, David Griffiths <> wrote:
> I reinstalled cygwin after a disk failure recently and one of my
> scripts stopped working. The problem can be easily reproduced by
> entering:
>
> $ cygpath -m boo/..
> cygpath: error converting &q
On Fri, Sep 13, 2013 at 01:17:05PM -0400, Robert Pendell wrote:
>On Fri, Sep 13, 2013 at 11:55 AM, David Griffiths <> wrote:
>> I reinstalled cygwin after a disk failure recently and one of my
>> scripts stopped working. The problem can be easily reproduced by
>> enter
> Yes, that's exactly right, assuming that 'boo' doesn't exist.
Hi, it happens even if boo does exist. To put it in context, the
script in question was attempting to determine the current directory:
CURRENT_DIR=$(cygpath -ma "${0}"/../)
(I didn't write this
On Mon, Sep 16, 2013 at 5:56 AM, David Griffiths <> wrote:
>> Yes, that's exactly right, assuming that 'boo' doesn't exist.
>
> Hi, it happens even if boo does exist. To put it in context, the
> script in question was attempting to determine the current
v localhome proc usr
boo cygwin.bat etc netrelsbin var
cygdrive cygwin.ico home netrel.build share
cygmount.bat Cygwin-Terminal.ico lib netrel.inst tmp
norton[~]
% cygpath -m /boo/..
D:/cygwin
It doesn't work if boo is not a directory bu
Greetings, David Griffiths!
>> Yes, that's exactly right, assuming that 'boo' doesn't exist.
> Hi, it happens even if boo does exist. To put it in context, the
> script in question was attempting to determine the current directory:
> CURRENT_DIR=$(cygpath -ma
On Mon, Sep 16, 2013 at 11:56 AM, David Griffiths
wrote:
>> Yes, that's exactly right, assuming that 'boo' doesn't exist.
>
> Hi, it happens even if boo does exist. To put it in context, the
> script in question was attempting to determine the current directory:
Greetings, Robert Klemme!
>>> Yes, that's exactly right, assuming that 'boo' doesn't exist.
>>
>> Hi, it happens even if boo does exist. To put it in context, the
>> script in question was attempting to determine the current directory:
>>
>
ome/dgriff> cd test
/home/dgriff/test> cygpath -m "file\.."
./
/home/dgriff/test> cygpath -m "file/.."
cygpath: error converting "file/.." - No such file or directory
/home/dgriff/test> cygpath -m "file\..\.."
C:/cygwin/home/dgriff/
/home/dgriff/
gt;
> Might be helpful to have some examples:
>
> /home/dgriff> mkdir test
> /home/dgriff> cd test
> /home/dgriff/test> cygpath -m "file\.."
> ./
Using \ means you are asking Windows to do the resolution, and Windows
has a known issue that it is intentionally NO
have some examples:
/home/dgriff> mkdir test
/home/dgriff> cd test
/home/dgriff/test> cygpath -m "file\.."
./
/home/dgriff/test> cygpath -m "file/.."
cygpath: error converting "file/.." - No such file or directory
/home/dgriff/test> cygpath -m "fi
> But why are you even using cygpath to try and determine the containing
> directory? 'dirname' does that task, in a much more portable manner,
> and without having to worry about whether 'file/..' can be abused in
> spite of POSIX semantics
To given even more
On Thu, Sep 19, 2013 at 3:23 PM, David Griffiths
wrote:
>> But why are you even using cygpath to try and determine the containing
>> directory? 'dirname' does that task, in a much more portable manner,
>> and without having to worry about whether 'file/..&#x
On 2/14/2014 1:22 PM, Andrey Repin wrote:
Greetings, All!
I would like to request a small functional change for cygpath.
In the event of empty given path argument (i.e. `cygpath -ml ""') silently
return an empty result without error message.
This would greatly simplify wrapper
Greetings, Larry Hall (Cygwin)!
> On 2/14/2014 1:22 PM, Andrey Repin wrote:
>> Greetings, All!
>>
>> I would like to request a small functional change for cygpath.
>> In the event of empty given path argument (i.e. `cygpath -ml ""') silently
>&
On Feb 14 23:43, Andrey Repin wrote:
> Greetings, Larry Hall (Cygwin)!
>
> > On 2/14/2014 1:22 PM, Andrey Repin wrote:
> >> Greetings, All!
> >>
> >> I would like to request a small functional change for cygpath.
> >> In the event of empty give
Greetings, Corinna Vinschen!
>> >> I would like to request a small functional change for cygpath.
>> >> In the event of empty given path argument (i.e. `cygpath -ml ""') silently
>> >> return an empty result without error message.
>> >
Greetings, Corinna Vinschen!
> P.S.
> I've tried to rebuild it myself, but hit a roadblock.
Had to get appropriately tired before I realized, what make tried to tell me.
> make: *** No rule to make target
> '/c/dev/sdc1/cygwin/build/winsup/cygwin/Makefile', needed by
> '/c/dev/sdc1/cygwin/build/
I'm not exactly sure what you are trying to accomplish with that patch,
but it looks to me as if everything you want is already present:
cygpath --help
states
-i, --ignore ignore missing argument
which outputs nothing if you pass it an empty argument (or even without
any fu
On 2/16/2014 12:40 AM, m0viefreak wrote:
I'm not exactly sure what you are trying to accomplish with that patch,
but it looks to me as if everything you want is already present:
cygpath --help
states
-i, --ignore ignore missing argument
which outputs nothing if you pass
Greetings, m0viefreak!
> I'm not exactly sure what you are trying to accomplish with that patch,
> but it looks to me as if everything you want is already present:
> cygpath --help
> states
> -i, --ignore ignore missing argument
With "that patch&quo
nsure that the program operates orderly.
I think you're looking for more from cygpath than it's designed to give.
Its intent is to perform direct Windows<->POSIX path conversions using the
mount table and to provide access to some system defined paths in Windows.
That's real
lly
>> conceived
>> tests to ensure that the program operates orderly.
> I think you're looking for more from cygpath than it's designed to give.
> Its intent is to perform direct Windows<->POSIX path conversions using the
> mount table and to provide access to so
On Feb 15 22:57, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>
> >> >> I would like to request a small functional change for cygpath.
> >> >> In the event of empty given path argument (i.e. `cygpath -ml ""')
> >> >
Greetings, Corinna Vinschen!
>> >> >> I would like to request a small functional change for cygpath.
>> >> >> In the event of empty given path argument (i.e. `cygpath -ml ""')
>> >> >> silently
>> >> >> ret
On Feb 16 18:41, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>
> >> >> >> I would like to request a small functional change for cygpath.
> >> >> >> In the event of empty given path argument (i.e. `cygpath -ml ""')
> >>
Corinna Vinschen sent the following at Sunday, February 16, 2014 10:11 AM
>> > NATIVE=$(cygpath -ml "$2" 2>/dev/null)
>
>And what's the problem with redirections?
>
>I fail to see the big difference between adding a redirection compared
>to add
>> That, aside the fact it needs to create a redirection.
>>
>> > NATIVE=$(cygpath -ml "$2" 2>/dev/null)
> And what's the problem with redirections?
> I fail to see the big difference between adding a redirection
> compared to adding an option charac
On Sun, Feb 16, 2014 at 12:30 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote
> if [ ! -z "$2" ] ; then NATIVE="$(cygpath -ml "$2")" ; fi
That might better be written as this
[ "$2" ] && NATIVE=$(cygpath -ml "$2")
You do not need the
>
> On Sun, Feb 16, 2014 at 12:30 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote
> > if [ ! -z "$2" ] ; then NATIVE="$(cygpath -ml "$2")" ; fi
>
> That might better be written as this
>
> [ "$2" ] && NATIVE=$(cygpath -m
On Sun, Feb 16, 2014 at 7:07 PM, Andy Hall wrote
> Goodness. If code cleanliness is the issue, Why not simply hide this construct
> in a function?
Really this whole thread is a joke. He needs to just
cygpath -ml "$2" &>/dev/null
as others have said and be done with
Hi Tod,
On Thu, Mar 10, 2011 at 5:31 PM, Tod wrote:
> I just ran an update and now I can't get either of these two programs to
> display anything. I execute them and get nothing back. I tried getting out
> of X (I use WindowMaker) to see if that was an issue but the bare bones
> console has the
201 - 300 of 725 matches
Mail list logo
