11–20 of 55 posts
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...
But, its funny that it is more than half of the full content in the git clone...
Glad to see there is a small village of indomitable programmers still holding out against the invaders :)
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...
Its probably for testing purpose. Its a big file of natural text so you can easily checks a lot of things with it and its a lot less boring than pages of lorem ipsum... But, its funny that it is more than half of the full content in the git clone...
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…
I agree that cw violates a pattern, but I think it's a reasonable violation. (Not necessarily good, but reasonable.
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…
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…
> you will also need cweb because one file is written in literate programming Glad to see there is a small village of indomitable programmers still holding out against the invaders :)
For people not familiar with Acme, I found this 20-minute video tour very informative: http://research.swtch.com/acme
Earlier quoted context omitted.
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?
For multiple contributors, I don't think this will scale well, atleast without using some tool on top of the VCS.