Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #14234 > unrolled thread

Re: [PATCH] Add nofirstword completion option

Started byChet Ramey <chet.ramey@case.edu>
First post2018-06-12 14:54 -0400
Last post2018-06-12 14:54 -0400
Articles 1 — 1 participant

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH] Add nofirstword completion option Chet Ramey <chet.ramey@case.edu> - 2018-06-12 14:54 -0400

#14234 — Re: [PATCH] Add nofirstword completion option

FromChet Ramey <chet.ramey@case.edu>
Date2018-06-12 14:54 -0400
SubjectRe: [PATCH] Add nofirstword completion option
Message-ID<mailman.1765.1528829714.1292.bug-bash@gnu.org>

[Multipart message — attachments visible in raw view] — view raw

On 6/12/18 1:28 PM, Luca Boccassi wrote:
> On Fri, 2018-06-08 at 11:03 -0400, Chet Ramey wrote:
>> On 6/8/18 10:40 AM, Luca Boccassi wrote:
>>
>>> Any chance you had a sec to look at the diff? Would love some
>>> feedback!
>>
>> I'm going to try and look at it this weekend. It's been a busy couple
>> of
>> months.
> 
> Hi Chet,
> 
> I've seen that the change is now in the devel branch, thank you so
> much!
> I also like way more the new option name, definitely clearer :-)
> 
> One difference I noticed with the previous version is that when trying
> to complete a command when the line starts with an empty space (eg: to
> avoid the history) the initial word programmable completion doesn't
> happen.
> 
> It seems to hit the following branch:
> 
>        else if (s >= e && n[0] == '\0' && text[0] == '\0' && start > 0)
>          {
>            foundcs = 0; /* empty command name following assignments */
>            in_command_position = was_assignment;
>          }
> 
> Given was_assignment is 0, then the programmable completion is later
> not attempted.
> 
> Since that branch matches an empty command name, should it perhaps call
> the EMPTYCMD completion?

It's not an empty command line, since it starts with point after column 0.
It should perform command completion, though.

Try the attached patch, or wait for the next devel branch push.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

[toc] | [standalone]


Back to top | Article view | gnu.bash.bug


csiph-web