GNU bug report logs - #77443
[shepherd] Shell completion does not quote arguments

Previous Next

Package: guix;

Reported by: Tomas Volf <~@wolfsden.cz>

Date: Tue, 1 Apr 2025 22:54:02 UTC

Severity: normal

To reply to this bug, email your comments to 77443 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-guix <at> gnu.org:
bug#77443; Package guix. (Tue, 01 Apr 2025 22:54:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to Tomas Volf <~@wolfsden.cz>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Tue, 01 Apr 2025 22:54:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Tomas Volf <~@wolfsden.cz>
To: bug-guix <at> gnu.org
Subject: [shepherd] Shell completion does not quote arguments
Date: Wed, 02 Apr 2025 00:52:56 +0200

Hello,

given two services named cron-foo-(bar) and cron-foo-(baz), the shell
completion provided by Shepherd does not correctly handle the (
character.

    $ herd status cron-<TAB>             <-- completes into...
    $ herd status cron-foo-(<POINT>      <-- ... this
    $ herd status cron-foo-(<TAB>        <-- but this does nothing

Manually fixing up the ( and trying again:

    $ herd status cron-foo-\(bar<TAB>    <-- completes into...
    $ herd status cron-foo-(bar)         <-- ... this

However the final line, while the service name is correct (from
Shepherd's point of view), is not a valid shell syntax.

I assume some other characters might cause similar problems.

Have a nice day,
Tomas

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
This bug report was last modified 3 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.