--- Begin Message ---
Subject: |
gash-utils & fzf conflict |
Date: |
Wed, 08 Dec 2021 18:23:04 +0700 |
Hello,
Gash-utils causes fzf to fail.
After installing gash-utils, attempting `bash5.0$ fzf` produces:
```
[Command failed: set -o pipefail; command find -L . -mindepth 1 \( -path
'*/\.*' -o -fstype 'sysfs' -o -fstype 'devfs' -o -fstype 'devtmpfs' -o -fstype
'proc' \) -prune -o -type f -print -o -type l -print 2> /dev/null | cut -b3-]
```
Uninstalling gash-utils removes the problem.
Best,
Blake
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#52372: gash-utils & fzf conflict |
Date: |
Wed, 08 Dec 2021 18:14:12 +0100 |
Blake,
Command failed: […] command find
This isn't ‘really’ a bug: fzf invokes whichever find(1)
executable happens to be in $PATH at run time, and reasonably
expects it to support the POSIX ‘-L’ option.
It also willfully tries to hide any useful error messages:
2> /dev/null
…maybe that's what makes Rust so safe?
gash-utils doesn't implement find -L, so failure is to be
expected. As you discovered the fix is as simple as uninstalling
gash-utils, and possibly using it in a Guix environment if you
really need it.
I don't think installing gash-utils globally into your main
profile is a good idea!
Since find(1) is such a key requirement of fzf, it makes sense to
treat it as a fixed input in this case and keep a reference to
findutils' in a wrapper.
Done in commit 9bac41c2b8e7be5ab713402591ceeb32c635c214.
Thanks!
T G-R
signature.asc
Description: PGP signature
--- End Message ---