Live data from Hacker News

Edit: A Relaxing Mix of Vi and Acme

c9x.me

31–40 of 55 posts

Re: Edit: A Relaxing Mix of Vi and Acme

#31
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…

While I'm all for not standardizing on github, git send-email doesn't actually work. First off, your assumption that people use the command line to interact with git is no longer correct. While that was true when I started using git, that's no longer a requirement for basic usage. Next, perhaps as a corallary, many computer users don't have local email working, ie 'mail user@example.com' on the command line doesn't w…

It's been a few years, but I got `git send-email` to work pretty easily back when I was contributing to Git. I seem to recall there simply being some configuration to tell it what SMTP server to use, and then just creating a single ~/.gitaliases file to map nicknames to email addresses.

There's also `git imap-send` if you want to have it dump the email into the Drafts folder on an IMAP server, where you can review it and send it from your normal mail client.

Re: Edit: A Relaxing Mix of Vi and Acme

#32
post #30

That's neat, it reminds me of MPW and the scheme interpreter I used long ago on a mac, wish I could remember which one now. They had a worksheet where you could go back to a previous line with the keyboard or mouse and hit enter there (or edit it first and hit enter then) to execute. I had a very nice worksheet with lots of templates I would follow.

Eddie(Text Editor) by Pavel Císler has a worksheet like that.

Re: Edit: A Relaxing Mix of Vi and Acme

#35
post #2

Lovely.... Now to get some command line utils to interact with a clojure repl and some form of splits (i.e. for documentation). This is actually something I might contribute to! :P edit: async is already in... mea culpa

Splits are available in the git master branch.

Re: Edit: A Relaxing Mix of Vi and Acme

#36
post #8

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…

> Presumably in this editor "_" represents the "whole line" region, which leads to also "c_" and "y_".

That's not specific to this editor. In vim _ goes from the cursor to the end of the line (but does not include the newline at the end like $ does).

Re: Edit: A Relaxing Mix of Vi and Acme

#37
post #9

I found this in the doc/ subdirectory of the repository: http://c9x.me/git/?p=ed.git;a=blob;f=doc/republic.txt;h=366f... I am really curious about what the full text of Republic is doing here...

I thought it could be fun to include it in the documentation. Why not, after all. This is a good read. It turns out that I also used it for tests, if the editor behaves smoothly on this file I judge it fast enough.

Re: Edit: A Relaxing Mix of Vi and Acme

#38
post #8

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…

The reasons you cite are the reasons why it is that way. Concerning the 'c' command, I leave it that way until people are so annoyed that they have to dive in the code themselves, it is a kind of social experiment. I got used to not using it.

I went through lots of thinking to make the code nice and clean and would like to see if it is indeed that way by having people modify it.

Re: Edit: A Relaxing Mix of Vi and Acme

#39
post #34

I might just be missing it, but I don't see the license mentioned anywhere. Anyone know what it is?

I hacked it. It's public domain for now. I might (or not) switch to MIT later.

I don't think that's possible. If it's public domain, none can claim copyright.

Re: Edit: A Relaxing Mix of Vi and Acme

#40
post #19

Earlier quoted context omitted.

Also, I asked HN about modern Acme clones recently: https://news.ycombinator.com/item?id=8269442 (glad this came along)

I'm the developer of plan9-for-vimspace[1], which you mentioned in your thread. I've not been very active with it, because I came up against some limitations in vim, but I really want to go further with it. I would really like some feedback on what stuff should go in or out. I've thought a lot on how to implement acme's tag lines and a plumber system (just this weekend, I was thinking of providing a fuse-based system…

Were the issues you hit being addressed by neovim (https://github.com/neovim/neovim)? They seem to be pretty interested in making a more extensible vim.
Post reply on HN