Live data from Hacker News

Emacs, naked

bzg.fr

191–200 of 201 posts

Re: Emacs, naked

#191
post #73

I've found the latest revisions of Emacs to be incredibly ugly, and I have to turn off most of the crap (menus, etc.) to be comfortable. Stock Emacs also seems to want to open up a minibuffer when I've told it "please just edit this set of files". It's also got some idea that I want to to suspend the shell I launched it from (er, no, not ever). The argument I see on forums is: "Well, the right way to use Emacs is to…

UniPress Emacs (aka Gosling Emacs aka Soft Hoarder Emacs) had a VI emulation mode, that when you went :q, switched you back into a shell buffer that had its mode lines hidden, with all the keyboard bindings set so you couldn't tell you were in Emacs. The only vi command I know is :q!

Earlier this week I was using ed(1) to edit a conf file, because (as the parent says) I only know one vi command :-)

Re: Emacs, naked

#192

Earlier quoted context omitted.

I don't "plan" to, but I hope for it to be possible. In a couple of years, yes. LightTable shows great promise as an editor and it's design makes it well suited to being an environment in the future. I'm just worried that before LT gets to become what I want it to Emacs will already have what is attractive in LT. For me it's ClojureScript and much more flexible UI. If Emacs gets Guile as it's scripting language (and…

If you are interested in helping with the Editor and improving text support in general... the first step is to help with the new text model. If you are interested, contact us. It would be nice to have that ready for Pharo4 :-)

I was under the impression that the new editor is already in Pharo 3? I don't remember all the details, but I think I at one point saw some rich editing classes while browsing packages in my image. It implemented line-numbers and other niceties. But it may have been something I installed from squeaksource. Anyway, I only recently started playing with Pharo 3, and noticed many improvements to editor, but didn't have the time to investigate so I just assumed it's already done.

I would really like to contribute somehow to Pharo development, it's absolutely fantastic piece of software. I went through tickets on official bug-tracker, but there are many of them and it's hard to tell which are important and which are being worked on. (BTW: Komitter is a very nice idea!) I didn't write to the mailing list, because I don't have (especially lately) enough time to do anything substantial; I just wanted to get some simple regression (for example) which I could fix in a couple of minutes/half an hour. The section of bug tracker with tickets like this would be a great help. Otherwise I'll certainly try to get involved more once I have a bit more free time :)

Re: Emacs, naked

#193
post #182

Earlier quoted context omitted.

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…

If it's a command we start to use often we bind it to a shortcut (If I may presume to speak for emacs users). It's not much different than shell commands. Some you just type, some you create an alias/function shortcut for.

I recently discovered an emacs package that lets me type M-x and then the first letter or two of a command that I used recently and it completes it for me from there (smex.el). That's even easier than coming up with a new keybinding.

Just to try and help you understand how emacs users see it, your most common vim commands that are a single character are actually sometimes a single character and sometimes they need to be prefixed by an ESC to get you into the right mode. That inconsistency is what killed me when I tried to use vim. In emacs every command is always the same, no need to keep track of what mode I'm in.

Re: Emacs, naked

#194
post #183

Earlier quoted context omitted.

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.

Oh, yeah, that drives me crazy too. Usually, I cd to the root of whatever project I'm working on, and I want all paths to be relative to the root of that project (though since I started to use ctrlp[1], it's less relevant).

1: https://github.com/kien/ctrlp.vim

Re: Emacs, naked

#195

Earlier quoted context omitted.

Are you sure that MELPA has issues? I've been running with it since it started and one thing that I can say about it is that its been a joy to use. Hats off to milkypostman & sanityinc for maintaining it. If you do have an issue, I suggest you open it on MELPA's GitHub issue page and I'm pretty confident that you'll get a quick response. As for tweaking Emacs' config, yea, I have to admit, I've spent time on it too a…

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.

Or a feature. ;-) Don't forget that el-get has been popular for years, and it pulls dev versions of libraries. I don't see any compelling evidence that breakage is more frequent for MELPA users than for those who only use Marmalade.

It's correct that we don't want our current packages to build off non-master tags or branches, and that's because we've a bigger picture in mind. It's a concrete goal of MELPA is to provide two parallel archives of packages: the existing one, filled with "bleeding edge" packages, and a new archive containing "stable" packages which have been built from the same upstream sources, but using existing version tags found there. We're making progress with this goal: see https://github.com/milkypostman/melpa/pull/1407, for example.

If we can pull this off, this will yield the best of both worlds: users will get known-good versions of packages, and at the same time they will be confident that the stable packages came from the upstream developer's source tree (which isn't at all assured with Marmalade). It will also make releasing a new stable package as easy as tagging a source repository.

Recent versions of `package.el` allow packages to be pinned to specific package archives, which lets those concerned about bleeding-edge breakage pick and choose between "stable" and "unstable" packages on a case-by-case basis.

Re: Emacs, naked

#196

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…

Hmm. Is there a particular repeated source of breakage? I only use MELPA, and apart from the recent nrepl->cider migration (which was intentionally piloted on MELPA) I've not had any instances where my work was hindered by package issues. And as a maintainer, I update my packages daily.

Re: Emacs, naked

#197

Earlier quoted context omitted.

Awesome! Mind if I grab a copy of this image, to use with whatever attribution you like, on the repo README? I don't use nyan-mode myself, and it'd be nice to have the screenshot to show people who find the repository.

Sure, go ahead :). I'll put link to and/or a screenshot of your project somewhere in the Nyan Mode page/readme, as you wrote it was inspired by a comment about Nyan Mode ;).

Thanks -- but you might want to wait a little while; someone opened a Github issue pointing out that the API offers better weather info than I'm using, and also linking a weather icon font I didn't know existed, so I'm mid-rewrite right now. It'll look a lot better once it's done. :)

Re: Emacs, naked

#198

Coming from Vim, when I switched to Emacs, I found the starting aesthetic experience more than lacking (or, ugly). It took me some time (and a helpful HN discussion) until I found good themes and good plugins to make it look aesthetically pleasing (to my eyes, at least, after all people's tastes differ). If somebody is looking for a nice Emacs theme and feels that the OP is a bit too minimal, have a look at my Emacs…

I am super glad to see Soothe being used / well loved. Thanks for using it.

Re: Emacs, naked

#199

Earlier quoted context omitted.

There are serious problems trying to run it as a server on Mac OS X. Basically it's not a real option on this platofrm.

I run Emacs on Mac OS X as a server. What I don't do is "emacs --daemon". I launch Emacs and then "M-x server-start RET". This seems to avoid any weird issues. I use the "ec" script show here: http://emacsformacosx.com/tips

alias edemon='/Applications/Emacs.app/Contents/MacOS/Emacs --daemon"

will give you a more helpful alias.

Re: Emacs, naked

#200

Earlier quoted context omitted.

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…

Have you tried structured-haskell-mode[1]? There are video demonstrations here[2].

[1]: https://github.com/chrisdone/structured-haskell-mode

[2]: https://www.youtube.com/playlist?list=PLlzKKtH5TyE-R-k86na3b...

Post reply on HN