[Newbie] 'set|grep' doesn't work as expected

[Newbie] 'set|grep' doesn't work as expected

[Thiago F.G.Albuquerque]

Hi,

In bash I can type

set | grep <something>

and it's ok.

In zsh, it gives me the message:

Binary file (standard input) matches

Why?

Thiago

Re: [Newbie] 'set|grep' doesn't work as expected

[Phil Pennock]

[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]

On 2002-05-24 at 20:27 -0300, Thiago F. G. Albuquerque wrote:
> In bash I can type
> 
> set | grep <something>
> 
> and it's ok.
> 
> In zsh, it gives me the message:
> 
> Binary file (standard input) matches
> 
> Why?

Because you have something in the environment with a non-plaintext
representation.

Perhaps: export foo="$(print '\efred')"

It could be that you've even inherited a key=value pair where the key is
the problem.  But zsh itself won't let you set such.

Perhaps you have UTF or ISO 8859 data in a string and your grep doesn't
know about the local.

If your grep supports the "-a" option, to force interpretation as ASCII,
perhaps you could try that.

Or track down _why_ you have strange values in your environment.


If this is at all related to your use of zsh vs bash, then you've put
binary data into the environment in one of your zsh startup files.
-- 
I just felt a great disturbance in the net, as if millions of packets
suddenly cried out in terror, and were suddenly discarded. -- amt

[-- Attachment #2: Type: application/pgp-signature, Size: 187 bytes --]

Re: [Newbie] 'set|grep' doesn't work as expected

[Preben Peppe Guldberg]

Således berettede Phil Pennock (Phil.Pennock@globnix.org) den [020525]:
> On 2002-05-24 at 20:27 -0300, Thiago F. G. Albuquerque wrote:
> > In bash I can type

> > set | grep <something>

> > and it's ok.

> > In zsh, it gives me the message:

> > Binary file (standard input) matches

> > Why?

> Because you have something in the environment with a non-plaintext
> representation.

I think that would be IFS. In bash the default is <space><tab><newline>,
while zsh add <nul> to these.

Peppe
-- 
                                      "Before you criticize someone, walk
Preben "Peppe" Guldberg  __/-\__       a mile in his shoes. That way, if
c928400@student.dtu.dk    (o o)        he gets angry, he'll be a mile away
----------------------oOOo (_) oOOo--  - and barefoot."    --Sarah Jackson

Re: [Newbie] 'set|grep' doesn't work as expected

[Phil Pennock]

[-- Attachment #1: Type: text/plain, Size: 459 bytes --]

On 2002-05-25 at 01:59 +0200, Preben Peppe Guldberg wrote:
> Således berettede Phil Pennock (Phil.Pennock@globnix.org) den [020525]:
> > Because you have something in the environment with a non-plaintext
> > representation.
> 
> I think that would be IFS. In bash the default is <space><tab><newline>,
> while zsh add <nul> to these.

Uhm, why are you routinely exporting IFS to your environment?
-- 
It's never too late to have a happy childhood.

[-- Attachment #2: Type: application/pgp-signature, Size: 187 bytes --]

Re: [Newbie] 'set|grep' doesn't work as expected

[Dan Nelson]

In the last episode (May 25), Phil Pennock said:
> On 2002-05-25 at 01:59 +0200, Preben Peppe Guldberg wrote:
> > Sσledes berettede Phil Pennock (Phil.Pennock@globnix.org) den [020525]:
> > > Because you have something in the environment with a non-plaintext
> > > representation.
> > 
> > I think that would be IFS. In bash the default is <space><tab><newline>,
> > while zsh add <nul> to these.
> 
> Uhm, why are you routinely exporting IFS to your environment?

Set shows all variables, exported and local.

-- 
	Dan Nelson
	dnelson@allantgroup.com

Re: [Newbie] 'set|grep' doesn't work as expected

[Thiago F.G. Albuquerque]

Preben Peppe Guldberg wrote:

> Således berettede Phil Pennock (Phil.Pennock@globnix.org) den [020525]:
> 
>>On 2002-05-24 at 20:27 -0300, Thiago F. G. Albuquerque wrote:
>>
>>>In bash I can type
>>>
> 
>>>set | grep <something>
>>>
> 
>>>and it's ok.
>>>
> 
>>>In zsh, it gives me the message:
>>>
> 
>>>Binary file (standard input) matches
>>>
> 
>>>Why?
>>>
> 
>>Because you have something in the environment with a non-plaintext
>>representation.
>>
> 
> I think that would be IFS. In bash the default is <space><tab><newline>,
> while zsh add <nul> to these.


You're right. Look:

1 ~> echo $IFS | dump
0000  20  9  A  0  A                                     .....

This is <space>, '\t', '\n' and '\0'. The last "A" is the '\n' printed by echo.

In bash, IFS is set to nothing.

I unset IFS in zsh and "set|grep" worked again.
Using "grep -a" also works.

Is it ok if I remove \0 from IFS?

I would like to thank everybody who replied to my message. Thank you.

Thiago

Re: [Newbie] 'set|grep' doesn't work as expected

[Borsenkow Andrej]

В Вск, 26.05.2002, в 01:45, Thiago F.G. Albuquerque написал:
> You're right. Look:
> 
> 1 ~> echo $IFS | dump
> 0000  20  9  A  0  A                                     .....
> 
> This is <space>, '\t', '\n' and '\0'. The last "A" is the '\n' printed by echo.
> 
> In bash, IFS is set to nothing.
> 

Impossible (unless you either unset it yourself or have very broken
version). (Value of) IFS is used to split input line into words in some
contexts; I am sure about `read' builtin and possibly some others
(select?). By default it is set to space, TAB and LF for sure; I am not
sure if \0 is Zsh extension (anybody cares to lookup in SUS?)

> I unset IFS in zsh and "set|grep" worked again.
> Using "grep -a" also works.
> 
> Is it ok if I remove \0 from IFS?
> 

Zsh itself does not depend on its value. But you may have some scripts
that expect it to contain \0. 

-andrej

RE: [Newbie] 'set|grep' doesn't work as expected

[Borsenkow Andrej]

Ю В Вскб 26ю05ю2002б в 01Ж45б Ершфпщ АюПю Фдигйгукйгу написалЖ
> > You're right. Look:
> >
> > 1 ~> echo $IFS | dump
> > 0000  20  9  A  0  A                                     .....
> >
> > This is <space>, '\t', '\n' and '\0'. The last "A" is the '\n'
printed by
> echo.
> >
> > In bash, IFS is set to nothing.
> >
> 
> Impossible (unless you either unset it yourself or have very broken
> version). (Value of) IFS is used to split input line into words in
some
> contexts; I am sure about `read' builtin and possibly some others
> (select?). By default it is set to space, TAB and LF for sure; I am
not
> sure if \0 is Zsh extension (anybody cares to lookup in SUS?)
> 

For the record - neither SUS V2 nor SUS V3 specify default IFS value.
The only statement is, if IFS is not defined shell behaves as if it
contains space, TAB and NL.

-andrej