I just started using emacs to do all of my C++ and python coding in (thank you python mode!) and so far it's been "ok." The only thing that I find a inconvenient is that emacs doesn't have tabs to click on when you want to switch buffers, and because of that, I constantly have to look at the buffer list in order to find out what buffer I want to go to. Anyways, that's my 2 cents. Hopefully emacs will be faster to code in once I get more experienced with using it.

XEmacs has tabs.

Quote:

XEmacs has tabs.

Really? I didn't know that. Oh well, all I really need is just to enlarge my XEmacs window and keep the buffer list on the bottom so I remember what the names are. I'm starting to like this no-mouse interface :)
p.s. You wouldn't happen to know how to disable the toolbar in XEmacs, do you? I tried putting a "(set-specifier default-toolbar-visible-p nil)" in .emacs, but it gives me an error message saying:
Symbol's function definition is void: set-specifier

pico is just fine for me

Maybe don't vim, but emacs is a IDE. Ed is a text-editor, not emacs.

what's the definition of an IDE? i use vim as an IDE. the only thing that lacks is the support of a debugger, although AFAIK gvim has a compile-time feature of setting breakpoints with mouse clicks. I saw this working with a SUN IDE some years ago, but i don't remember the name... Apart from that i miss only auto completion, but i don't miss it much.

but the coolest feature is (IMHO) that you can use those thousands of vim-features without using the mouse ever. That way your hands stay on the keyboard, and if you are able to type fast you'll always be faster then if you switch from keyboard to mouse, make some clicks, then switch back to the keyboard etc. It's faster, and better for your forearms.

i used to be really comfortable with windows and MS Visual Studio, and i was quite fast, i think. But then at work i was "forced" to write software on a old SUN Sparc computer; a coworker showed me vi and emacs, and i chose vi, for no obvious reasons... i needed about two months, then i was A LOT faster using vi and i didn't want to use Developer Studio anymore (that was the time when i decided to uninstall Windows and switch to Linux on my PC at home)...

Quote:

Original post by crupp but the coolest feature is (IMHO) that you can use those thousands of vim-features without using the mouse ever. That way your hands stay on the keyboard, and if you are able to type fast you'll always be faster then if you switch from keyboard to mouse, make some clicks, then switch back to the keyboard etc. It's faster, and better for your forearms.

However, actually typing code is a very small part of the development process. Debugging, refactoring, navigating the code(which vi is really bad at) takes up way more time.

In my case, now that our Java app is done and debugging is what we do, I use Netbeans debug mode, and don't bother editing files with vim .. that really feels odd to me, but it is faster not using vim when it comes to debuging Java code.

BTW for those interested auto-complete in vim is used by pressing Ctrl-n or Ctrl-p while in insert mode, also dont forget to create a tag file for your source code (:help tag & man ctag), and setting your path in vim (:set path=/home/user_x/src/**) then :find ClassName.java can be very handy as a search command.

Quote:

Original post by bytecoder I just started using emacs to do all of my C++ and python coding in (thank you python mode!) and so far it's been "ok." The only thing that I find a inconvenient is that emacs doesn't have tabs to click on when you want to switch buffers, and because of that, I constantly have to look at the buffer list in order to find out what buffer I want to go to. Anyways, that's my 2 cents. Hopefully emacs will be faster to code in once I get more experienced with using it.

There are a million emacs scripts that allow you to flip buffers with one key-binding. They're really convenient and useful. Search for bubble buffers or something like that.

Quote:

... navigating the code(which vi is really bad at) ...

Yes and no.

vi(m) is actually the best I've found for editing in a small area.. it is extremely fast (and easy!) to move to a particular part of a line for instance via many different ways.

However, vi(m) is like most code editors when it comes to large scale navigation being limited to moving to tags by and large. Which is severely lacking in comparison to some methods. Well, there is `gd` and such like but they tend to be hit or miss for how I do things I've found.

This said I normally have ms.net, filemanager and vim open.. I compile in ms.net depending on the scale of the error I either fix it in ms.net or open the file in vim. For normal coding I open files in vim via the filemanager (servant salamander allows you to specify an external editor so it is a simple <f4>) So hum.. Have I switched to an IDE? I don't think so. This is how I've always done my windows coding.. When I started I used Multi-Edit, then Visual Slick Edit and now VIM. ms.net's editor is vastly superior to vc5's but it is lacking considerably for things I do a lot so I use something else, namely vim. So I think you can say my OS is my IDE, which sounds about like it should be and has been.

So to answer the original question, no I’ve not been tempted to switch to an IDE .. I do change components at times though ;)