Re: The C locale

Christopher Faylor: >Andy Koppe: >>Trying to reply to [banned]'s post about locale issues, I got >>rather confused about the C locale. The manual and the POSIX standard >>say that it supports ASCII only, so in theory anything above 0x7F >>should be rejected. In practice though, both Cygwin 1.5 and

Re: GNU screen hangs

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 ag

Re: struct dirent.d_reclen

-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_recle

Re: struct dirent.d_reclen

-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 pro

Re: std::arg() bug : not repetitive ?

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

Re: How to install QT in CYGWIN

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

Re: struct dirent.d_reclen

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, whos

Re: std::arg() bug : not repetitive ?

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

Re: [ANNOUNCEMENT] Updated: screen, now with 256-color support!

> '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

Re: [ANNOUNCEMENT] Updated: screen, now with 256-color support!

> > 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=scr

Re: [ANNOUNCEMENT] Updated: screen, now with 256-color support!

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/sc

Re: std::arg() bug : not repetitive ?

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.

Re: std::arg() bug : not repetitive ?

--- 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 (

Re: GNU screen hangs

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 -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/

struct dirent.d_reclen

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 get

Re: std::arg() bug : not repetitive ?

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 > #include "oct-cmplx.h" > > int main () > { > Complex z1 (1.0, 1.0), z2

Re: GNU screen hangs

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

Re: [ANNOUNCEMENT] Updated: screen, now with 256-color support!

> 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 th

Re: [ANNOUNCEMENT] Updated: screen, now with 256-color support!

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 p

Re: [ANNOUNCEMENT] Updated: screen, now with 256-color support!

> > 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

std::arg() bug : not repetitive ?

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 #include "oct-cmplx.h" int main () { Complex z1 (1.0, 1.0), z2 (1.0, 1.0); std::cout << (arg(z1)) << '\

Re: 1.7.0-60: diff -qr crashes

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),

Re: [ANNOUNCEMENT] Updated: screen, now with 256-color support!

Andy Koppe 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

Re: 1.7.0-60: diff -qr crashes

be better if I released a snapshot before a > new release. > > Could you try to duplicate this with today's snapshot from: > > http://cygwin.com/snapshots/ > > I'm generating it now. Please wait for the September 1 snapshot to > show up before trying anything

Re: 1.7.0-60: diff -qr crashes

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 compar

Re: GNU screen hangs

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 -- Prob

Re: GNU screen hangs

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 The gene pool sure could use a little chlorine. -- Problem reports: http://cygwin.com/problems.html FAQ:

1.7.0-60: diff -qr crashes

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 comman

Re: BitDefender again

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 F

Re: [OT] Re: GNU screen hangs

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

Re: [OT] Re: GNU screen hangs

Ah, censorship. The Official Truth will become the Truth, when the opposition is censored. On 2009-09-01, Dave Korn 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, arrogance and > me-first egotism.

[OT] Re: GNU screen hangs

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 fa

Re: GNU screen hangs

On Tue, Sep 01, 2009 at 10:23:58AM +, TV wrote: >On 2009-09-01, Dave Korn 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 >ton

Re: GNU screen hangs

On 2009-09-01, Dave Korn 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, have to make everyth

Re: GNU screen hangs

TV wrote: > On 2009-08-31, Christopher Faylor 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 certainly not just him who thinks so,

Re: GNU screen hangs

On 2009-08-31, Christopher Faylor 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 going to complete my transition from Linux