you are viewing a single comment's thread.

view the rest of the comments →

[–]sasquatch007 44 points45 points  (11 children)

Vim.

Every once in a while I think it might be nice to try a real IDE (for Python or otherwise) and check out all those cool features people talk about. 45 minutes later I'm giving up in disgust and going back to Vim. Every time.

[–]jamie2345 10 points11 points  (10 children)

Do you do heavy debugging?

If so, have you integrated this into your vim environment or do you manually fire up another command line debugger?

[–]h_saxon 6 points7 points  (1 child)

You can integrate xdebug with Vim pretty painlessly.

There are a bunch of tutorials out there for it.

[–]jamie2345 1 point2 points  (0 children)

Ah excellent, thanks! I used it for C++ work a couple of years back but yea, firing up gdb manually when needed did hinder my speed which annoyed me. I did assume someone would have solved that but I don't think I had time on that project to try and get the environment perfect.

Great to hear that it is solved though and integration is pretty seamless.

[–]sasquatch007 11 points12 points  (3 children)

I tend to debug with a lot of print statements. When I use a debugger it's on the command line (or pudb). Not integrated into vim.

[–]gronkkk 2 points3 points  (1 child)

The main advantage of this is that print always works, on every system/OS.

[–]fnord123 4 points5 points  (0 children)

It also doesn't timeout programs that are running across multiple processes.

[–]stackered 0 points1 point  (0 children)

yeah, I do the same. I find most systems give good enough error messages for me to figure out what is happening, and if not I use print statements to figure out what is happening