Skip to content

Tags: taq/vim-git-branch-info

Tags

0.1.5

Toggle 0.1.5's commit message
Implemented autogroup

0.1.4

Toggle 0.1.4's commit message
Changed version number

0.1.3

Toggle 0.1.3's commit message
Now the version number is ok

0.1.2

Toggle 0.1.2's commit message
Seems that there were a little bug when loading the file from some ot…

…her plugin

0.1.1

Toggle 0.1.1's commit message
Changed the checking about the original branche while saving a file a…

…s a optional - and not default - option

0.1.0

Toggle 0.1.0's commit message
Forgot again to change the version number. Need to deal with rebase t…

…o change the log messages when I do that. :-p

0.0.9

Toggle 0.0.9's commit message
There were a bug when rebasing. On this situation HEAD just have a ha…

…sh and not the information about the branches the plugin looks for. Thanks for Joachim Bargsten for warning me about this.

I made a double check on the HEAD file. If there is not the information the script wants, a message about the condition is returned. If something also "explodes" there, there is a try/catch block.
If detect this rebase/merge/bisect situation, the file will be always saved without the branch verification.

0.0.8

Toggle 0.0.8's commit message
Argh, another bug fixed. When trying to write to a file different fro…

…m the current

one, it was not saved. That happened because I was trying to save the file without
it's name, presuming if we tell to save to another file with :w the name was correct.It was fixed using expand("<afile>"). Btw, there was another bug when trying to save to an existing file and need to use the bang (!) with write. It was fixed checking if a bang command was used and executing the bang version if needed.

0.0.7

Toggle 0.0.7's commit message
Changed the version number

0.0.6

Toggle 0.0.6's commit message
Extra check on permissions of the Git directory