[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#16282: revisit; reasoning for not using ENV vars to provide workarou
From: |
Linda Walsh |
Subject: |
bug#16282: revisit; reasoning for not using ENV vars to provide workarounds for POSIX limitations? |
Date: |
Sat, 28 Dec 2013 16:00:48 -0800 |
User-agent: |
Thunderbird |
Paul Eggert wrote:
Linda Walsh wrote:
> Adding colons to the middle of the env var
That would make the var impossible to use from the shell.
----
That's what I thought you'd say -- meaning it would be well protected
against accidental usage.
However:
env foobar::snore=1 |grep ::
foobar::snore=1
And no matter what the name is, if it makes a standard
utility behave in odd ways, it'll break scripts that
don't expect the odd behavior. That's the essential
objection here.
----
Having "rm -fr ." not follow historical depth-first behavior and,
out of sequence, check for a . is "odd behavior".
That's the essential objection -- and I'm trying to get back
the original behavior -- not ask for some new behavior.