[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC] {print,}env -0

From: Pádraig Brady
Subject: Re: [RFC] {print,}env -0
Date: Mon, 26 Oct 2009 19:27:42 +0000
User-agent: Thunderbird (X11/20071008)

Eric Blake wrote:
> Since environment variables may contain newlines, but env and printenv 
> currently separate output entries via newline, we have a case of ambiguous 
> output.  For example, "env | sed -n '/^a.*=/ s,=.*,,p'" does not necessarily 
> tell you the set of environment variables beginning with "a", because I could 
> have done "export b=$'\na=c'".  What do list readers think of the idea of 
> adding:
> env -0/--null
> printenv -0/--null
> as a means of unambiguously representing the current contents of the 
> environment with NUL terminators instead of newlines?

It's consistent and makes sense.
I've not needed it myself (I think :)),
but I would say it's worth adding.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]