public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@cygnus.com>
To: "E. Robert Tisdale" <edwin@netwood.net>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: setmode (long)
Date: Tue, 02 Mar 1999 18:59:00 -0000	[thread overview]
Message-ID: <19990302220000.A3492@cygnus.com> (raw)
In-Reply-To: <36D51691.6E1579DF@netwood.net>; from E. Robert Tisdale on Thu, Feb 25, 1999 at 01:23:29AM -0800

On Thu, Feb 25, 1999 at 01:23:29AM -0800, E. Robert Tisdale wrote:
>Christopher Faylor wrote:
>> That's right in older Cygwin's
>> setting the mode to TEXT didn't necessarily change the mode.
>> This should be fixed in the snapshots.
>>
>> We have gone around and around on this behavior in the developers list
>> but I think that the current implementation is correct.
>
>What do you mean by "older Cygwin's"?
>I downloaded Beta 20.1 and installed it.
>
>Do you mean that the problem has already been fixed in the snapshots?
>Has anyone actually tested (test'd) the snapshots
>to determine whether this behavior still persists or not?

Yes.  I meant that this has been fixed in the latest snapshots.

>Should I download the latest snapshot
>and use it to compile my application programs?
>Or should I wait until the next release
>before upgrading my compiler?

That's not a decision I can make.  You're welcome to try a snapshot
but snapshots carry no guarantees as far as stability is concerned.
However, this is a DLL problem so you should not have to recompile
your program to see a benefit.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

WARNING: multiple messages have this Message-ID
From: Christopher Faylor <cgf@cygnus.com>
To: "E. Robert Tisdale" <edwin@netwood.net>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: setmode (long)
Date: Wed, 31 Mar 1999 19:45:00 -0000	[thread overview]
Message-ID: <19990302220000.A3492@cygnus.com> (raw)
Message-ID: <19990331194500.QqXq3BHQ9jp5Y7vsAKWfzABPQIes74bg37gZ-v712dc@z> (raw)
In-Reply-To: <36D51691.6E1579DF@netwood.net>

On Thu, Feb 25, 1999 at 01:23:29AM -0800, E. Robert Tisdale wrote:
>Christopher Faylor wrote:
>> That's right in older Cygwin's
>> setting the mode to TEXT didn't necessarily change the mode.
>> This should be fixed in the snapshots.
>>
>> We have gone around and around on this behavior in the developers list
>> but I think that the current implementation is correct.
>
>What do you mean by "older Cygwin's"?
>I downloaded Beta 20.1 and installed it.
>
>Do you mean that the problem has already been fixed in the snapshots?
>Has anyone actually tested (test'd) the snapshots
>to determine whether this behavior still persists or not?

Yes.  I meant that this has been fixed in the latest snapshots.

>Should I download the latest snapshot
>and use it to compile my application programs?
>Or should I wait until the next release
>before upgrading my compiler?

That's not a decision I can make.  You're welcome to try a snapshot
but snapshots carry no guarantees as far as stability is concerned.
However, this is a DLL problem so you should not have to recompile
your program to see a benefit.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


  parent reply	other threads:[~1999-03-02 18:59 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-24  0:31 E. Robert Tisdale
     [not found] ` < 36D39A03.89B3C703@netwood.net >
1999-02-24 11:42   ` Christopher Faylor
1999-02-25  1:26     ` E. Robert Tisdale
     [not found]       ` < 36D51691.6E1579DF@netwood.net >
1999-02-25  3:51         ` ... is not writable by you Sebastien Barre
     [not found]           ` < 4.1.19990225124802.02724850@mail.club-internet.fr >
1999-02-25  7:21             ` Dennis Newbold
     [not found]               ` < Pine.LNX.3.96.990225083630.12938A-100000@blackberry.ivs.com >
1999-02-25  9:41                 ` Sebastien Barre
1999-02-25 11:14                   ` John Fortin
     [not found]                     ` < 36D59F7D.81FA327@ibm.net >
1999-02-25 16:33                       ` Sebastien Barre
1999-02-28 23:02                         ` Sebastien Barre
1999-02-28 23:02                     ` John Fortin
1999-02-28 23:02                   ` Sebastien Barre
1999-02-28 23:02               ` Dennis Newbold
1999-02-28 23:02           ` Sebastien Barre
1999-02-25  8:02         ` setmode (long) DJ Delorie
1999-02-25 22:44           ` E. Robert Tisdale
1999-02-28 23:02             ` E. Robert Tisdale
1999-02-28 23:02           ` DJ Delorie
1999-02-25  9:25         ` Mumit Khan
1999-02-28 23:02           ` Mumit Khan
1999-02-28 23:02       ` E. Robert Tisdale
1999-03-02 18:59       ` Christopher Faylor [this message]
1999-03-03 19:29         ` E. Robert Tisdale
     [not found]           ` < 36DDFD4C.B4B6F7C4@netwood.net >
1999-03-04  8:17             ` Chris Faylor
1999-03-31 19:45               ` Chris Faylor
1999-03-31 19:45           ` E. Robert Tisdale
1999-03-31 19:45         ` Christopher Faylor
1999-02-28 23:02     ` Christopher Faylor
1999-02-28 23:02 ` E. Robert Tisdale
     [not found] <3.0.5.32.19990225144311.0084fc50@pop.ne.mediaone.net>
1999-02-25 12:12 ` E. Robert Tisdale
     [not found]   ` < 36D5ADF0.C5FC769@netwood.net >
1999-02-25 18:48     ` Pierre A. Humblet
     [not found]       ` < 3.0.5.32.19990225215015.00857270@pop.ne.mediaone.net >
1999-02-25 18:57         ` Mumit Khan
1999-02-25 22:29           ` E. Robert Tisdale
1999-02-28 23:02             ` E. Robert Tisdale
1999-02-28 23:02           ` Mumit Khan
1999-02-28 23:02       ` Pierre A. Humblet
1999-02-28 23:02   ` E. Robert Tisdale
     [not found] ` <3.0.5.32.19990225152844.008374c0@pop.ne.mediaone.net>
1999-02-25 21:56   ` E. Robert Tisdale
1999-02-28 23:02     ` E. Robert Tisdale
1999-02-26  2:47 Bernard Dautrevaux
1999-02-28 23:02 ` Bernard Dautrevaux
1999-03-03 19:19 ` E. Robert Tisdale
1999-03-31 19:45   ` E. Robert Tisdale

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19990302220000.A3492@cygnus.com \
    --to=cgf@cygnus.com \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=edwin@netwood.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).