From: Einar Largenius <einar.largenius@gmail.com>
To: Hilton Chain <hako@ultrarare.space>
Cc: Tobias Geerinckx-Rice <me@tobias.gr>,
73142@debbugs.gnu.org, Nils Landt <nils@landt.email>,
help-guix@gnu.org, elaexuotee@wilsonb.com
Subject: bug#73142: [PATCH] gnu: libsixel: Fix bash completion.
Date: Mon, 09 Dec 2024 10:20:26 +0100 [thread overview]
Message-ID: <87ikrtfc11.fsf@gmail.com> (raw)
Message-ID: <20241209092026.BelpJBZm8LAyu7pDgBp_7y1CGo-UbAPSbwN3Ccc6nyI@z> (raw)
In-Reply-To: <87h67g59np.wl-hako@ultrarare.space> (Hilton Chain's message of "Sat, 07 Dec 2024 13:44:58 +0800")
Hi,
It turned out I sourced my completion incorrectly. When I changed my setup as per Nilss suggestion the issue stopped. I assume by sourcing it this way this issue is already taken into account and resolved elsewhere.
lördag den 07 december 2024 skrev Hilton Chain:
> * gnu/packages/image.scm (libsixel)[source]: Fix bash completion.
>
> Fixes: https://issues.guix.gnu.org/73142
> Reported-By: elaexuotee@wilsonb.com
> Fixes: https://mail.gnu.org/archive/html/help-guix/2024-12/msg00029.html
> Reported-by: Einar Largenius <einar.largenius@gmail.com>
> Change-Id: I7e30bfa4ad6efcf27b2e89a42c34802b53bd30e0
> ---
>
> Does this patch fix the issue?
--
Med vänliga hälsningar Einar
next prev parent reply other threads:[~2024-12-11 7:29 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
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 [this message]
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=87ikrtfc11.fsf@gmail.com \
--to=einar.largenius@gmail.com \
--cc=73142@debbugs.gnu.org \
--cc=elaexuotee@wilsonb.com \
--cc=hako@ultrarare.space \
--cc=help-guix@gnu.org \
--cc=me@tobias.gr \
--cc=nils@landt.email \
/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).