Earlier quoted context omitted.
Interesting. For what it's worth, I plan to give Emacs another go pretty soon here, but I'll be sticking with Common Lisp. I'm kind of done my courting period with Clojure.
Emacs + Slime for CL should be a piece of cake as long as you don't insist on using your distribution's packages. Mail me (see profile) when you run into any problems and I'll help you out.
Let's just use Emacs
131–140 of 169 posts
Re: Let's just use Emacs
#132A few years ago I switched to emacs because I needed a cross-platform editor that worked with multiple languages and was available on command-line Linux. vi(m) was (and is) unintuitive. As you work with emacs and customize it to work with your flow, your hands, and your keyboard, it starts to feel as comfortable as old shoes. Over time, the incremental efficiencies add up, and it becomes clear that a non-customizable…
I started using vim, and at first, it was kind of hard to get used to all the commands and remember everything... but after a while (1~2 weeks) it felt so fluid and easy – everything makes kind of sense, it's easy to install new plugins (pathogen ftw!), it's easy to hack those plugins, themes (most of the time) just works.
Re: Let's just use Emacs
#133Earlier quoted context omitted.
I'm not trying to be snarky here, but if you change the font and turn the toolbar off what's left of the design?
If only you could configure Eclipse until nothing was left of its design!
Most of the clutter is gone, but all of the nice IDE features (refactoring, immediate error detection, etc.) are still there. It's a nice way to work.
Re: Let's just use Emacs
#134Earlier quoted context omitted.
I work on a 5GB source tree at work with a couple (or more? I haven't looked) thousand Java source files. After my last machine decided it would be a good time to crap out and I started over with a new OS X install, I tried working strictly with vim and emacs and our scripts (written by vim aficionados, it seems) to navigate around the codebase. It was like a root canal. If I was on fire. Seriously--I'm not an Eclips…
Don't use ctags, they're garbage. --- Emacs user that uses a lot of "IDE esque" features
I used to use pymacs and ropemacs with python, but it broke in hard to determine ways, and then on my latest project it was horribly slow, so I stopped.
I still live in emacs
Re: Let's just use Emacs
#135Earlier quoted context omitted.
Please do. Bonus points if you include something about Vimpulse ( http://www.emacswiki.org/cgi-bin/wiki/vimpulse.el ) to entice vim users to give it a try.
Cool, I haven't tried that library. I use the built-in vi-mode which does basic stuff. Please check back with http://jlongster.com/ in a few months, I have plans to start doing this kind of stuff there.
Re: Let's just use Emacs
#136Earlier quoted context omitted.
For what it's worth, I read derision in your original post as well.
Sometimes, a really simple statement is a Tabula Rasa. We read into it what we believe, or what we think others might believe. Nothing exceptionally wrong with that, and so we ask the author: "Did you mean such-and-such?" If they didn't, they clarify their intent and we move along. I have spent more time thinking about the nature of programming languages than editors, so I will perhaps ruin a perfectly good neutral s…
> I don't think it's a coïncidence.
This invites the reader to ask "Well, then what's the reason?" And you as the author haven't stated what you think is the answer, which makes the careless reader (in my defense, it's a single post!) bring up a cached thought for the answer. In my case, I see passive arguments all the time that use the same style you tried to use neutrally, where the arguers try to lead the reader to conclude the other side is brain damaged without specifically saying so.
Anyway, interesting case on miscommunication and careless reading. :)
Re: Let's just use Emacs
#137You think 20 years from now people will still be voting up articles about Emacs and Vim? just curious
We had a programming intern a couple years ago, he was doing some Python stuff for us. One day he comes to me all excited about this awesome editor he found that was x-platform and had syntax highlighting for everything and was scriptable. I like editors so I asked him what it was..."It's called Vim!". The editor I had been using for years. :)
Re: Let's just use Emacs
#138Earlier quoted context omitted.
Sometimes, a really simple statement is a Tabula Rasa. We read into it what we believe, or what we think others might believe. Nothing exceptionally wrong with that, and so we ask the author: "Did you mean such-and-such?" If they didn't, they clarify their intent and we move along. I have spent more time thinking about the nature of programming languages than editors, so I will perhaps ruin a perfectly good neutral s…
I'll add myself as another data point to sensing a hidden criticism/accusation of brain damage in your original post. Particularly, I think the main problem is this: > I don't think it's a coïncidence. This invites the reader to ask "Well, then what's the reason?" And you as the author haven't stated what you think is the answer, which makes the careless reader (in my defense, it's a single post!) bring up a cached t…
Re: Let's just use Emacs
#139Articles about why anything you can do in a "simpler" text editor can and should be done in emacs strongly resemble articles about why anything you can do in a less powerful programming language can and should be done in Lisp. I don't think it's a coïncidence.
Simple text editor = simple + powerful Emacs = complex + powerful Lisp = simple + powerful Blub = complex + powerful Given this your association doesn't make much sense. I think most people prefer simple + powerful. And this isn't black and white - Blub can often be simpler for X simple task. However the real yard stick is whether as your problem domain gets more complex does Blub suddenly lose its veneer of simplici…
Emacs seems quite simple to me, actually. Intimidating at first, sure. Complex to master, but simple to use.
Then again, there's an obvious difference between something that is difficult to learn and something that is difficult to use. In fact most tools require training at first to use them, and Emacs is not any different.
Re: Let's just use Emacs
#140Earlier quoted context omitted.
Continued: If you are not serious about editing text, then you will be served by many other editors.
Downvoting without explanation? Fine, I love my competitors using lesser tools.
* Being needlessly argumentative
* Borderline trolling. You _know_ how these arguments go.
* Fallaciously arguing that tools cannot be compared based on how well they get the job done
(IDEs vs 'editors') rather than their implementation
* Getting pissy about downvotes and posting multiple times instead of editing
You've been here a year. You should know better.