Hello namsh, > Personally I cannot live without 'git add -p'. > And I want to say vimagit is a great plugin for this workflow. > Thanks for your powerful plugin.
Great to hear that! > But, it is too slow for me. There is some improvements to do around that. I have some on going branches about performances, but some of them introduce some tedious and error prone logics that ask some work. Anyway, you may want to try the branch next to test a first performance improvement feature. > But, ':Magit' took 5 seconds to show the status. > CR on Makefile took 5 seconds. > 'S' on Makefile took 5 seconds..... For your specific problem, may I ask you to report it on github? It will be easier to me to track him for next release. One question anyway: do you have untracked files or stashes in your repository? If so, could you try the branch next to check that it solves your performance issue? > I run several time, so the timing is not for cold start. > For me, this plugin needs at least 5 seconds to do something. > If this is not expected, should I check something? vimagit display logic is really simple today. It will cache in internal vim variables the whole diffs in your repository, including untracked files; for example, if your repository has a build directory which is not ignored, vimagit will cache diff for each files in your build directory, which may take a long time. In branch next, it won't cache diffs for "closed" file/dir (which is the default when you open the vimagit buffer). Thank you for your report, it will help to improve vimagit. Jérôme -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
