| To: | Nathan Scott <nscott@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] Fwd: PCP metrics auto-completion in the command line |
| From: | Roman Revyakin <rrevyakin@xxxxxxxxxx> |
| Date: | Tue, 12 May 2009 10:42:51 +1000 |
| Cc: | kenj@xxxxxxxxxxxxxxxx, pcp@xxxxxxxxxxx |
| In-reply-to: | <663113014.4742211242024212224.JavaMail.root@xxxxxxxxxxxxxxxxxx> |
| Organization: | Aconex |
| References: | <374355103.4742181242024085099.JavaMail.root@xxxxxxxxxxxxxxxxxx> <663113014.4742211242024212224.JavaMail.root@xxxxxxxxxxxxxxxxxx> |
On Mon, 11 May 2009 16:43:32 +1000 (EST) Nathan Scott <nscott@xxxxxxxxxx> wrote: > > ----- "Ken McDonell" <kenj@xxxxxxxxxxxxxxxx> wrote: > > > Its running pminfo internally ... > COMPREPLY=(`compgen -W '$(command pminfo)' $cur`) > > ... maybe Roman can explain how that bit works. compgen is > a bash builtin: > Yes, it generates the completion list out of the output it receives from the pminfo command. > > Not sure what -W does. > Generate completions out of the given wordlist. > > And with -h and/or -a, hard to see how this is going to work without > > surprises. > > Those are explicitly excluded via the regexs (i.e. if those were the > last part of the command line before attempting expansion, then no > expansion is attempted, I think). > Yes, exactly. Heavy Bash syntax :-) Roman |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | pcp updates (2.8.3), Nathan Scott |
|---|---|
| Next by Date: | Re: [pcp] pcp updates (2.8.3), Mark Goodwin |
| Previous by Thread: | Re: [pcp] Fwd: PCP metrics auto-completion in the command line, Ken McDonell |
| Next by Thread: | pcp updates (2.8.3), Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |