Paul Eggert wrote:
L A Walsh wrote:
The idea would be to have it be transparent. Adding
on various output filters is hardly transparent.
Nor is having behavior depend on environment variables.
---
The behavior isn't dependent on environment variables.
The behavior is selected by
L A Walsh wrote:
The idea would be to have it be transparent. Adding
on various output filters is hardly transparent.
Nor is having behavior depend on environment variables.
As for env-vars. What problems are you envisioning.
Shell scripts might stop working because the environment
tail -f letsencrypt.log
tail: unrecognized file system type 0x53464846 for ‘letsencrypt.log’.
please report this to bug-coreutils@gnu.org. reverting to polling
Paul Eggert wrote:
L A Walsh wrote:
I'm working on some loose ends, but basically,
First, it would default to providing no change. ;-)
Through use of a switch it can expand the tabs to spaces
using a default of every 8th column (after 1) (using a
switch value of 'ExpandTo').
And with 2 env
On 01/28/2017 12:15 AM, Owen Leibman wrote:
> Testing a script to see how it handled invalid data, I had it execute the
> command:
> date -d "x023-04-05 01:00"
> Somewhat surprisingly, this was not treated as an error. The response was:
> Tue Apr 4 06:07:02 LMT 0023
>
> This happened on a Ubuntu
L A Walsh wrote:
I'm working on some loose ends, but basically,
First, it would default to providing no change. ;-)
Through use of a switch it can expand the tabs to spaces
using a default of every 8th column (after 1) (using a
switch value of 'ExpandTo').
And with 2 env vars, TTY_TABSIZE & TT
Owen Leibman wrote:
Is the date command behaving as it should for all these examples?
Those letters are military time zone abbreviations, so yes.
