Hello
Just had a case where my GeanyVC plugin locked up the CPU when selecting the 'Commit' menu option.
I had to manually commit the changes from the command line: "git commit -a"
If this happens again what should I do next time? Is there some debug setting I should use? Or are we looking to move to the new git browser plugin being developed? Does that have add and commit functionality?
Cheers Murray
On 3 July 2011 13:01, Murray Collingwood murray@focus-computing.com.au wrote:
Hello
Just had a case where my GeanyVC plugin locked up the CPU when selecting the 'Commit' menu option.
I had to manually commit the changes from the command line: "git commit -a"
If this happens again what should I do next time? Is there some debug setting I should use? Or are we looking to move to the new git browser plugin being developed? Does that have add and commit functionality?
First you should post more information, OS, geany --version, plugin version, git version etc.
Details of what you were doing, eg local remote repos, which sorts of file systems, transfer protocols?
What do you mean by "locked up"? 100% cpu, crashed the OS? did you try more than once? was it Geany or git, did git even get run at all?
Yes, you can run with gdb, see the hacking file for details.
Without putting words in the respective developers mouths, I understand that Gitbrowser and GeanyVc are complementary, not replacements.
Cheers Lex
On Sun, 3 Jul 2011 14:34:34 +1000 Lex Trotman elextr@gmail.com wrote:
Without putting words in the respective developers mouths, I understand that Gitbrowser and GeanyVc are complementary, not replacements.
Thhis is my understanding too, based on the feature goals of gitbrowser I guess. And I really think they are fitting well together ;)
Cheers, Frank
On Sun, Jul 3, 2011 at 9:47 PM, Frank Lanitz frank@frank.uvena.de wrote:
On Sun, 3 Jul 2011 14:34:34 +1000 Lex Trotman elextr@gmail.com wrote:
Without putting words in the respective developers mouths, I understand that Gitbrowser and GeanyVc are complementary, not replacements.
Thhis is my understanding too, based on the feature goals of gitbrowser I guess. And I really think they are fitting well together ;)
Thanks! :) And yes, I would certainly agree, gitbrowser has no "active" Git operations supported. All it does is make the set of files tracked by Git navigable in Geany, and provide a (quite polished, imnsho) quick-open dialog for rapidly opening documents belonging to a repository. I do all my Git interaction the command-line way, since I'm still very much a newbie with Git and want to learn.
/Emil - gitbrowser author
Am 04.07.2011 09:09, schrieb Emil Brink:
I do all my Git interaction the command-line way, since I'm still very much a newbie with Git and want to learn.
It depends. I'm doing a couple of things using a GUI like gitg, as it makes it easier in some cases. But even the better UI doesn't support all features the CLI do offer ;) In past I also tried giggle as well as gitk/git ui but wasn't this satisfied with, even they have some real nice features too.
Cheers, Frank
On Sun, 3 Jul 2011 13:01:53 +1000 Murray Collingwood murray@focus-computing.com.au wrote:
Hello
Just had a case where my GeanyVC plugin locked up the CPU when selecting the 'Commit' menu option.
I had to manually commit the changes from the command line: "git commit -a"
If this happens again what should I do next time? Is there some debug setting I should use? Or are we looking to move to the new git browser plugin being developed? Does that have add and commit functionality?
Did you had a lot of changes inside your git repository? This usaly happens in such cases and is caused by the way how the information about changes are cought and printed into commit dialog.
Cheers, Frank
Hi Lex, Frank
Sorry guys, I just assume everybody is using Debian Squeeze like me, and of course the slightly aged Geany 0.19.1 (why am I still using this old version...) with GeanyVC 0.19. I'm using it because there were binaries available and generally I'm finding the binaries of any package I download constitute the most stable version available. (That's an interesting discussion for another time possibly).
I use Propel with my PHP development and consequently there is a script that generates and occasionally updates class files. It's fairly intelligent and only updates files necessary (not simply overwriting everything). Anyways, after making some changes to my database schema the Propel script was run that updated about 100 class files (ie these files were not modified within Geany). There were about 6-8 files updated using Geany.
I then opened one of the files modified within Geany and right-mouse on the file pane to bring up the context menu and select the 'VC commit' option. At this point Geany stopped responding and the CPU (well one of them anyways) was at 100%.
I tried this twice with the same result.
I tried a 'git status' at the console and it worked fine, however it did show a largish number (100 or so) files that had been modified along with a few new files that were not yet in the repository control.
I was able to open a number of new files that had been created and selected the 'VC file actions' -> 'Add to version control' and this function worked fine. After adding these files I tried the 'VC commit' again and it hung again.
I finally ended up running at the console 'git commit -a' and this worked okay.
Frank, you suggested that there might be a problem with changes to a large number of files as I had, and probably exasperated by the version I'm running. Will the latest version make any difference to this? Or do I simply resort to the command line when this happens again?
Lex, in light of the above do you think there is still any value in running the dbg and providing results from this?
Thanks for your responses. Cheers Murray
On 3 July 2011 16:39, Frank Lanitz frank@frank.uvena.de wrote:
On Sun, 3 Jul 2011 13:01:53 +1000 Murray Collingwood murray@focus-computing.com.au wrote:
Hello
Just had a case where my GeanyVC plugin locked up the CPU when selecting
the
'Commit' menu option.
I had to manually commit the changes from the command line: "git commit
-a"
If this happens again what should I do next time? Is there some debug setting I should use? Or are we looking to move to the new git browser plugin being developed? Does that have add and commit functionality?
Did you had a lot of changes inside your git repository? This usaly happens in such cases and is caused by the way how the information about changes are cought and printed into commit dialog.
Cheers, Frank -- Frank Lanitz frank@frank.uvena.de
Geany mailing list Geany@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany
On Sun, 3 Jul 2011 21:35:42 +1000 Lex Trotman elextr@gmail.com wrote:
Lex, in light of the above do you think there is still any value in running the dbg and providing results from this?
If Frank thinks its a known bug then probably not worth it unless he asks you to.
I agree. Of course if you like to have a look into it and maybe provide a fix, this would be cool. However, most likely its 'hanging' on adding the changes to the tree showing them inside the commit dialog.. 'hanging' because Geany will come back... maybe within 30min or something. BUT: If you like to run Geany within gdb and verify whether this is really the cause, this might could help also a bit to double check its no other issue.
Cheers, Frank
On Sun, 3 Jul 2011 20:57:13 +1000 Murray Collingwood murray@focus-computing.com.au wrote:
Frank, you suggested that there might be a problem with changes to a large number of files as I had, and probably exasperated by the version I'm running. Will the latest version make any difference to this? Or do I simply resort to the command line when this happens again?
Its a general issue with the plugin, which needs to be addressed. I can only suggest to use in such cases the command line git interface.
As I mentioned before, its caused by the general design how geanyVC is adding the changes into commit dialog which is rather intelligent for huge changesets :(
Cheers, Frank