Re: qpdf or bashcompinit completion bug

[Vincent Lefevre <vincent@xxxxxxxxxx>]

On 2025-08-19 06:33:53 +0100, Stephane Chazelas wrote:
> 2025-08-18 22:12:46 +0200, Vincent Lefevre:
> [...]
> > I would not expect IFS to have changed to a non-standard value for
> > the completion functions. Or should these functions be written in
> > such a way they should work for any IFS value?
> [...]
> 
> IFS is set by users when they want to split things using $(...)
> or $=var of read.

But this does not seem to affect the completion system. If I change
IFS in my shell and change a completer to output IFS (as hex), then
it is the standard IFS value that is output, not the value I have
set in the shell.

> But here in any case, the output of qpdf --zsh-completion is
> intended to be evaluated as is, not split, with the default
> value of IFS or otherwise, do doing that splitting (leaving
> $(...) unquoted) is wrong.

Yes, quoting is much better. But the result is the same as long as
the eval'ed command does not generate tabs, newlines or significant
sequences of spaces.

-- 
Vincent Lefèvre <vincent@xxxxxxxxxx> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)