Hello,
On 2018-12-20 6:46 p.m., L A Walsh wrote:
On 12/20/2018 5:21 PM, Assaf Gordon wrote:
If you are requesting such features (or others)
It's best to start a new thread for each topic.
They've already been discussed and ignored because there was no
way to add the feature for a defa
On 12/20/2018 5:21 PM, Assaf Gordon wrote:
If you are requesting such features (or others)
It's best to start a new thread for each topic.
They've already been discussed and ignored because there was no
way to add the feature for a default behavior other than
ENV vars or a config, both
Features where their non inclusion was unable to be met due to
pre-existing usage and where using or allowing behavior change based
on ENV vars was disallowed due to new gnu policies to minimize usage
of ENV vars. At the time config files were mentioned as a possible
solution but at the time I wa
Hello,
On 2018-12-20 5:36 p.m., L A Walsh wrote:
The below methods cannot alter or fix the problems that require
a configuration file.
Example: have 'rm -fr .' do a depth first removal and not pre-inspect
any argument before its children.
Whether or not to expand tabs in output so that outp
If the behaviors you want cannot be done now via command-line options,
that's not an argument against configuring via PATH; it's merely an
argument that you would like some random features that the programs
don't provide now.
The below methods cannot alter or fix the problems that require
a configuration file.
Example: have 'rm -fr .' do a depth first removal and not
pre-inspect any argument before its children.
Whether or not to expand tabs in output so that output to
a terminal that doesn't have tabstops every 8
tags 33787 wontfix
close 33787
stop
Hello,
On 12/17/18 11:12 PM, L A Walsh wrote:
I find that /etc/xattr.conf is being used to regulate behavior in gnu
tools.
It's worth noting that "/etc/xattr.conf" comes from a shared-library
(libattr.so) that is optionally used by cp(1).
It is not part of
On 12/20/18 2:40 PM, L A Walsh wrote:
But coreutils already does act differenty based on what
local libraries it pulls in at runtime.
Of course, and that doesn't affect the point. From coreutils viewpoint
those libraries are part of the system configuration, just as
/etc/passwd is, and just a
But coreutils already does act differenty based on what
local libraries it pulls in at runtime. If you want to
ensure they have the same behavior then they'd be statically
linked.
Second, coreutils behaves differently depending on the contents
of xattr.conf -- any util that deals with files will
On 12/17/18 11:12 PM, L A Walsh wrote:
I find that /etc/xattr.conf is being used to
regulate behavior in gnu tools.
Sure, just as lots of other system configuration files do, e.g.,
/etc/passwd. But these files are intended to act globally throughout the
operating system; they're not an except
10 matches
Mail list logo
