From: Volker Quetschke <quetschke@scytek.de>
To: cygwin@cygwin.com
Subject: Re: bash-3.1-7^[$B!!^[(BBUG
Date: Thu, 14 Sep 2006 17:22:00 -0000 [thread overview]
Message-ID: <45098FB4.40703@scytek.de> (raw)
In-Reply-To: <004c01c6d821$68f5fdf0$a501a8c0@CAM.ARTIMI.COM>
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
Dave Korn wrote:
> On 14 September 2006 17:59, Volker Quetschke wrote:
>
>> Hi!
>
>> (snip)
>>> +#ifdef __CYGWIN__
>>> + /* lseek'ing on text files is problematic; lseek reports the true
>>> + file offset, but read collapses \r\n and returns a character
>>> + count. We cannot reliably seek backwards if nr is smaller than
>>> + the seek offset encountered during the read, and must instead
>>> + treat the stream as unbuffered. */
>>> + if ((bp->b_flag & (B_TEXT | B_UNBUFF)) == B_TEXT)
>> ------------------------^^^^^^^^^^^^^^^^^ ^^^^^^
>> part of the patch looks suspicious to me. You probably just want to test
>> if the LHS expression is true.
>
> You reckon? That looks to me like a test for B_TEXT is set *and* B_UNBUFF
> is cleared. Since the action we're going to take if this test succeeds is to
> set the stream unbuffered, there's no need to do it for a stream that already
> /is/ unbuffered. That's how it looks to me at first glance, anyway.
See, it was the lack of coffee ;) Sorry for the noise.
Volker
(snap)
--
PGP/GPG key (ID: 0x9F8A785D) available from wwwkeys.de.pgp.net
key-fingerprint 550D F17E B082 A3E9 F913 9E53 3D35 C9BA 9F8A 785D
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2006-09-14 17:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 4:38 bash-3.1-7^[$B!!^[(BBUG Eric Blake
2006-09-13 5:25 ` bash-3.1-7^[$B!!^[(BBUG Christopher Faylor
2006-09-13 14:33 ` bash-3.1-7^[$B!!^[(BBUG Eric Blake
2006-09-13 20:07 ` bash-3.1-7^[$B!!^[(BBUG Shankar Unni
2006-09-13 20:37 ` bash-3.1-7^[$B!!^[(BBUG mwoehlke
2006-09-13 21:48 ` bash-3.1-7^[$B!!^[(BBUG Eric Blake
2006-09-13 22:08 ` bash-3.1-7^[$B!!^[(BBUG mwoehlke
2006-09-13 23:46 ` bash-3.1-7^[$B!!^[(BBUG Volker Quetschke
2006-09-13 23:58 ` bash-3.1-7^[$B!!^[(BBUG David Rothenberger
2006-09-14 0:30 ` bash-3.1-7^[$B!!^[(BBUG Larry Hall (Cygwin)
2006-09-18 2:48 ` bash-3.1-7^[$B!!^[(BBUG Carlo Florendo
2006-09-18 2:54 ` bash-3.1-7^[$B!!^[(BBUG Carlo Florendo
2006-09-14 0:19 ` bash-3.1-7^[$B!!^[(BBUG Christopher Faylor
2006-09-14 1:09 ` bash-3.1-7^[$B!!^[(BBUG Volker Quetschke
2006-09-14 2:07 ` bash-3.1-7^[$B!!^[(BBUG Christopher Faylor
2006-09-14 11:13 ` bash-3.1-7^[$B!!^[(BBUG Eric Blake
2006-09-14 16:58 ` bash-3.1-7^[$B!!^[(BBUG Volker Quetschke
2006-09-14 17:15 ` bash-3.1-7^[$B!!^[(BBUG Dave Korn
2006-09-14 17:22 ` Volker Quetschke [this message]
2006-09-14 17:26 ` bash-3.1-7^[$B!!^[(BBUG Eric Blake
2006-09-21 3:50 ` bash-3.1-7^[$B!!^[(BBUG Christopher Layne
2006-09-14 15:21 ` bash-3.1-7 bug mwoehlke
2006-09-21 3:48 ` bash-3.1-7^[$B!!^[(BBUG Christopher Layne
2006-09-21 3:37 ` bash-3.1-7^[$B!!^[(BBUG Christopher Layne
-- strict thread matches above, loose matches on Subject: below --
2006-09-13 4:13 bash-3.1-7^[$B!!^[(BBUG Eric Blake
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=45098FB4.40703@scytek.de \
--to=quetschke@scytek.de \
--cc=cygwin@cygwin.com \
/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).