unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Blake Shaw <blake@nonconstructivism.com>
Cc: bug-guix@gnu.org, 52372-done@debbugs.gnu.org
Subject: bug#52372: gash-utils & fzf conflict
Date: Wed, 08 Dec 2021 18:14:12 +0100	[thread overview]
Message-ID: <87k0gfuhke.fsf@nckx> (raw)
In-Reply-To: <87czm7cpd3.fsf@nonconstructivism.com>

[-- Attachment #1: Type: text/plain, Size: 893 bytes --]

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2021-12-08 17:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08 11:23 bug#52372: gash-utils & fzf conflict Blake Shaw via Bug reports for GNU Guix
2021-12-08 17:14 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2021-12-09  5:29   ` Blake Shaw via Bug reports for GNU Guix
2021-12-11 16:12   ` Timothy Sample
2021-12-08 17:30 ` Maxime Devos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k0gfuhke.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=52372-done@debbugs.gnu.org \
    --cc=blake@nonconstructivism.com \
    --cc=me@tobias.gr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).