What IDEs are you using to develop git?

Hi there,

I am interested in helping out and improving git, though I haven't programmed in C for quite a while now and thus have to relearn quite some things. I understand the different branches (master, next, pu) and so on, and were successful in compiling git with my Ubuntu 9.04. [yeea] ;)

One thing I would like to ask you: what, if any, IDEs are you working with? I tried Anjuta but were unsuccessful in importing the git folder from any branch into Anjuta. Eclipse worked a bit better, though I am still batteling with the debugger a bit.

Any recommendations, manuals or how-to tips are greatly welcome. And one thing: thank you for your effort! Git really caught my attention and I was so much amused by the Google-Techtalk that Linus gave about Git, that it sparked my interest in relearning how to program again ;)

Best regards from lovely Dresden in Germany Frank Münnich

2009/8/25 Frank Münnich <git@frank-muennich.com>:

I think everyone just uses vim/emacs :-)

John

Il giorno mar, 25/08/2009 alle 13.47 +0100, John Tapsell ha scritto:

I can't get how would one take vim or emacs instead of an IDE like Eclipse. That's probably because I'm mainingly a Java developer and i don't know vim/emacs very much.

What are the advantages of developing git with vim/emacs over an IDE?

Cheers, Daniele

On Sun, 30 Aug 2009, Daniele Segato wrote:

I've spent all my career as a professional programmer using vim as my sole source code editor for the last 15 years.

Simplicity.

Nicolas

I can only reply very generally (I don't develop git - I develop php and use git). However, I have tried to use Eclipse on a number of occasions and have always drifted back to Vim. With a bit of learning can can do most of the stuff that an IDE does, usually faster and with less fuss. However, the killer for me is that you can access your development box in an emergency over a slow dialup line and vim will get you out of trouble - your fancy, resource-hogging IDE will not.

2009/8/30 Daniele Segato <daniele.bilug@gmail.com>:

On Sun, Aug 30, 2009 at 9:06 PM, Howard Miller<howard@e-learndesign.co.uk> wrote:

Ditto. And with a very modest screen size. Modern IDEs need a huge monitor, and then more, just to show what they want to show you.

Not what you need.

So when working on webapps, I normally keep my editor (usually an emacs variant) window small, and have lots of terminal windows tracing relevant logs (webserver, db server) and 3~4 webbrowsers logged in as different users.

When working on git itself, it's much easier -- as all you need is your editor and your terminal to compile & debug so for a simple task like git itself, an IDE might even work ;-)

cheers,

m

söndag 30 augusti 2009 20:07:44 skrev Daniele Segato <daniele.bilug@gmail.com>:

Vim and Emacs has, and have had tools suitable for C and other languages for ages. If you have learned to master them it's hard to find anything as good. If you do java the tools in vim and emacs are not as developed as those for older languages, which Eclipse is originally developed as a tool for Java development and it shines at it. For non-java things vary. The C/C++ support in Eclipse is getting better, but it' nowhere near what exists for Java. Learning and avoiding its's bugs and quirks is probably not worth it if you already have other good or better tools.

VIM and Emacs are really IDE's. In particular you can login to emacs directly and never leave it until you log out. Besdides all you pogramming tools you have your email and (yes) your mp3 player there. That's pretty integrated to me.

-- robin

On Sun, Aug 30, 2009 at 11:29 PM, Robin Rosenberg<robin.rosenberg.lists@dewire.com> wrote:

One could argue that some of these features makes them Integrated Dicking-around Environments instead of Integrated Development Environments ;)

Daniele Segato wrote:

Pre-trained fingers in my case. I quite like simple IDE's such as Geany, but I get so annoyed when emacs keybindings don't work, or when the auto- indentation doesn't do what I want it to do that I just revert back to my simple editor instead.

On Sun, Aug 30, 2009 at 11:37 PM, Daniele Segato <daniele.bilug@gmail.com> wrote:

How much mouse do you use and how much keyboard?
And now read http://steve.yegge.googlepages.com/effective-emacs.
Note: vi is ergonomically superior to emacs (shortest keystrokes, no
mouse at all)  but emacs can do more than vi

Frank Münnich wrote:

No IDE. Just jed (a lightweight emacs-ish editor).

I've tried to learn Geany, but my fingers are too trained to the emacs shortcuts and I'm far too used to the behaviour of my current editor to be able to switch without a month or so of idling, and that's not really an option at $dayjob.

On 08/25/2009 03:15 PM, Frank Münnich wrote:

kdevelop rocks. Debugging perfect. Just configure a C external-make project and off you go.

Cheers Boaz

Frank Münnich (git@frank-muennich.com) wrote on Aug 25, 2009:

I'm using Eclipse CDT on Ubuntu. The only thing that has been a pain is the debugging application output console is not a true xterm or console and doesn't show diff output (which is what I've been focused on) properly, so for that Data Display Debugger has been useful.

Frank Münnich <git@frank-muennich.com> writes:

I personally use GNU Emacs when working with git-controlled projects.

See also question 20. What editor, IDE or RAD you use working with Git? in Git User's Survey 2009 (http://git.or.cz/gitwiki/GitSurvey2008)

   Among text editors (although with plugins, addons, modes one can
   make those into something resembling IDE) Vim with 51% wins over
   TextMate with 33%, which in turn wins over Emacs with 21%. Next in
   turn is Eclipse with 13% (assuming that editors in 'other' won't
   change it; this would a bit unlikely, though); it is most popular
   among Java IDE listed (from those NetBeans is more popular than
   IntelliJ IDEA). XCode, MS Visual Studio and KDevelop IDE have
   similar popularity, surpassing Anjuta.

Vim (or gvim if I want better colors), and cscope. Cscope + vim is a killer combination that enables you to fly around projects of any size very efficiently. I swear by it. I use it at my job to navigate a project consisting of over 14000 lines of code. It makes tracing execution and navigating a project child's play.

Hope that helps, Jeremy

On Aug 25, 2009, at 8:15, Frank Münnich <git@frank-muennich.com> wrote: