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

Hi Einar,

On 6 December 2024 14:14:54 UTC, Einar Largenius <einar.largenius@gmail.com> wrote:
>    bash: have: command not found

'have' isn't a binary or bash builtin, it's a function defined only when sourcing completion files in the intended manner using the "bash-completion" package.  You'll see that in 'bash -x' output once you fix your configuration.

>It doesn't appear to impact the functionality of the shell.

It just won't define _img2sixel() to provide completions for that command.

>Here is the relevant part of my config:
>
>    # ...
>    for f in "$HOME"/.guix-profile/etc/bash_completion.d/* ; do
>        . "$f"
>    done
>    # ...

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

Do you have any idea which package added this (broken) code?  Which distribution are you using?


Kind regards,

T G-R

Sent on the go.  Excuse or enjoy my brevity.


  reply	other threads:[~2024-12-06 19:18 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 [this message]
2024-12-06 21:59   ` Einar Largenius
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=ED3FBAB3-496B-4A24-8409-9FB122FB67DA@tobias.gr \
    --to=me@tobias.gr \
    --cc=einar.largenius@gmail.com \
    --cc=help-guix@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.
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).