[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] fix COMP_WORDS when completing an empty word
|
From: |
Lawrence Velázquez |
|
Subject: |
Re: [PATCH] fix COMP_WORDS when completing an empty word |
|
Date: |
Thu, 30 Jun 2022 13:49:31 -0400 |
|
User-agent: |
Cyrus-JMAP/3.7.0-alpha0-713-g1f035dc716-fm-20220617.001-g1f035dc7 |
On Mon, Jun 20, 2022, at 6:28 AM, n+bash@monade.li wrote:
> From: Naïm Favier <n@monade.li>
>
> Currently, typing `cmd flag1 flag2` (note the two spaces), navigating
> between the two spaces and hitting Tab produces
> `COMP_WORDS=(cmd flag1 flag2)` without inserting an empty word between
> flag1 and flag2.
>
> I believe this comes from considering the cursor ("sentinel") as a block
> rather than a line, which does not make sense in a completion context,
> but might possibly make sense in other contexts?
Looks like this dates to this change, although I'm not completely sure.
https://git.savannah.gnu.org/cgit/bash.git/tree/CWRU/old-changelogs/CWRU.chlog.v12?h=devel#n7702
--
vq