unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Einar Largenius <einar.largenius@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>, help-guix <help-guix@gnu.org>
Subject: Re: bash: have: command not found
Date: Fri, 06 Dec 2024 22:59:12 +0100	[thread overview]
Message-ID: <87zfl8qxqn.fsf@gmail.com> (raw)
In-Reply-To: <ED3FBAB3-496B-4A24-8409-9FB122FB67DA@tobias.gr> (Tobias Geerinckx-Rice's message of "Fri, 06 Dec 2024 19:17:28 +0000")

fredag den 06 december 2024 skrev Tobias Geerinckx-Rice:

> So yeah, this is the problem. This isn't how completion works. Remove
> it. Install "bash-completion". Be happy.

I have installed that package. Guix doesn't touch my login shell config
(.bashrc) as far as I know, so I needed to add those lines on my own. I
believe guix-home and guix-system adds loading for bash-completion
automatically.

I believe its more likely that a broken package is the culprit. In my
current profile I have 5 completion scripts only img2sixel complains.

> Do you have any idea which package added this (broken) code?

No idea, how can I tell which package adds img2sixel?

> Which distribution are you using?

I am using Fedora 41 as a foreign distro.

-- 
Med vänliga hälsningar Einar


  reply	other threads:[~2024-12-06 21:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06 14:14 bash: have: command not found Einar Largenius
2024-12-06 19:17 ` Tobias Geerinckx-Rice
2024-12-06 21:59   ` Einar Largenius [this message]
2024-12-06 22:58     ` Tobias Geerinckx-Rice
2024-12-09  9:16       ` Einar Largenius
2024-12-07  4:01 ` Nils Landt
2024-12-07  5:44   ` [PATCH] gnu: libsixel: Fix bash completion Hilton Chain
2024-12-09  9:20     ` Einar Largenius
2024-12-09  9:20       ` bug#73142: " Einar Largenius

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=87zfl8qxqn.fsf@gmail.com \
    --to=einar.largenius@gmail.com \
    --cc=help-guix@gnu.org \
    --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.
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).