On 05/26/2017 10:23 AM, technosaurus wrote:
> Should this be |xprintf("%s%c", *ev, '\n'*!(toys.optflags_0));| ???
Oops. (Legitimate typo, adjacent keys.)
I tested env -0 and env without -0 before checking it in, but that turns
_any_ flag into -0, which I didn't check. :)
Thanks,
Rob
No, i do not have use case for this.
I've implemented pathchk because it was on roadmap, had a decent spec
and was small enough to do in a couple of evenings.
I'm happy to contribute, but most of the stuff on the roadmap is either
huge or in pending.
I'm not sure i have enough time to do
On 05/26/2017 10:54 AM, enh wrote:
>> Sigh I agree with this in principle (although I would have gone the
>> other way and enforced periods),
>
> happy to go the other way too; i only removed them because the current
> majority was periodless.
>
> (i haven't been able to guess whether it's
On 05/26/2017 11:21 AM, Ilya Kuzmich wrote:
> Signed-off-by: Ilya Kuzmich
> ---
> tests/pathchk.test | 85 ++
> toys/posix/pathchk.c | 95
>
> 2 files changed, 180