Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Edit: A Relaxing Mix of Vi and Acme

c9x.me

Post reply on HN
Print view View original

1–10 of 55 posts

Re: Edit: A Relaxing Mix of Vi and Acme

#4

Post by micheljansen »

Looks like there are some differences with vi, among others:

* "dd" is not implemented, use "d_"

* "cw" will not work as in vi, use "ce" or "cl"

* "r" is not implemented, use "cl"

I think these are very common mnemonics, so I wonder why they are not implemented and if there are any plans to do it in the future. I use these all the time, so this would be a major turnoff for me.

Re: Edit: A Relaxing Mix of Vi and Acme

#5

Post by bru »

rcarmo wrote: post #3

Very nice. Wish it was on Github for easier contributing (and issue tracking).

>easier contributing

Er... what? What's hard about contributing? You don't have to go through a web interface for everything? IMHO that makes it easier.

    $ git clone git://c9x.me/ed.git
    
    $ git format-patch --cover-letter  
    
    $ git send-email
`man git send-email` will tell you anything you need to know: configuration options, examples... If is well-written and straightforward! Seems like the author isn't interested in public issue tracking (yet), and using Github wouldn't have changed that.

I, for one, celebrate that he's not using Github. I'm very afraid of the git == github trend I'm seeing amongst many people (technically semi-literate or even technical people)

Re: Edit: A Relaxing Mix of Vi and Acme

#6

Post by allegory »

bru wrote: post #5
rcarmo wrote: post #3

Very nice. Wish it was on Github for easier contributing (and issue tracking).

>easier contributing Er... what? What's hard about contributing? You don't have to go through a web interface for everything? IMHO that makes it easier. $ git clone git://c9x.me/ed.git $ git format-patch --cover-letter $ git send-email `man git send-email` will tell you anything you need to know: configuration options, examples... If is well-written and straightforward! Seems like the author isn't interested in publi…

Excellent points. Monocultures are terribly harmful, especially in the open-source side of things. While github is convenient, it's not the right answer for a lot of things and terribly inconvenient for others.

I use git without github. I use it with vim outliner and keep the issues in the repo.

Re: Edit: A Relaxing Mix of Vi and Acme

#7

Post by rcarmo »

bru wrote: post #5
rcarmo wrote: post #3

Very nice. Wish it was on Github for easier contributing (and issue tracking).

>easier contributing Er... what? What's hard about contributing? You don't have to go through a web interface for everything? IMHO that makes it easier. $ git clone git://c9x.me/ed.git $ git format-patch --cover-letter $ git send-email `man git send-email` will tell you anything you need to know: configuration options, examples... If is well-written and straightforward! Seems like the author isn't interested in publi…

I wouldn't mind bitbucket, either. Anything that would give this more exposure.

And, seriously, e-mailing patches is tedious, error-prone and ultimately inefficient. _anything_ that smooths the path for contributors is paramount for a successful project, and I, for one, would love this becoming more than a one-off, niche thing.

(I'd also like to have Alt-Enter instead of Tab on it, and a Mac port, and even though the first is trivial enough to do, the second requires a fair amount of time to implement)

Re: Edit: A Relaxing Mix of Vi and Acme

#8

Post by xiaq »

micheljansen wrote: post #4

Looks like there are some differences with vi, among others: * "dd" is not implemented, use "d_" * "cw" will not work as in vi, use "ce" or "cl" * "r" is not implemented, use "cl" I think these are very common mnemonics, so I wonder why they are not implemented and if there are any plans to do it in the future. I use these all the time, so this would be a major turnoff for me.

Because they are not very reasonable?

* "dd" isn't reasonable because it violates the "command + movement/region" structure of vi commands. So is "cc" and "yy". None of "c d y" is not a movement or region. Presumably in this editor "_" represents the "whole line" region, which leads to also "c_" and "y_". Much more regular although it does require you to lift your finger one more time.

* "cw" isn't reasonable because "w" as a movement usually means "to the next word", but in "cw" it means "to the end of current word" instead. "ce" is indeed better.

* "r" is actually not bad (indeed "rx" is equivalent to "clx", but the former requires 2 keystrokes), but I guess it's because the author rarely uses it.

Anyway the editor is pretty small, it might be easy or even fun to hack it! :)

Re: Edit: A Relaxing Mix of Vi and Acme

#10

Post by bru »

allegory wrote: post #6
bru wrote: post #5

Earlier quoted context omitted.

>easier contributing Er... what? What's hard about contributing? You don't have to go through a web interface for everything? IMHO that makes it easier. $ git clone git://c9x.me/ed.git $ git format-patch --cover-letter $ git send-email `man git send-email` will tell you anything you need to know: configuration options, examples... If is well-written and straightforward! Seems like the author isn't interested in publi…

Excellent points. Monocultures are terribly harmful, especially in the open-source side of things. While github is convenient, it's not the right answer for a lot of things and terribly inconvenient for others. I use git without github. I use it with vim outliner and keep the issues in the repo.

You use vim outliner plugin for the issues? How does that work?

Are your issues simple text files describing it? In a "issues" folder? Do you enforce a format? How do you track their status?

Post reply on HN