On Sat, 07 Oct 2017, Hiltjo Posthuma wrote:
> I think this is still not clear: what if a file is hidden due to its path?
> for example: $HOME/.config/somefile
>
> should it be visible or not?
>
> the stest man page uses the term "file" but "path" is meant.
> for example:
> -d Test that f
On Sat, Oct 07, 2017 at 11:54:05AM +0200, Kamil Cholewiński wrote:
> Hi Hiltjo,
>
> On Fri, 06 Oct 2017, Hiltjo Posthuma wrote:
> > Where is the patch?
>
> Attached, example below. However I would rather first discuss what
> should be the correct / expected behavior, before proposing a change.
>
Hi Hiltjo,
On Fri, 06 Oct 2017, Hiltjo Posthuma wrote:
> Where is the patch?
Attached, example below. However I would rather first discuss what
should be the correct / expected behavior, before proposing a change.
Going fast forward without a clear direction still gets you nowhere.
> $ ./stest
On Fri, Oct 06, 2017 at 03:50:28PM +0200, Kamil Cholewiński wrote:
> Hi list,
>
> stest from dmenu f428f3e produces broken results for paths starting with
> a "." that are not hidden files. I think this is best illustrated with a
> conversation with the shell:
>
> > $ ls -d ./bin
> > ./bin
> > $
Hi list,
stest from dmenu f428f3e produces broken results for paths starting with
a "." that are not hidden files. I think this is best illustrated with a
conversation with the shell:
> $ ls -d ./bin
> ./bin
> $ stest -d ./bin
> $ stest -ad ./bin
> ./bin
stest should probably treat the path with
