unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Blake Shaw <blake@nonconstructivism.com>, 52372@debbugs.gnu.org
Subject: bug#52372: gash-utils & fzf conflict
Date: Wed, 08 Dec 2021 17:30:59 +0000	[thread overview]
Message-ID: <c76376eb11dbe81a7ff0f1dc970e56599d3a21a6.camel@telenet.be> (raw)
In-Reply-To: <87czm7cpd3.fsf@nonconstructivism.com>

Blake Shaw via Bug reports for GNU Guix schreef op wo 08-12-2021 om
18:23 [+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.

Seems like 'coreutils' (or 'coreutils-minimal'?) should be added to the
wrap-program & inputs in the package definition of 'fzf' (untested),
and bin/fzf should be wrapped as well.

Or maybe it's not the fzf that is problematic, but the bash
completions.

Greetings,
Maxime.





      parent reply	other threads:[~2021-12-08 17:32 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
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 [this message]

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=c76376eb11dbe81a7ff0f1dc970e56599d3a21a6.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=52372@debbugs.gnu.org \
    --cc=blake@nonconstructivism.com \
    /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).