Re: Bug#864493: notmuch: bash completion eats typed option

["Łukasz Stelmach" <l.stelmach@samsung.com>]

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

Control: reassign -1 npm 1.4.21+ds-2

Dear Maintainer of the npm package.

The reassignment of COMP_WORDBREAKS variable in
/etc/bash_completion.d/npm causes serious problems described in this bug.

It was <2017-08-23 śro 11:27>, when Jani Nikula wrote:
> On Wed, Aug 23, 2017 at 11:59 AM, Łukasz Stelmach
> <l.stelmach@samsung.com> wrote:
>> I looked carefuly and I am sure I use only packaged bash-completion
>> configuration. I looked also at other commands which use the
>> --long-option=VALUE pattern (e.g. mkinitrd --with=, nslookup -class=)
>> and completions for them fail the same way, so it seems more like
>> bash-completion issue rather than notmuch one.
>
> mkinitrd --with= and nslookup -class= completions work for me just
> fine. Indeed does not look like a notmuch specific issue to me either.
>
>> Is there a general way to tell the completion engine not to replace
>> anything before (and including) "="?
>
> I thought _init_completion -s parameter would cover it.
>
> What do you have in $COMP_WORDBREAKS?

    $ printf "$COMP_WORDBREAKS" | hexdump -vC
    00000000  20 09 0a 22 27 40 3e 3c  3d 3b 7c 26 28 3a        | .."'@><=;|&(:|
    $ COMP_WORDBREAKS="=${COMP_WORDBREAKS}"

Bingo!

    $ fgrep -r COMP_WORDBREAKS /etc

And the answer is:

    /etc/bash_completion.d/npm:COMP_WORDBREAKS=${COMP_WORDBREAKS/=/}


Thank you very much for your assistance. I am reassigning the bug to the
npm package.
-- 
Łukasz Stelmach
Samsung R&D Institute Poland
Samsung Electronics

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]