Larry Hall (Cygwin) wrote:
newsletter wrote:
Hi all
I am trying to configure the $PATH variable in cygwin and am having
problems getting a path to program files to work. It keeps saying
"Program: No such file or directory". I've tried to put quotes (both
single and double) around the offendin
newsletter wrote:
Hi all
I am trying to configure the $PATH variable in cygwin and am having
problems getting a path to program files to work. It keeps saying
"Program: No such file or directory". I've tried to put quotes (both
single and double) around the offending line but it doesn't work a
Hi all
I am trying to configure the $PATH variable in cygwin and am having
problems getting a path to program files to work. It keeps saying
"Program: No such file or directory". I've tried to put quotes (both
single and double) around the offending line but it doesn't work as well.
what is t
http://cygwin.com/acronyms/#PCYMTNQREAIYR
There usually isn't any reason to put email addresses in the body of
messages. That is the case here. It is fodder for spammers and, maybe
more importantly, it is just line noise which detracts from the content
of the message.
cgf
-
On Sun, Jul 09, 2006 at 12:59:10PM -0600, Brian Liedtke wrote:
>- Original Message -
>From: "Christopher Faylor"
>To:
>Sent: Sunday, July 09, 2006 12:50 PM
>Subject: Re: Problem with embedded spaces in path name for --info-script
>switch in tar
- Original Message -
From: "Christopher Faylor" <[EMAIL PROTECTED]>
To:
Sent: Sunday, July 09, 2006 12:50 PM
Subject: Re: Problem with embedded spaces in path name for --info-script
switch in tar
On Sun, Jul 09, 2006 at 12:43:23PM -0600, Brian Liedtke wrote:
Us
On Sun, Jul 09, 2006 at 12:43:23PM -0600, Brian Liedtke wrote:
>Using tar-1.15.1-4.
>
>I am writing a script to create multi-volume archives using tar. However it
>appears that the --info-script switch doesn't handle imbedded spaces in the
>path name.
>In the sample script below, I have hard-encod
Using tar-1.15.1-4.
I am writing a script to create multi-volume archives using tar. However it
appears that the --info-script switch doesn't handle imbedded spaces in the
path name.
In the sample script below, I have hard-encoded the path to verify that was
the problem
and not with building t
http://cygwin.com/acronyms/#PCYMTWLL PLEASE!
* Andreas Eibach (2005-06-28 14:14 +0100)
> Yes, this is the umpteenth time this gets asked, but also the umpteenth plead
> to fix this in cygwin (as it _definitely_ works in Linux, also with vfat and
> non-Linux partitions!!)
This is probably the um
On Tue, 28 Jun 2005, Nikhil Nair wrote:
> Just a quick observation - but first an apology: I haven't read the
> thread, as I've only just subscribed, so this may have already been said.
>
> I'm a bit surprised by this wildcard behaviour, as I would have assumed
> "CD 1..." would have been picked u
On Tue, 28 Jun 2005, Andreas Eibach wrote:
> Needless to say that scripts containing
>
> for i in `ls *.dat*`; do
Ouch!!!
> will NOT work, because Cygwin will interpret each sub-string between the \ '
> s separately, making parsing files a nuisance.
That script won't work anywhere. Who
Hi,
Just a quick observation - but first an apology: I haven't read the
thread, as I've only just subscribed, so this may have already been said.
I'm a bit surprised by this wildcard behaviour, as I would have assumed
"CD 1..." would have been picked up by "CD *".
I'd suggest that this is a bash
Original Message
>From: Andreas Eibach
>Sent: 28 June 2005 14:14
> fix this in cygwin (as it _definitely_ works in Linux,
I'm glad you're so definite about this, it's good to have such confidence
in your own beliefs that you feel no need to verify them against reality.
> ls -hog "CD *"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Andreas Eibach on 6/28/2005 7:14 AM:
>
> -rw-r--r-- 1 0 Jun 28 14:46 CD0.dat
> -rw-r--r-- 1 24K Jun 28 14:46 CD 1 - Multimedia.dat
> -rw-r--r-- 1 2.9K Jun 28 14:46 CD 2 - Multimedia.dat
...
> ls -hog "CD*[12]*"
>
> WORK
I don't see the problem.
> ls -hog "CD *"
> ls: CD *: No such file or directory
Of course. There is no file whose name is the four character string "CD *", so
ls doesn't find anything.
> ls -hog "CD [12]*"
> ls: CD [12]*: No such file or directory
Ditto. There is no file whose name is the six
Yes, this is the umpteenth time this gets asked, but also the umpteenth plead
to fix this in cygwin (as it _definitely_ works in Linux, also with vfat and
non-Linux partitions!!)
I have two files in ~, say they're
CD0.dat
CD1 - Multimedia (foo1).dat
CD2 - Multimedia2 (foo2).dat
+
Dave Korn wrote:
I use the same trick myself because a lot of apps can't handle a
filename with a space in it, not even if it gets correctly escaped and
passed through to argv, but I've never known bash filename completion
to have a problem: it escapes all the spaces and other metachars
beautif
> -Original Message-
> From: cygwin-owner On Behalf Of Andrew DeFaria
> Sent: 29 September 2004 16:16
> However, one trick that I do to more easily deal with the "Program
> Files" think is:
>
> $ mount -bsf "/cydrive/c/Program Files" /apps
>
> Then it's simply /apps//. Much easier to d
On Thu, Feb 13, 2003 at 09:52:27AM -0500, Christopher Faylor wrote:
> On Thu, Feb 13, 2003 at 09:32:12AM -0500, Kirschner, Paul E.UTRC wrote:
> >breaks my .cshrc. Several paths in my win2000 system path (from the
> >environment variables section) are of the form "c:\program files\...". That
On Thu, Feb 13, 2003 at 09:32:12AM -0500, Kirschner, Paul E.UTRC wrote:
>breaks my .cshrc. Several paths in my win2000 system path (from the
>environment variables section) are of the form "c:\program files\...". That
>space now breaks my cshrc lines like...
>
>setenv PATH $PATH":/d/jdk1.3
The latest tcsh change...
I've updated the version of tcsh to 6.12.00-4.
- /etc/csh.login now preserves spaces in pathnames when evaluating $path.
breaks my .cshrc. Several paths in my win2000 system path (from the
environment variables section) are of the form "c:\program files\...". That
space
21 matches
Mail list logo
