Skip to content
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

When updating, list commits which have been pulled in #8

Closed
airblade opened this issue Sep 16, 2016 · 6 comments
Closed

When updating, list commits which have been pulled in #8

airblade opened this issue Sep 16, 2016 · 6 comments

Comments

@airblade
Copy link
Owner

When a plugin is updated, voom prints something like:

vim-fugitive updated: 7 commits

I would like to be able to display what those commits were:

vim-fugitive updated: 7 commits
  * 8a89354 Minor formatting tweaks.
  * 8777d70 Clarify installation instructions.
  * 5c8aa62 Installation directory defaults to ~/.vim.
  * a39deb5 Add vim-plug to list of alternatives.
  * ec5791c Add note about voom edit.
  * 3ba2e3a Fix shellcheck warnings.
  * ead083f Add edit command.

The problem is that each plugin-update runs in a background process, and their output is interleaved.

@Rycieos
Copy link
Contributor

Rycieos commented Sep 16, 2016

The command you are looking for is
git log --oneline master..origin/master
Running that before the pull will give the output you want.

Storing that as a bash string then echoing it might not cause the interleaving?

@airblade
Copy link
Owner Author

airblade commented Sep 16, 2016

That's the command I use currently, although I pipe it into wc -l to summarise the output on 1 line.

I seem to remember I tried storing the output as a string and echoing that, but it still interleaved. It was a while ago now so I could be wrong.

Update: I just tried it again and the output is still interleaved.

@Rycieos
Copy link
Contributor

Rycieos commented Sep 16, 2016

Added a commit that adds this. It uses printf to print the log, so it is not interleaved.

To test this, I ran

for D in ~/.vim/bundle/*/; do
  cd "$D"
  git reset --hard HEAD~3
  cd ..
done

voom update

This produced this output: pastebin.

Note, the svn log output has to be run through awk to be on one line, and it really sucks. See here. Any ideas to make this cleaner would be great.

If this looks good, I can make a pull request.

@Rycieos
Copy link
Contributor

Rycieos commented Dec 12, 2016

And if you do an update with subversion instead, it looks like this:

$ voom update
updated DidYouMean: 1 commit(s)
r16 Allow filenames containing spaces

updated supertab: 1 commit(s)
r172 fix SuperTabLongestHighlight to only move the cursor when the completion popup is visible

updated nerdcommenter: 5 commit(s)
r455 Add ansible file type (#276)
r454 Remove trailing whitespace for top and bottom line (#269)
r453 Add support for molpro and vasp chemistry packages
r452 add support for M4 macro processor (#271)
r451 Add alternate delimiters for autohotkey (matching ahk)

updated targets.vim: 2 commit(s)
r541 Merge pull request #165 from wellle/vim-plug
r540 Add install instructions for vim-plug

updated splitjoin.vim: 8 commit(s)
r534 Handlebars block components
r533 Handlebars component setting -- bracket on same line
r532 Demo gif
r531 Fix for case statement alignment
r530 Remove "examples" directory
r529 Merge pull request #93 from mutewinter/jsx
r528 refactor: remove need for update to JS
r527 add JSX support

@Rycieos
Copy link
Contributor

Rycieos commented Feb 17, 2017

I have since gotten git on all of my work environments, which means that SVN support is no longer important to me. Since I had to hack voom a ton to get svn to work, I decided to go back and try and solve this issue again, without the clutter of the SVN code in the way. Turns out it was really simple. I will open a pull request with my changes.

My other pull request for SVN support I am no longer supporting. I will leave it open in case there is interest, but I don't care for that feature anymore.

@airblade
Copy link
Owner Author

Closed by 0e08f8c. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants