Github messages for voidlinux
 help / color / mirror / Atom feed
From: Jjp137 <Jjp137@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] chocolate-doom's bash completion scripts are man pages instead
Date: Tue, 16 Jan 2024 03:38:35 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48228@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 992 bytes --]

New issue by Jjp137 on void-packages repository

https://github.com/void-linux/void-packages/issues/48228

Description:
### Is this a new report?

Yes

### System Info

Void 6.1.71_1 x86_64 GenuineIntel uptodate FFFFFFFF

### Package(s) Affected

chocolate-doom-3.0.1_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

no

### Expected behaviour

The `/usr/share/bash-completion/completions/chocolate-{doom,heretic,hexen,strife}` files should be Bash completion scripts.

### Actual behaviour

The `/usr/share/bash-completion/completions/chocolate-{doom,heretic,hexen,strife}' files are man pages.

This results in unexpected behavior, such as Chocolate Doom suddenly launching, when trying to tab-complete parameters such as WAD file names.

### Steps to reproduce

1. `xbps-install chocolate-doom`
2. `cat /usr/share/bash-completion/completions/chocolate-{doom,heretic,hexen,strife}`
3. Notice that the output looks similar to man pages.

             reply	other threads:[~2024-01-16  2:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16  2:38 Jjp137 [this message]
2024-01-17  1:26 ` [ISSUE] [CLOSED] " sgn
2024-02-17  3:19 ` Jjp137
2024-02-18  0:53 ` classabbyamp

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48228@inbox.vuxu.org \
    --to=jjp137@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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 NNTP newsgroup(s).