Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: killall completion
- X-seq: zsh-users 14633
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Zsh list <zsh-users@xxxxxxx>
- Subject: Re: killall completion
- Date: Thu, 03 Dec 2009 08:15:40 -0800
- In-reply-to: <4B173208.5060602@xxxxxxxxxxxxx>
- List-help: <mailto:zsh-users-help@zsh.org>
- List-id: Zsh Users List <zsh-users.zsh.org>
- List-post: <mailto:zsh-users@zsh.org>
- Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
- References: <4B14AAA3.3090609@xxxxxxxxxxxxx> <20091201194117.3dc2993b@pws-pc> <4B15BE9F.7020808@xxxxxxxxxxxxx> <091201202341.ZM9955@xxxxxxxxxxxxxxxxxxxxxx> <4B173208.5060602@xxxxxxxxxxxxx>
On Dec 3, 6:35am, sergio wrote:
}
} Bart Schaefer wrote:
}
} > However, it seems that _arguments gets confused when faced with an
} > argument that resembles an option, because although the above does
} > the right thing when asked to complete several process names, and
} > also does the right thing when completing after "killall -s KILL",
} > it fails to complete after "killall -KILL".
} So what your code improves?
It offers both signals and process names when completing after "killall"
with nothing else on the line yet.
} May be the solution is to generate -SIGNALS as options?
You could try it, but I think there might be a problem because, for
example, -ABRT can be (mis)interpreted as -A -B -R -T. This is a case
where the command's syntax conflicts with the standard option/argument
syntax that _arguments is designed to support.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author