Live data from Hacker News

Emacs, naked

bzg.fr

181–190 of 201 posts

Re: Emacs, naked

#181
I have a moderately well written emacs.d, and I'd be happy to see a few use it/learn from it/correct me/give feedback.

Just startup emacs (24+) with the init.el and it will download dependencies from elpa. Will have to restart once afterwards to make the theme right.

Screeshot : http://i.imgur.com/2wmxir5.png Source: https://github.com/jaseemabid/emacs.d

Re: Emacs, naked

#182
post #96

Earlier quoted context omitted.

A transparent background adds too much visual noise in my opinion. The same is true for line numbers.

Line numbers can be handy to locate compiler errors. I removed it once but then it became a lot harder to locate where the program was causing problems or where the compiler errors occurred. I would like to remove them but I guess I am stuck with it ....

You should run the compiler inside Emacs (M-x compile). That way you can easily jump to error locations. (You can also use M-x goto-line to quickly jump to a specific line)

Re: Emacs, naked

#183

Earlier quoted context omitted.

I switch between Vim and Emacs depending on mood. It's a very hard deal: Emacs is a plateform that can do a lot of things besides editing, but it requires a lot of configuration fiddling, and is a bit too slow on the old machine on which I'm using it (must be a single core Pentium with Mandriva 9). Vim has a lot of things right off the box and is fast, but you have to use other programs to have a comfortable environm…

I switched to Emacs after being very impressed with nxml-mode. I found no better xml editor on Linux. Emacs is great if there is a mode that's written for what you're doing--for instance, nxml-mode. I can imagine it's also great for C, for instance, because that mode is old and has seen lots of work. For lisp I'm sure Emacs is peerless. Emacs is not so great if there's not a good mode for you. I grew frustrated tryin…

I feel exactly the same way.

I was hoping I could get a "minimal" setup to edit Python code, and even that was too much to ask for. "Code folding? What's code folding precious? What's code folding?" --Smeagol

Apparently "minimal" doesn't apply to Emacs. Being complex is in its nature. It wants to become everything.

The worst was how every time you open a different file, your `CWD` always changes to that file's location.

Re: Emacs, naked

#184
I hoped the article would be not about look-and-feel, but about building a stripped-down version of Emacs without obsolete parts like TRAMP or LEIM (because there are system-global subsystems for those nowadays), or maybe even trying to tear chunks from MULE.

In a perfectionist "must be a pure gem, no imperfections allowed" sense, ton of seemingly unnecessary libraries is the only thing that actually bothers me about The Editor.

Re: Emacs, naked

#185

Earlier quoted context omitted.

The issue Melpa has is that it builds from HEAD, whereas many package authors treat HEAD as a working state that should not be used directly. Melpa doesn't (or didn't last time I checked) have support for building off tags or non-master branches, which would solve this. And if I remember correctly, when I raised this issue, he disagreed on some philosophical grounds. So it's an inherent problem in Melpa.

On IRC we get a steady stream of confused users (in both the #emacs and #clojure channels) who added melpa because some library recommended it in their readme and they didn't realize it would cause every package they use to also pull from the unstable branch. It is a huge support headache. However, these days I only very rarely find packages that aren't available on Marmalade. When I do, it's usually enough to ask th…

Fair point.

But one of the issues with Marmalade is that anybody can fork your project (patch it or not) and just push it. With MELPA, they try to get the original authors to submit the projects. If you've got patches, they are pretty strict about it and encourage you to get them merged in the package rather than accepting a fork.

Re: Emacs, naked

#186

Earlier quoted context omitted.

> What's wrong with the normal haskell-mode? The indentation doesn't work well. It gets the indentation right maybe 80% of the time, but missing it 20% of the time is a big deal when you have to deal with the "tab-cycle." I spent so much time fiddling with indentation that I turned off auto indentation...and Emacs without mode-based auto indentation is much worse than Vim with manual indentation. I also had problems…

Did you try all three indentation modes? It's a bit unfortunate that there have to be three separate indenters, but most people find that one of them is good enough.

Yep, tried all three, and looked at at least one mode that someone else is developing to see if it had better indentation. I don't remember the names of the three indenters being all that distinguishing, so I had to keep notes in my .emacs just to tell them apart.

One good indenter (maybe with options to select how to style your code) would be better than three. I remember reading a blog post about how hard it is to indent Haskell automatically. It breaks my chain of thought though to have something automatic that works only most of the time. It means I routinely have to stop to fiddle with the editor to make it indent correctly.

Re: Emacs, naked

#187

Earlier quoted context omitted.

I wonder what the fad-editor in LightTable's place will be called in a few years?

That's pretty uncharitable to LightTable which is doing a number of things differently. Inline evaluation, and great support for ClojureScript with a connected repl to name a few.

Ok, what would be the next fad Javascript wrapper be called in a few years? (does anyone remember CoffeeScript?)

Re: Emacs, naked

#189
post #182

Earlier quoted context omitted.

Line numbers can be handy to locate compiler errors. I removed it once but then it became a lot harder to locate where the program was causing problems or where the compiler errors occurred. I would like to remove them but I guess I am stuck with it ....

You should run the compiler inside Emacs (M-x compile). That way you can easily jump to error locations. (You can also use M-x goto-line to quickly jump to a specific line)

Serious question, are Emacs users seriously in the habbit of typing things like M-x some-long-command-with-minuses? In Vim to go to a line number it's just colon line number, e.g. ":34" goes to line 34. I mean that's the default, not something that's been keymapped. Or do you guys end up keymapping things like that frequently aswell? Then again you guys don't have modal editing so I can see why it's always M-x before doing something non-edity, so it might seem assbackwards for a Vim user :)

I take for instance the most common commands I use in Vim to edit with that I use 95% of the day and they're rarely more than a single character or 3 at the most.

Re: Emacs, naked

#190
post #183

Earlier quoted context omitted.

I switched to Emacs after being very impressed with nxml-mode. I found no better xml editor on Linux. Emacs is great if there is a mode that's written for what you're doing--for instance, nxml-mode. I can imagine it's also great for C, for instance, because that mode is old and has seen lots of work. For lisp I'm sure Emacs is peerless. Emacs is not so great if there's not a good mode for you. I grew frustrated tryin…

I feel exactly the same way. I was hoping I could get a "minimal" setup to edit Python code, and even that was too much to ask for. "Code folding? What's code folding precious? What's code folding?" --Smeagol Apparently "minimal" doesn't apply to Emacs. Being complex is in its nature. It wants to become everything. The worst was how every time you open a different file, your `CWD` always changes to that file's locati…

Interesting, I consider that a great feature. That always bugged me in Vim. When I open a file in a different location, most of the time I want to be in that CWD. I guess it depends on how people work.
Post reply on HN