Friendly Acme Thread

I think I've wrote most of my code in it. Nothing beats it while working on some days with pipeline toolkit.

>>58725126
>I think I've wrote most of my code in it. Nothing beats it while working on some days with pipeline toolkit.
*Data*

sam is better

>>58725179
>sam is better
you cannot beat it when it comes to remote or multiple files editing

>>58725179
isn't all of sams functionality contained in acme?
what can sam do that acme can't?

I think the concepts behind acme and plan9 are amazing, but I just cannot use it to it's full potential. In my opinion, It is not intuitive at all.

But holy fuck is it sexy.

>>58725034
I've never manged to use it. Got a good tutorial?

>>58727054
unfortunately I think there's not really a good tutorial.
There are only a few resources about acme usage online.
So I think, if you want to use Acme, then for the most part you'll have to figure out yourself how to make it work.

Russ cox tour of Acme. This might be the best tutorial available as it covers many features.
https://www.youtube.com/watch?v=dP1xVpMPn8M

A blog post series about a guy trying Acme
http://echosa.github.io/blog/2014/06/18/lets-try-acme-ep-1-hello/

A blog post about mouse usage in acme
http://jlouisramblings.blogspot.de/2012/11/is-keyboard-or-mouse-faster-for-text.html

And of course the original paper by Rob Pike
http://doc.cat-v.org/plan_9/4th_edition/papers/acme/

Sell me on acme, why should I switch from GNU nano?

>>58729312
suits the need to be different from all the other hipsters in IRC

>>58729312
By using Acme you can rid yourself of GNU, and finally feel like a true UNIX person.
As the saying goes, everything is a file in UNIX, and it shows in Acme. It has windows which show the contents of a file.
But by using a virtual file system the contents of each window are also accessible as a file.
This enables you to write other programs that manipulate the contents of Acme windows directly. This is the UNIX way of writing plugins.