On Thu, Oct 29, 2009 at 03:41, marc <[email protected]> wrote: > > Core wrote: > >> How does nbgit play nicely with changes that are happening outside its >> control? Basically, what are the workarounds to avoid confusing >> NetBeans or nbgit until features like checkout/push/pull/merge are >> working? For example, what else should I do before or after invoking >> a "custom action" to avoid problems? > > It works fine, but takes ages -- think netbeans scanning hell without > the disk thrashing -- to get itself back in line after doing an external > git commit. (Ininitiate this via /git/status in nb) All you, the > user, wants, is for the little blue icons to disappear.
Somebody requested that a 'Refresh' action was added to the Git menu. It might simplify this use case considerable. And for custom actions a checkbox could be added to automatically refresh after running the external command. See issue 54 to star, comment etc.: - http://code.google.com/p/nbgit/issues/detail?id=54 > This seems like such a simple use case -- like scanning hell! -- that > it's confusing why it needs to do so much work. The current way it is implemented can probably be improved a lot. In the worst case (I didn't actually look into this yet), the plugin can request refreshing of single files, meaning that JGit will do all the initialization diffing the index and throw away most of the work. What we should do of course is to improve the background refreshing task to batch stuff together and reduce the amount of wasted work. -- Jonas Fonseca --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nbgit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nbgit?hl=en -~----------~----~----~----~------~----~------~--~---
