[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Custom word completion, word splitting, bad behavior
From: |
Nick Patavalis |
Subject: |
Re: Custom word completion, word splitting, bad behavior |
Date: |
Tue, 13 Feb 2018 08:55:01 +0200 |
On Mon, Feb 12, 2018 at 6:33 PM, Chet Ramey <chet.ramey@case.edu> wrote:
>
> Because, as I said in my original reply, readline understands how to
> complete inside quoted strings. If point is after the `b', for instance,
> and you hit TAB, readline scans back to the open quote and passes
> "p/foo/a b" to the completion function.
>
I see...
Still the *line* is split correctly into two words (ls | tm"p/foo a
b") regardless of the presence of '"' in COMP_WORDBREAKS. Then
readline decides to complete the second word (tm"p/foo/ a b) in this
manner (ignoring the part before the quotes). So this is not really
pertinent to our original discussion...
/npat
- Custom word completion, word splitting, bad behavior, Nick Patavalis, 2018/02/05
- Re: Custom word completion, word splitting, bad behavior, Chet Ramey, 2018/02/05
- Re: Custom word completion, word splitting, bad behavior, Nick Patavalis, 2018/02/06
- Re: Custom word completion, word splitting, bad behavior, Chet Ramey, 2018/02/07
- Re: Custom word completion, word splitting, bad behavior, Nick Patavalis, 2018/02/07
- Re: Custom word completion, word splitting, bad behavior, Chet Ramey, 2018/02/14
- Re: Custom word completion, word splitting, bad behavior, Chet Ramey, 2018/02/07
- Re: Custom word completion, word splitting, bad behavior, Nick Patavalis, 2018/02/07
- Re: Custom word completion, word splitting, bad behavior, Chet Ramey, 2018/02/12
- Re: Custom word completion, word splitting, bad behavior,
Nick Patavalis <=