Emacs is great but getting it setup just the way you like is tedious. It's not easy to set tabbing to work just the way you want, to get line numbers to be displayed, etc. This is all compounded if you don't have a net connection to download just existing scripts. It is also horridly slow due to all the LISP interpretation.
I do like Emacs, but I tend to use MicroEmacs rather than the real deal. Easier to get that working, runs quicker, uses less memory, etc. (Or at least it
feels like it uses less memory. I haven't actually checked that.)
I should use Emacs more often than I do as it is useful. I just really dislike reconfiguring it or trying to make it do something different. I love the amount of power it provides, but you have to make a lot of room in your head for storing all the information you need to work with it as proficiently as normal IDEs. That can take a lot of time. The future payoff is much better, though.
Quote: "I have watched few episodes. Emacs is a geeky thing for geeks who likes geeky things"
It works directly in a terminal. AkelPad doesn't. Sometimes working in a terminal isn't done because you want to, at which point Emacs becomes infinitely better (as it works). That said, Vi(m) is the usual installation for terminals.
I might be misinterpreting this also, but it does not look like AkelPad runs on anything but Windows. Is there a reason to use AkelPad over Notepad++ then? Both support plug-ins, only run on Windows, and are open source. When you say "smart code highlight," does that mean AkelPad looks through your source code and tries to infer where variables are declared or when macros are evaluated? That's definitely useful, but I personally prefer that to be in an IDE that
actually knows about my project and the macros I pass to the compiler. I don't think AkelPad would be worse if it did that too as long as that could be disabled.
Web -
Tweets
“Typing is no substitution for thinking.”