I tried this installation to a network drive on one machine again with
last week's new setup.exe, which didn't solve the problem as Corinna had
assumed, but with more detailed test results:
The machine runs Windows XP Professional, drvies H: and T: are normal
Windows mounts or NFTS network
On Nov 24 18:21, Thomas Wolff wrote:
I tried this installation to a network drive on one machine again
with last week's new setup.exe, which didn't solve the problem as
Corinna had assumed, but with more detailed test results:
The machine runs Windows XP Professional, drvies H: and T: are
Hi,
I tried the case sensitive purpose , but did not work
I created a c:\test dyrectory, then my fstab is as follow :
c:/test /test auto binary,posix=1,user 0 0
when I create a file x or X , there is only one file listed with ls
Best Regards
S.Ancelot
--
Problem reports:
On Nov 24 12:24, David Antliff wrote:
On Mon, Nov 23, 2009 at 17:26, Eric Blake wrote:
According to David Antliff on 11/22/2009 9:20 PM:
Any suggestions how to investigate this further? Is there some way
that Windows or Cygwin is somehow preventing the deletion of this
directory?
On Nov 24 09:32, stephane ancelot wrote:
Hi,
I tried the case sensitive purpose , but did not work
I created a c:\test dyrectory, then my fstab is as follow :
c:/test /test auto binary,posix=1,user 0 0
when I create a file x or X , there is only one file listed with ls
On Nov 23 20:29, Linda Walsh wrote:
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Linda Walsh on 11/23/2009 4:59 PM:
Instead of using random characters out of the 'random free area' --
which could display as anything if you aren't in cygwin, depending
on
On Nov 24 09:50, Corinna Vinschen wrote:
On Nov 23 20:29, Linda Walsh wrote:
Eric Blake wrote:
But then, how would you distinguish between the valid UTF-16 replacement
used to represent an invalid character, and a valid UTF-16 character
representing itself? I'm sorry, but the value of a
On Nov 23 13:20, Christopher Faylor wrote:
On Mon, Nov 23, 2009 at 10:07:05PM +0800, Huang Bambo wrote:
There's some diffirence between cygwin and other *nix:
In other *nix with this condition, those ended child process could be
list by ps command with defunctag, will you fix it?
Cygwin
I would recommend using the completed port of grep ( ls) made for Windows.
http://utools.com/msls.htm
On Tue, Nov 24, 2009 at 5:00 AM, Gary Johnson garyj...@spocom.com wrote:
On 2009-11-23, Morten Kjærulff wrote:
On Mon, Nov 23, 2009 at 4:51 PM, Alan Fay empty...@gmail.com wrote:
Howdy!
Alan Fay wrote:
# Problem command, no matching text (mt) appearing bold/blue, run in a
C# solution:
What exactly does run in a C# solution mean? That doesn't sound like an
ordinary environment for cygwin command-line tools to be running in.
Anyway, I can reproduce your problem (matching
Found this:
http://savannah.gnu.org/bugs/?18666
could be related (or the actual error?)
On Tue, Nov 24, 2009 at 2:10 PM, Dave Korn
dave.korn.cyg...@googlemail.com wrote:
Alan Fay wrote:
# Problem command, no matching text (mt) appearing bold/blue, run in a
C# solution:
What exactly does
Morten Kjærulff wrote:
Found this:
http://savannah.gnu.org/bugs/?18666
could be related (or the actual error?)
Bingo. 1.7 uses UTF8 by default. 1.5 doesn't use UTF8 at all. On Cygwin
1.7, grep -i whatever works, but LC_ALL=C.ASCII grep -i fails.
cheers,
DaveK
--
Problem
On Tue, Nov 24, 2009 at 10:25:12AM +0100, Corinna Vinschen wrote:
On Nov 23 13:20, Christopher Faylor wrote:
On Mon, Nov 23, 2009 at 10:07:05PM +0800, Huang Bambo wrote:
There's some diffirence between cygwin and other *nix:
In other *nix with this condition, those ended child process could be
On Tue, Nov 24, 2009 at 03:07:12PM +0100, Morten Kj?rulff wrote:
On Tue, Nov 24, 2009 at 2:10 PM, Dave Korn wrote:
?Anyway, I can reproduce your problem (matching text colour disappears when
'-i') in a bash shell in cygwin 1.5, but it works just fine under 1.7; you
might want to try that.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adrian May wrote:
1. If you ...
2. Does anybody ...
3. Even if ...
4. You can ...
5. I did ...
6. I did ...
Too much words for my mind. My vocabulary of English ended in the middle
of the first paragraph.
Man, you really offended at the
On 2009-11-24, Christopher Faylor wrote:
On Tue, Nov 24, 2009 at 03:07:12PM +0100, Morten Kj?rulff wrote:
On Tue, Nov 24, 2009 at 2:10 PM, Dave Korn wrote:
?Anyway, I can reproduce your problem (matching text colour disappears when
'-i') in a bash shell in cygwin 1.5, but it works just fine
On Nov 24 18:19, Slava Zanko wrote:
P.S. guys from cygwin devel-team: mc-4.6.1 too old for supporting,
mc-4.7.0-pre2 and newest don't compile on current cygwin (because
cyrrent cygwin don't have ipv6 support :( ). Is you have any ideas about?
Cygwin 1.7 with IPv6 support exists quite some time
On Nov 24 18:19, Slava Zanko wrote:
P.S. guys from cygwin devel-team: mc-4.6.1 too old for supporting,
mc-4.7.0-pre2 and newest don't compile on current cygwin (because
cyrrent cygwin don't have ipv6 support :( ). Is you have any ideas about?
Cygwin 1.7 with IPv6 support exists quite some time
Hi Online Marketer,
You have just taken the first step toward a new life!
get in here http://cug.kr/1yt
Here we go.What you are going to do is set up online accounts.
I WILL SHOW YOU EXACTLY HOW TO DO THIS.
I'm not an internet guru, I'm a real person with real answers to real problems.
Corinna Vinschen wrote:
On Nov 23 20:29, Linda Walsh wrote:
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Linda Walsh on 11/23/2009 4:59 PM:
Instead of using random characters out of the 'random free area' --
which could display as anything if
http://www.cygwin.com/ml/cygwin-xfree/2006-12/msg00082.html is an example of a
report involving zombie processes within cygwin 1.5
--
Tcl - It's the real thing. http://wiki.tcl.tk/
http://www.purl.org/NET/lvirden/ http://www.xanga.com/lvirden/
Anything in this posting represents only my
On Sat, 2009-11-21 at 17:59 +0800, Adrian May wrote:
6. I did actually give you all the information you need and I don't
care why your mail server spat it back. Which version of cygwin?
If you want US to look into this, you need at least to supply the
versions of libraries mc is linked
24.11.2009 18:35, Corinna Vinschen wrote:
Cygwin 1.7 with IPv6 support exists quite some time and the official
release is due very soon now. See http://cygwin.com/#beta-test
There's no reason anymore to build against Cygwin 1.5.25.
Ok, thanks for info. I'll try to compile mc with new version
On Tue, Nov 24, 2009 at 08:26:39AM -0800, Gary Johnson wrote:
On 2009-11-24, Christopher Faylor wrote:
On Tue, Nov 24, 2009 at 03:07:12PM +0100, Morten Kj?rulff wrote:
On Tue, Nov 24, 2009 at 2:10 PM, Dave Korn wrote:
?Anyway, I can reproduce your problem (matching text colour disappears
The following behavior differs between Cygwin bash (both versions 3.2.39,
3.2.49) and Fedora/Linux bash (both versions 3.2.33 and 4.0.33):
$ [[ foo =~ \\bfoo\\b ]]; echo $?
Cygwin:
1
Linux:
0
Cygwin returns 0 only if I remove the \\b from before and after the word
'foo'
What is going on
I have been wondering about this for a long time...
The ps command on cygwin and Linux use incompatible options flags and
display incompatible output formats. Additionally, linux ps is much more
feature rich.
While I could live with fewer features, the incompatibility in basic input
options
We have several people who have updated their cygwin setup in the last
month or so, and after doing so subversion no longer wants to connect
to our subversion server. The server uses apache and ssl with our own
cert. After upgrading the subversion client no longer ask the this
cert is
procps
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
OK - I think I found the answer which is that \b is a GNU extension not
recognized in cygwin.
So, I guess the question now is there an alternative way of recognizing word
boundaries?
In particular, I am trying to match a process id where $proc is a list of
one or more processes (awk'd from ps).
aputerguy writes:
Perhaps, I could try adding white space as in
[[ $proc =~ 456 ]]
but not sure if that will always work.
Actually it doesn't work.
I guess I could try to try to prepend/postpend something like an 'x' to each
element of $proc, but that seems really kludgey
--
View this
Just for the record, the following works:
[[ $proc =~ (^|[^0-9])$foo([^0-9]|$) ]] ; echo $?
where I use $foo to store the process number I am trying to match against
--
View this message in context:
aputerguy wrote:
OK - I think I found the answer which is that \b is a GNU extension not
recognized in cygwin.
So, I guess the question now is there an alternative way of recognizing word
boundaries?
Bash man page for '~=' refers to man regex(3) which refers to man regex(7)
which
Dave Korn writes:
Bash man page for '~=' refers to man regex(3) which refers to man regex(7)
which describes word boundary markers as below:
$ [[ foo =~ [[:\:]]foo[[:\:]] ]]; echo $?
0
$ [[ foobar =~ [[:\:]]foo[[:\:]] ]]; echo $?
1
Thanks David!
I had actually greppe'd both regex(3) and
This might come across as slightly smart-assed, but if you wrote your
script in Perl, you wouldn't have the platform problem, nor the
word-boundary problem. True you would have a Perl problem, but that
would still be several orders of magnitude easier than trying to have
Linux, Cygwin and Posix
What I have often done in a case like this is:
Add the separator (space in this case) at each end of the list.
So, if the initial string is 101 203 455 I turn that into
101 203 455 .
LIST= ${LIST}
Then I match the desired string, also surrounded by spaces,
like this:
[ -z ${LIST##*
aputerguy nabble at kosowsky.org writes:
HOWEVER, this solution while sweet for cygwin-bash, has the CONVERSE
PROBLEM.
Apparently, the special strings [[::]] and [[::]] are not recognized under
Linux regex(7) - they give return code 2.
And why is that surprising? 'man 7 regex' _did_ state:
On Tue, Nov 24, 2009 at 10:18:27PM +, Eric Blake wrote:
aputerguy nabble at kosowsky.org writes:
HOWEVER, this solution while sweet for cygwin-bash, has the CONVERSE
PROBLEM.
Apparently, the special strings [[::]] and [[::]] are not recognized under
Linux regex(7) - they give return code
aputerguy schrieb:
Hugh Myers:
This might come across as slightly smart-assed, but if you wrote your
script in Perl, you wouldn't have the platform problem, nor the
word-boundary problem. True you would have a Perl problem, but that
would still be several orders of magnitude easier than
Dave Korn dave.korn.cygwin at googlemail.com writes:
$ [[ foo =~ [[:\:]]foo[[:\:]] ]]; echo $?
0
(Note that I had to backslash-escape the and there. In other contexts
that might not be needed.)
But here's something weird with how bash manages quoting inside [[ ]]. If you
add a
On 11/24/2009 11:59 AM, wynds...@aim.com wrote:
We have several people who have updated their cygwin setup in the last
month or so, and after doing so subversion no longer wants to connect to
our subversion server. The server uses apache and ssl with our own
cert. After upgrading the
40 matches
Mail list logo
