Date: Thu, 11 Nov 1999 16:28:53 -0800 (PST) From: Paul Eggert <eggert@twinsun.com> To: tstromberg@rtci.com Cc: freebsd-current@freebsd.org, bug-gnu-utils@gnu.org Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? Message-ID: <199911120028.QAA06638@shade.twinsun.com> In-Reply-To: <382B2711.E13A1CC8@rtci.com> (tstromberg@rtci.com) References: <382B2711.E13A1CC8@rtci.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Date: Thu, 11 Nov 1999 15:29:05 -0500 From: Thomas Stromberg <tstromberg@rtci.com> I just happened to notice this today. For some reason 'grep' seems to think that 'set' output is binary, not text. Most likely this is because the output of your `set' command contains binary data. In the past, this has been reported by people whose `set' command would output something like this: IFS=' ^@' where the `^@' in my message denotes a single NUL byte (control-@) in the original. If this is what's happening to you, then this is quite possibly a bug in your shell, since environment variables cannot possibly contain NUL bytes in Unix. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911120028.QAA06638>