|
A strong argument for a chase? flag for file-info, and a issue which needs to be considered
hga@xxxxxx
(26 Aug 2019 15:21 UTC)
|
||
|
(missing)
|
||
|
Re: A strong argument for a chase? flag for file-info, and a issue which needs to be considered
hga@xxxxxx
(26 Aug 2019 18:00 UTC)
|
||
|
Re: A strong argument for a chase? flag for file-info, and a issue which needs to be considered
Lassi Kortela
(26 Aug 2019 15:28 UTC)
|
||
|
Re: A strong argument for a chase? flag for file-info, and a issue which needs to be considered
hga@xxxxxx
(26 Aug 2019 15:39 UTC)
|
||
|
Re: A strong argument for a chase? flag for file-info, and a issue which needs to be considered
Lassi Kortela
(26 Aug 2019 15:46 UTC)
|
||
|
Re: A strong argument for a chase? flag for file-info, and a issue which needs to be considered
Lassi Kortela
(26 Aug 2019 15:48 UTC)
|
||
|
Re: A strong argument for a chase? flag for file-info, and a issue which needs to be considered hga@xxxxxx (26 Aug 2019 16:04 UTC)
|
||
Re: A strong argument for a chase? flag for file-info, and a issue which needs to be considered hga@xxxxxx 26 Aug 2019 16:04 UTC
> From: Lassi Kortela <xxxxxx@lassi.io> > Date: Monday, August 26, 2019 10:48 AM > To "chase" a symlink is funny but the default Unix term if "follow". > Which one should we pick? "chase?" is how the argument is named in the scsh documentation, and code, but there's no reason to follow, shall we say, its names for arguments, which are placeholders. follow? works for me. - Harold