From: Wayne Davison <wayned@users.sourceforge.net>
To: Zsh Workers <zsh-workers@sunsite.dk>
Subject: PATCH: rpm completion
Date: Mon, 27 Aug 2001 12:25:54 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.33L2.0108271159400.10711-100000@phong.blorf.net> (raw)
I noticed a couple problems with the rpm completion. The first one is
that the verify option does not understand the package-specification
options, nor does it complete package filenames with -p. I believe
that the attached patch fixes this properly. (FYI, yes it is legal to
do "rpm -Vf /path/to/file" to verify the package associated with that
file, to do "rpm -Vp some.rpm" to verify the files in the uninstalled
package file against what's installed on the system, and to use
"rpm -Va" to verify all installed packages.)
One other thing I noticed was that "rpm --clean spec" does not complete
filenames in the spec-file position. Not even the man page mentions
that this is legal, but using "rpm -ba --clean spec" is the same as
doing "rpm -ba spec" followed by "rpm --clean spec". I didn't try to
fix this one, since I don't know how to program the new completion
system in any meaningful way yet.
..wayne..
---8<------8<------8<------8<---cut here--->8------>8------>8------>8---
Index: Completion/Redhat/Command/_rpm
--- Completion/Redhat/Command/_rpm 2001/08/15 13:33:52 1.4
+++ Completion/Redhat/Command/_rpm 2001/08/27 19:14:05
@@ -142,9 +142,9 @@
verify)
_arguments -s \
'(-y --verify)-V' '(-V --verify)-y' '(-y -V)--verify' \
- "${commonopts[@]}" "${pathopts[@]}" \
+ "${commonopts[@]}" "${packageopts[@]}" "${pathopts[@]}" \
--no{deps,md5,files} \
- '*:RPM package:->package' && ret=0
+ '*:RPM package:->package_or_file' && ret=0
;;
upgrade)
tmp=( '(--upgrade)-U' '(-U)--upgrade' '(--force)--oldpackage' )
---8<------8<------8<------8<---cut here--->8------>8------>8------>8---
reply other threads:[~2001-08-27 19:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.33L2.0108271159400.10711-100000@phong.blorf.net \
--to=wayned@users.sourceforge.net \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).