On 2005-09-04 CAiRO <[EMAIL PROTECTED]> wrote:
> Debian Bug Tracking System wrote on Sun, 04.09.2005:
[...]
>> It has been closed by one of the developers, namely
>> Andreas Metzler <[EMAIL PROTECTED]>.
[...]
>> On 2005-09-04 CAiRO <[EMAIL PROTECTED]> wrote:
[...]
>>> updatedb supports the environment variable PRUNEPATHS. In contrast
>>> to other environment variables which enumerate paths (e.g. PATH),
>>> the paths in PRUNEPATHS have to be split by space instead of a
>>> colon.
>> Where is the bug? There is no universal standard delimiter-character
>> and the updatedb's behavior is documented.
[...]
> Actually, it isn't documented (in the man page). The command line
> argument is documented and you'd have to conclude that the environment
> variable follows the same syntax which I didn't because I'm used delimit
> paths by a colon.
Hello,
"The environment variable PRUNEPATHS also sets this value."
Yours is a rather surprising reaction to that. If env-variable and
argument were using different syntax, the manpage would say in _big_
letters.
> It might not be a universal standard, but it's a
> defacto standard. Do you disagree that it would be advantageous for the
> user if the standard tools all used the same delimiter for their
> environment variables that contain paths?
No, not really. I'd say it was strange if I'd needed to use a
different syntax for environment and commandline. On top of that e.g.
OpenBSD's locate updatedb behaves the same way.
cu andreas
--
"See, I told you they'd listen to Reason," [SPOILER] Svfurlr fnlf,
fuhggvat qbja gur juveyvat tha.
Neal Stephenson in "Snow Crash"
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
