Just wondering how many X - window maker packages are available in the
current release of Cygwin 1.5.24-2 - In previous versions, I was using
wmaker, however this download was disabled by default in a complete
installation recently..
Is there a more up-to-date window maker package buried in the fu
Upgrading to coreutils-6.9 breaks info, as it tries to invoke gunzip.exe.
This should be fixed in info to just invoke gunzip, since in gzip 1.3.9,
gunzip is merely a symlink (and the new coreutils no longer adds implicit
and confusing .exe extensions to symlinks).
Also, gzip has released a stabl
On Mon, Apr 23, 2007 at 06:34:45PM -0700, Gary Johnson wrote:
>I've been working on porting a simple terminal emulator application
>from HP-UX 10.20 to Cygwin. All it does is make a few termio
>settings on stdin, stdout and the specified serial port, then copy
>characters from stdin to the seri
On 24 April 2007 03:14, Lev Bishop wrote:
> On 4/23/07, Dave Korn wrote:
>> On 24 April 2007 00:53, Cary R. wrote:
>>
>>> I had some more time to look into this and when the
>>> simple C program I mentioned earlier uses variables
>>> like the other program, incorrect results are
>>> produced. I
On 4/23/07, Dave Korn wrote:
On 24 April 2007 00:53, Cary R. wrote:
> I had some more time to look into this and when the
> simple C program I mentioned earlier uses variables
> like the other program, incorrect results are
> produced. I have attached this C/C++ program. I
> certainly don't und
> gcc -fno-builtin ./pow-error.c
Yes -fno-builtin certainly makes the results
consistent, but I would consider this result slightly
less correct.
> Unless the function call is optimized away.
Hmm, I guess I didn't think something as complicated
as pow would get optimized away. Thanks for the
in
I've been working on porting a simple terminal emulator application
from HP-UX 10.20 to Cygwin. All it does is make a few termio
settings on stdin, stdout and the specified serial port, then copy
characters from stdin to the serial port and from the serial port to
stdout. It seems to work fin
On 24 April 2007 00:53, Cary R. wrote:
> I had some more time to look into this and when the
> simple C program I mentioned earlier uses variables
> like the other program, incorrect results are
> produced. I have attached this C/C++ program. I
> certainly don't understand what is going on. I woul
On 2007-04-23 23:52Z, Cary R. wrote:
> I had some more time to look into this and when the
> simple C program I mentioned earlier uses variables
> like the other program, incorrect results are
> produced. I have attached this C/C++ program. I
> certainly don't understand what is going on. I would
>
On 4/23/07, Cary R. wrote:
I had some more time to look into this and when the
simple C program I mentioned earlier uses variables
like the other program, incorrect results are
produced. I have attached this C/C++ program. I
certainly don't understand what is going on. I would
have expected pow t
I had some more time to look into this and when the
simple C program I mentioned earlier uses variables
like the other program, incorrect results are
produced. I have attached this C/C++ program. I
certainly don't understand what is going on. I would
have expected pow to be pass-by value which shou
Michael D. Adams wrote:
> On 4/23/07, Dave Korn wrote:
>> On 24 April 2007 00:19, Michael D. Adams wrote:
>> > On 4/22/07, Brian Dessent <[EMAIL PROTECTED]> wrote:
>> The workaround for this problem that I have found is to set the
>> *Windows* path to include C:\cygwin\bin before running
On 4/23/07, Dave Korn wrote:
On 24 April 2007 00:19, Michael D. Adams wrote:
> On 4/22/07, Brian Dessent <[EMAIL PROTECTED]> wrote:
The workaround for this problem that I have found is to set the
*Windows* path to include C:\cygwin\bin before running setup.exe. So
for example thi
On 4/23/07, Dave Korn wrote:
On 24 April 2007 00:19, Michael D. Adams wrote:
> On 4/22/07, Brian Dessent <[EMAIL PROTECTED]> wrote:
Please, Michael, try and http://cygwin.com/acronyms#PCYMTNQREAIYR avoid
quoting people's email addresses. Thanks.
Thank you for pointing that out. I had nev
On 24 April 2007 00:19, Michael D. Adams wrote:
> On 4/22/07, Brian Dessent <[EMAIL PROTECTED]> wrote:
Please, Michael, try and http://cygwin.com/acronyms#PCYMTNQREAIYR avoid
quoting people's email addresses. Thanks.
The workaround for this problem that I have found is to set the
*W
On 4/22/07, Brian Dessent <[EMAIL PROTECTED]> wrote:
Brian Dessent wrote:
> > The workaround for this problem that I have found is to set the
> > *Windows* path to include C:\cygwin\bin before running setup.exe. So
> > for example this sequence works:
> >
> > set PATH=C:\cygwin\bin;%PATH%
> > s
On Sun, 22 Apr 2007, sethk wrote:
I've had some success using a different version of zsh on vista.
In the UnxUtils package, there is a version of zsh, named sh. (Not copied
or linked to zsh, for whatever reason, and, I should say, named sh.exe.)
Two things:
1) that's a win32 native exe, not
Oh yeah now works fine,
thank you *very* much,
dafi
2007/4/23, Dave Korn <[EMAIL PROTECTED]>:
On 23 April 2007 10:33, Davide Ficano wrote:
> I create a file containing uppercase characters in name using cygwin
> program and Windows shows them as %xx%xx.
>
> For example the command
>
> touch A
On 23 April 2007 10:42, sg wrote:
> hi friends,,
>
> how to run shell script on cygwin in windows..
chmod a+x ./script-name
./script-name
i.e. it has to have the executable bit set, and you need to specify the
current directory as part of the path if you haven't got the current directory
in
On 23 April 2007 10:33, Davide Ficano wrote:
> I create a file containing uppercase characters in name using cygwin
> program and Windows shows them as %xx%xx.
>
> For example the command
>
> touch AABBCC
>
> generate the filename %41%41%42%42%43%43%44%44
>
> How can I fix definetively this pr
hi friends,,
how to run shell script on cygwin in windows..
--
View this message in context:
http://www.nabble.com/how-to-run-shell-script-tf3630186.html#a10136740
Sent from the Cygwin Users mailing list archive at Nabble.com.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simpl
I create a file containing uppercase characters in name using cygwin
program and Windows shows them as %xx%xx.
For example the command
touch AABBCC
generate the filename %41%41%42%42%43%43%44%44
How can I fix definetively this problem?
best regards,
dafi
--
Unsubscribe info: http://cyg
22 matches
Mail list logo
