mirrored from git://git.code.sf.net/p/zsh/code
-
Notifications
You must be signed in to change notification settings - Fork 441
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
yum completion #10
Closed
Closed
yum completion #10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
add history and first command after history. Taken from the man page of yum 3.2.29
expand further arguments of 'yum history'
add completion for 'yum help'
adding the following yum commands:
Please send this to zsh-workers@zsh.org; the zsh project doesn't use
github. Thanks!
P.S. The first hunk of your patch has an indentation error (four spaces
instead of two tabs).
|
okay. As a patch file attached to the email? Looking back at the master I see the formatting is before my patch mixed (spaces vs tabs) already. What's the desired indentation style? |
okay. As a patch file attached to the email?
Yes, attachments are fine.
Looking back at the master I see the formatting is before my patch mixed (spaces vs tabs) already. What's the desired indentation style?
Whatever is consistent with the rest of the file. I only noticed this
because the patch added a line using spaces inside a block ($_yum_cmds)
that uses tabs, so the diff looked funny.
Thanks!
|
Conflicts: Completion/Redhat/Command/_yum
closed by 2ba985f |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
adding the following yum commands:
update-to
(just whatupdate
expands)upgrade-to
(just whatupdate
expands)history
(the actual tricky one)help
(printing the available commands)load-transaction
(_files
)load-ts
(_files
)check
(just what the man page suggested)reinstall
(just whaterase
does - suggest installed packages)downgrade
(just whaterase
does - suggest installed packages)repolist
(just what the man page suggested)distribution-synchronization
(just whaterase
does - suggest installed packages)distro-sync
(just whaterase
does - suggest installed packages)history
still needs work. For some of the commands one should supply a transaction id (i.e. just a number from 1 toyum history stats | grep Transactions | sed "s/.*: //"
orlast
orall
) or a range (e.g.5..23
). At the moment I just haveall
last
as well as transaction IDs 1-3 hard coded for testing.Also, I didn't implement all
history
commands - I left out those where I couldn't easily test if I would suggest a valid command, such as inyum history rollback
.