On 2009-08-31, Christopher Faylor cgf-use-the-mailinglist-ple...@cygwin.com
wrote:
Apparently you don't know who I am.
An even bigger pile of shit than this project. A project leader
pretending to be an army sergeant with users rookies required
to follow his ridiculous commands.
I guess I'm
TV wrote:
On 2009-08-31, Christopher Faylor
cgf-use-the-mailinglist-ple...@cygwin.com wrote:
Apparently you don't know who I am.
An even bigger pile of
Don't kid yourself: it's you that's at fault, not the whole rest of the
world. You've been rude and arrogant from your first post. It's
On 2009-09-01, Dave Korn da...@googlemail.com wrote:
Don't kid yourself: it's you that's at fault, not the whole rest of the
world. You've been rude and arrogant from your first post.
Oh, this is must be a cultural thing about americans and
their tanned tongues. Can't stay to the facts,
On Tue, Sep 01, 2009 at 10:23:58AM +, TV wrote:
On 2009-09-01, Dave Korn da...@googlemail.com wrote:
Don't kid yourself: it's you that's at fault, not the whole rest of the
world. You've been rude and arrogant from your first post.
Oh, this is must be a cultural thing about americans and
TV wrote:
On 2009-09-01, Dave Korn wrote:
Wow. You kind of quoted my email address, but then you went and changed it
into some poor innocent bystander's account. Whoever that is won't be pleased
with you.
this space left blank for Tuomo to explain why that's the innocent
bystander's
Ah, censorship. The Official Truth will become the Truth,
when the opposition is censored.
On 2009-09-01, Dave Korn davek.spamt...@googlemail.com wrote:
Nonsense, it's got nothing to do with the way you say it, it's the content
of your message that nobody likes: self-regarding vanity,
One more time wrote:
Ah, censorship.
zOMG we is suppressing your freedumb of speach! O noes! Call for the
WH-bulance!
Seriously, that is the kind of pathetic nonsense spammers come out with.
You clearly read the messages through some anti-tuomov glasses,
as most of the FOSS herd
Or you can go the easy route, and follow the instructions they have
provided to rebase cygwin.dll.
I shall try their instructions and report back. (There must be other
BitDefender users similarily inconvenienced by version 2010 :)
--
Problem reports: http://cygwin.com/problems.html
Hi,
I've installed Cygwin Beta 1.7.0 (version -51) around mid of July.
Currently, version -60 is installed. Now (at least since version -53 or
so) I repeatedly encounter a bug with diff (diffutils 2.8.7-1). I use
diff to compare my working directory with the files on an usb stick. The
exact
TV wrote:
Oh, this is must be a cultural thing about americans and their tanned
tongues.
Excuse me, I'm off to the tongue tanning salon... ;-)
--
Andrew DeFaria http://defaria.com
The gene pool sure could use a little chlorine.
--
Problem reports: http://cygwin.com/problems.html
FAQ:
On Tue, Sep 01, 2009 at 07:12:51AM -0700, Andrew DeFaria wrote:
TV wrote:
Oh, this is must be a cultural thing about americans and their tanned
tongues.
Excuse me, I'm off to the tongue tanning salon... ;-)
Ok. I've got to stop drinking coffee while reading the cygwin list...
cgf
--
Problem
On Tue, Sep 01, 2009 at 04:01:06PM +0200, Torsten Sch?tze wrote:
Hi,
I've installed Cygwin Beta 1.7.0 (version -51) around mid of July.
Currently, version -60 is installed. Now (at least since version -53 or
so) I repeatedly encounter a bug with diff (diffutils 2.8.7-1). I use
diff to compare my
trying anything.
Okay, here we are. Using the 2009-09-01 snapshot
(cygwin1-20090901.dll.bz2, cygwin1-20090901.dbg.bz2) I obtain:
First, in directory 2009 (corresponds to diff.exe.stackdump-1), see
attachment diff.exe.stackdump-1-new
Exception: STATUS_ACCESS_VIOLATION at eip=C128
eax= ebx
Andy Koppe andy.koppe at gmail.com writes:
Andrew Schulman:
Instructions for starting screen with 256 color support are in
/usr/share/doc/screen/README.Cygwin. In brief, you have to invoke screen
as
TERM=screen-256color screen
I don't think that's quite right. Screen needs to be
On Tue, Sep 01, 2009 at 04:47:16PM +0200, Torsten Sch?tze wrote:
Christopher Faylor wrote:
Okay, here we are. Using the 2009-09-01 snapshot
(cygwin1-20090901.dll.bz2, cygwin1-20090901.dbg.bz2) I obtain:
First, in directory 2009 (corresponds to diff.exe.stackdump-1), see
attachment
Hi DaveK,
the following test case on complex numbers
is producing, puzzling result on cygwin (both 1.5 and 1,7)
with gcc-4.3.2 (and also 3.4.4), while working on other platform:
#include iostream
#include oct-cmplx.h
int main ()
{
Complex z1 (1.0, 1.0), z2 (1.0, 1.0);
std::cout (arg(z1))
TERM=xterm-256color screen -T screen-256color
Instead of specifying -T screen-256color every time, one can just put
'term screen-256color' into .screenrc. I'll update the docs to show this
when I make the release current.
Is there any reason that I shouldn't put this command into the
Andrew Schulman:
TERM=xterm-256color screen -T screen-256color
Instead of specifying -T screen-256color every time, one can just put
'term screen-256color' into .screenrc. I'll update the docs to show this
when I make the release current.
Is there any reason that I shouldn't put this
Andrew Schulman:
TERM=xterm-256color screen -T screen-256color
Instead of specifying -T screen-256color every time, one can just put
'term screen-256color' into .screenrc. I'll update the docs to show this
when I make the release current.
Is there any reason that I shouldn't put
Christopher Faylor wrote:
On Tue, Sep 01, 2009 at 07:12:51AM -0700, Andrew DeFaria wrote:
TV wrote:
Oh, this is must be a cultural thing about americans and their tanned
tongues.
Excuse me, I'm off to the tongue tanning salon... ;-)
Ok. I've got to stop drinking coffee while reading the
Marco Atzeri wrote:
Hi DaveK,
the following test case on complex numbers
is producing, puzzling result on cygwin (both 1.5 and 1,7)
with gcc-4.3.2 (and also 3.4.4), while working on other platform:
#include iostream
#include oct-cmplx.h
int main ()
{
Complex z1 (1.0, 1.0), z2
Wish list (probably post 7.1): As long as we are making struct dirent more like
Linux with the recent addition of d_type, we should probably also burn two of
the remaining 3 __d_unused1 bytes to declare unsigned short d_reclen, whose
value is always strlen(d_name), so that applications could
Andrew DeFaria wrote:
Excuse me, I'm off to the tongue tanning salon... ;-)
Crazy Americans! Tanning one end while bleaching the other! What's
going on in this country?!
--
Mark J. Reed markjr...@gmail.com
--
Problem reports: http://cygwin.com/problems.html
FAQ:
--- Mar 1/9/09, Dave Korn ha scritto:
Da: Dave Korn
Oggetto: Re: std::arg() bug : not repetitive ?
A: cygwin cygwin.com
Data: Martedì 1 settembre 2009, 19:14
Marco Atzeri wrote:
Hi DaveK,
the following test case on complex numbers
is producing, puzzling result on cygwin (both 1.5
Marco Atzeri wrote:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=323#c2
$g++-4 -ffloat-store comp_2.cc -O3 -o comp_4
./comp_4
0.785398
0.785398
0
0
Ah, good, thanks for the diagnosis. IIUC this is basically fixed in GCC
HEAD now and 4.5.0 shouldn't suffer the same problem.
Andrew Schulman:
Instead of specifying -T screen-256color every time, one can just put
'term screen-256color' into .screenrc. I'll update the docs to show this
when I make the release current.
Is there any reason that I shouldn't put this command into the default
/etc/screenrc file?
You're talking about setting e.g. TERM=xterm-256color in the environment by
default, but I was asking whether it would cause any harm to put 'term
screen-256color' into the default /etc/screenrc. Know any reason that I
shouldn't?
Well, yes. 'term screen-256color' sets
'term screen-256color' sets TERM=screen-256color in the
environment of programs running inside screen, hence any program or
script that recognises screen but not screen-256color will no
longer work as expected.
Btw, a different approach to enabling 256 colour support by default,
which doesn't
Dave Korn wrote:
IIUC this is basically fixed in GCC
HEAD now and 4.5.0 shouldn't suffer the same problem.
Just for completeness...
With 4.5-20090827 snapshot, it does:
$ g++-4.5 arg_bug.cpp -o0 -o arg_bug
$ ./arg_bug.exe
0.785398
0.785398
1
-3.06287e-17
being (on 1.7):
$ g++-4.5 -v
Using
On Tue, Sep 01, 2009 at 05:39:02PM +, Eric Blake wrote:
Wish list (probably post 7.1): As long as we are making struct dirent more
like
Linux with the recent addition of d_type, we should probably also burn two of
the remaining 3 __d_unused1 bytes to declare unsigned short d_reclen, whose
On 25/08/2009 11:19, Larry Hall (Cygwin) wrote:
On 08/25/2009 04:28 AM, Pok Wilson wrote:
I am intending to use QT4.5.3 to create my GUI.
4.5.3? The latest upstream release is 4.5.2.
Sorry my mistake, you're right its QT 4.5.2.
I'm no QT expert (and I actually haven't even touched it
Angelo Graziosi wrote:
Dave Korn wrote:
IIUC this is basically fixed in GCC
HEAD now and 4.5.0 shouldn't suffer the same problem.
Just for completeness...
With 4.5-20090827 snapshot, it does:
$ g++-4.5 arg_bug.cpp -o0 -o arg_bug
$ ./arg_bug.exe
0.785398
0.785398
1
-3.06287e-17
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Christopher Faylor on 9/1/2009 5:37 PM:
Maybe you mean d_namlen?
Yes; serves me right for confusing readdir(2) and readdir(3) man pages.
It is not a given that adding d_reclen would speed anything up since it
cause every single
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 9/1/2009 7:10 PM:
According to Christopher Faylor on 9/1/2009 5:37 PM:
Maybe you mean d_namlen?
Yes; serves me right for confusing readdir(2) and readdir(3) man pages.
Actually, it looks like Linux has only d_reclen
Mark J. Reed wrote:
Andrew DeFaria wrote:
Excuse me, I'm off to the tongue tanning salon... Â ;-)
Crazy Americans! Tanning one end while bleaching the other! What's
going on in this country?!
Here in America we treat both black and white equally! ;-)
Now what was I supposed to be bleaching
Jose Luis wrote:
I can start xterm from startxwin.bat:
%RUN% xterm -e /usr/bin/bash -l
but no rxvt:
%RUN% rxvt -bg white -fg black -e /bin/bash
although it can be started from command line:
jlfd...@jlfdiazwxp ~
$ rxvt -bg white -fg black -e
CVSROOT:/cvs/uberbaum
Module name:winsup
Changes by: c...@sourceware.org 2009-09-01 14:25:10
Modified files:
cygwin : ChangeLog select.cc
Log message:
* select.cc (peek_console): Always check window size when there is ANY
keyboard
activity.
CVSROOT:/cvs/src
Module name:src
Changes by: keithmarsh...@sourceware.org2009-09-01 20:41:55
Modified files:
winsup/mingw : ChangeLog
winsup/mingw/include: stdio.h
Log message:
Avoid multiple link time definitions of _printf() for C++
Patches:
On Aug 30 21:38, Christian Franke wrote:
Corinna Vinschen wrote:
If you plan to run a Cygwin application with restricted rights from your
administrative account, the IMHO right way would be to start the Cygwin
application through another application which creates a *really*
restricted user
39 matches
Mail list logo
