Live data from Hacker News

Emacs setup for Python development

caisah.info

1–10 of 56 posts

Re: Emacs setup for Python development

#3
That's a lot of junk that doesn't have a lot to do with Python.

Take a look here at my dotfiles to see how to use Rope/Ropemode/Ropemacs to get a Python-aware Emacs environment with the goodies that entails:

https://github.com/bitemyapp/dotfiles/

Edit: Try to ignore or not be daunted by the other directories, my Emacs setup is well maintained but very old and has over 400,000 LOC.

Re: Emacs setup for Python development

#4

The author seems to imply that sublime does not qualify as a "serious" editor, and offers a link to quora as explanation, but the article there doesn't address what Sublime is missing at all.

>doesn't address what Sublime is missing at all.

Being a fully programmable work environment.

Edit: I used ST2 for about a month. The Python was neat but it's going to fade away eventually.

Re: Emacs setup for Python development

#5

The author seems to imply that sublime does not qualify as a "serious" editor, and offers a link to quora as explanation, but the article there doesn't address what Sublime is missing at all.

It's hip to hate Sublime because it can't do X that Emacs or Vim can. There's a lot of criticism of ST by people who never actually used it or used it for a couple of minutes. Pathetic really.

Re: Emacs setup for Python development

#6

The author seems to imply that sublime does not qualify as a "serious" editor, and offers a link to quora as explanation, but the article there doesn't address what Sublime is missing at all.

>doesn't address what Sublime is missing at all. Being a fully programmable work environment. Edit: I used ST2 for about a month. The Python was neat but it's going to fade away eventually.

Vim and Emacs have had decades to get to that point. ST is a comparative baby. I'd love to see a modern editor that isn't designed around a terminal join those ranks.

Re: Emacs setup for Python development

#7
post #5

The author seems to imply that sublime does not qualify as a "serious" editor, and offers a link to quora as explanation, but the article there doesn't address what Sublime is missing at all.

It's hip to hate Sublime because it can't do X that Emacs or Vim can. There's a lot of criticism of ST by people who never actually used it or used it for a couple of minutes. Pathetic really.

I haven't seen a lot of hate in that direction. As someone who uses ST almost primarily, my biggest complaint is that it's not open source and free, which is going to stunt it's growth and keep it from being a real competitor with Emacs or Vim.

Re: Emacs setup for Python development

#8

The author seems to imply that sublime does not qualify as a "serious" editor, and offers a link to quora as explanation, but the article there doesn't address what Sublime is missing at all.

I'm impressed with Sublime Text after trying it out with some dedication — it has a lot to offer, and I'd recommend it over Emacs to someone just starting out, unless they think they might want to learn Lisp. But I think the author was right in saying that Emacs is more serious right now, even though I think Sublime Text will get there.

Re: Emacs setup for Python development

#9

Earlier quoted context omitted.

>doesn't address what Sublime is missing at all. Being a fully programmable work environment. Edit: I used ST2 for about a month. The Python was neat but it's going to fade away eventually.

Vim and Emacs have had decades to get to that point. ST is a comparative baby. I'd love to see a modern editor that isn't designed around a terminal join those ranks.

Pretty hard to "get to that point" when your editor isn't programmable.

Which goes back to my original point.

Seen lots of IDEs and editors come and go. Nothing new here, just more polish than the last guy.

Re: Emacs setup for Python development

#10
The Emacs tutorial is a great place to start.

Using Emacs is a bit of a paradigm shift in text editing, so you should expect a bit more work up front for great results later on. Going through the tutorial and learning the basic vocabulary and commands takes care of most of that up-front cost and should not take long. I think it took me less than two weeks of fairly casual use.

Part of the beauty is that most of the things in the blog are not limited to Python. All the general text-editing stuff trivially transfers to other languages you may want to learn. And Emacs supports any language you do want to learn to one extent or the other. For some languages, Emacs is even the only option!

So you should consider going through at least the beginning of all this even if you're not interested in Python per se.

Also, check out some of the Emacs Rocks![1] videos. I keep on recommending them because they are awesome. They really show off why Emacs is truly magical.

[1]: http://emacsrocks.com/

Post reply on HN