Hacker News Reader

Comment by Raphael_Amiard | Hacker News Reader

It is absolutely gorgeous, but it is also looking a lot more like a traditional text editor from what i can gather.

I'll download and play with it a bit anyway, to see what i get from it.

It is, but that's because we have to have a solid editing experience for the "simple" stuff before we can do the more interesting things. What good is it to have these awesome function oriented editors when you can't even modify a file efficiently? :)

We use tabs as a simple way of wrapping up a context. In the future they will include all sorts of neat things - and they aren't limited in any way. If we want, we can drop an infinite canvas into one, or a codex (a document made of many parts of different files). So yes, right now we wanted something beautiful and efficient to use while live coding, but as I said in my bit about 0.4.0, the really interesting semantic-oriented stuff (functions and the like) is what's next!

Has anyone started work on an Emacs Lisp to ClojureScript compiler? :)

Speaking of which, are Emacs keybindings coming any time soon?

and ParEdit

Seconded. If you're going to have any success in converting people who write Clojure code away from Emacs, you're going to need to copy its good parts.

Nice redesign though.

"If you're going to have any success in converting people who write Clojure code away from Emacs"

I'd say it would already be great if they could bring newcomers to Clojure: people who are rebutted because of Emacs.

As to me I'd need, at least: ace-jump-mode, paredit, the powerful macro system and the ability to create my own rules for highlighting / overlaying text as easily as from Emacs.

Short of that I'll keep using Emacs. Now what I think: it's probably easier to add LT's "instarepl" to Emacs than to add one million lines of elisp code to LT so...

I fully expect someone to hack a "Clojure instarepl" Emacs mode one of these days.

+1 for Emacs keybindings

(+ 1 1)

(partial (+ 1))

https://github.com/hraberg/deuce

I for one am glad you're nailing the editor part first. Because if this is ever to replace my usage of emacs, you have to at least get that part right. This hasn't yet replaced my emacs, but i'm more optimistic now. Some editing features missing are paredit, viewing source code of a clojure core function. (Alt-. in emacs.) When you eval something and it never terminates, you need a way to kill that thread. For IDE like features, #1 on my list is refactoring clojure code quickly, e.g. renaming symbols. As someone who's anal about prioritizing time, I don't ever customize the themes, etc, I just want killer useful features that save me time and "just work".

Even getting all of paredit is not essential imo - I'd settle for just slurp and barf support.

+1 for strong editing features. All the fancy stuff came after Emacs became an OS for editing text. Nail that, the rest follows.

Reply on news.ycombinator.com