From: Timothy Sample <samplet@ngyro.com>
To: 52372@debbugs.gnu.org
Subject: bug#52372: gash-utils & fzf conflict
Date: Sat, 11 Dec 2021 11:12:32 -0500 [thread overview]
Message-ID: <87r1ajm87j.fsf@ngyro.com> (raw)
In-Reply-To: <87k0gfuhke.fsf@nckx> (Tobias Geerinckx-Rice via Bug reports for's message of "Wed, 08 Dec 2021 18:14:12 +0100")
Hi Blake and Tobias,
Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
writes:
> 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!
Definitely not! Gash-Utils is very much pre-alpha software, and I don’t
really intend for those utilities to be useful beyond bootstrapping
their fully-featured GNU cousins. Ideally there would be a
bootstrapping version of Gash-Utils that installs the utilities, and a
regular version that just has Scheme interfaces. To date, it has felt a
little premature to bother with that.
However, if you find the Scheme interfaces from Gash-Utils useful, I’m
happy to make accommodations. Right now, I think that Guilers either
write their own utilities like ‘find-files’ or they copy them out of
Guix’s ‘(guix build utils)’ module (I tend to do the latter). It would
be nice if Gash-Utils could cover this use case and be a bit like
Python’s ‘shutil’, allowing a smoother transition from shell scripting
skills to Guile scripting skills.
-- Tim
next prev parent reply other threads:[~2021-12-11 16:13 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 [this message]
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=87r1ajm87j.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=52372@debbugs.gnu.org \
/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).