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


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

Re: 'complete' not working as documented

Started byChet Ramey <chet.ramey@case.edu>
First post2018-08-11 11:25 -0400
Last post2018-08-11 11:25 -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: 'complete' not working as documented Chet Ramey <chet.ramey@case.edu> - 2018-08-11 11:25 -0400

#14466 — Re: 'complete' not working as documented

FromChet Ramey <chet.ramey@case.edu>
Date2018-08-11 11:25 -0400
SubjectRe: 'complete' not working as documented
Message-ID<mailman.4991.1534001118.1292.bug-bash@gnu.org>
On 8/11/18 1:14 AM, Hugo Gabriel Eyherabide wrote:

> Bash Version: 4.4
> Patch Level: 18
> Release Status: release
> 
> Description:
> Bash manual says 'complete ... -D ... name' should be correct, whatever
> between -D and name applying to the completion on a command for which
> completion has not been previously defined.

No. In the description, `remaining' means `the options and option arguments
besides -D'.

> and
> 
> $ complete -p aabbname
> 
> shows nothing, indicating that the completion for aabbname has never been
> defined.

Yes. Any additional command name arguments supplied with -D are not used.

-- 
``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