Hi

I'm trying to fix a bug (the erroneous striping of \ escape characters in unit names) in the ARCH-Linux SystemD bash-completion script.

The crucial line is:
Basically I want to write something like:
so I get "protection" for the \ escape character (which starts to get swolled up otherwise!!) but also get expansion for variables $comps and $cur (which the ' quote prevents).

I've tried (a gross hack) creating the string first, then executing it, but =Fail - something like:
$COMPREPLY is just an empty string each time... $command contains the correct characters...

Any BASH experts out there able to help out a noob??

Mr Gates

Im not really sure the extra set of parenthesis is need but here some things you can try aside from that:
try:
Again not sure why you have the extra paranthesis, simply try this:

Aside form that I also don't know what the -- does? or what your code really does, it might help to try and explain it a little more.

@jaybutts

Sorry my bad for not giving enough details!!

The extra bracketing is convert a returned list of SystemD subcommands or Unit names to an array of potential responses! Just to re-iterate it's not my code at all. Like I mentioned it's the ARCH-Linux SystemD bash-completion script. All the script does is to provide command line completion for SystemD commands entered in a BASH shell (i.e. when you pressed the TAB key it tries to match against all valid responses).

With your suggestion (remove extra bracketing) the command-line completion variable $COMPREPLY will contain all the potential responses in a big list (individual entries separated by spaces). So that is not going to work!

The desired behaviour is to return an array containing individual valid responses, e.g.:

The problem I am trying to tackle is that SystemD Unit names have to use a name mangling system. If they contain (normally command-line escaped) things such as brackets, etc then these must be converted to escaped HEX code equivalents. The '-' character is used to represent Linux directory back-slashes ('/') - so must also be mangled.

E.g.:
would specify a mount-point Unit (for any specified filesystem) in the following (real Linux FS hierarchy) mount-point:
(where '\x2d'=HEX character code for '-')

See here for more info on the name mangling used.


I take the input Unit names and use awk mangle it to:
(doubling the number of '\' forward slashes so that the name works on the BASH commandline - since '\' characters must be escaped).

The problem is that the double quote " symbol around variables ${comps} and ${cur} results in them being transformed by the shell with '\\' combinations being replaced by '\'. So I would get back to:
When this is passed as a Unit name to the SystemD systemctl command

E.g.
would fail as an invalid Unit name as the BASH shell interprets the '\x' as an escaped 'x' character.

What I want the commandline completion to do is give:
Any thoughts? Sadly I am a total BASH scripting noob...
Bob

Not sure I understood the details, but it feels like a potential job for eval.