I’ve only skimmed this at the moment, but compiling highlights and philosophy from Plan 9 (and adjacent) mailing lists is something I’ve wanted to do for a while, so I’m really happy someone else has had the idea.
Indeed. although the current post only scratches the surface. I regularly mine 9fans for tips and tricks from seasoned practitioners. I use (deadpixi) sam especially when working on remote machines. It is a refreshing change from the frantic typing required on emacs and vi(m) and not having to carry your config across machines. Terminals still need a lot of typing but using @LeahNeukirchen’s tt, which is a Ruby/Tk implementation of the ideas from 9term, has made it tolerable again. Perhaps I should switch to acme fully…
Ruby/Tk was a bit of a bother to build (needed some symlinks to find the libs). Once built, tt is easily one of the most useful v0.1 program on my computers. Thanks!
I would go back to using Acme if it worked properly on “modern” Linux (read: Wayland). It’s easily the most consistent and frictionless development setup I’ve ever used.
ACME really shines on its native OSes that are designed for it, such as Plan 9 and Inferno.
There used to be an inferno instance with ACME called ACME_SAC that could be run in Windows, Linux and OSX which could access the host operating system paths. I really wish that it gets reborn one day.
sadly, VitaNova stopped working on it. But the code is all there. Eventually, I believe almost all of these tools would be ported to Go and “modernized”. There is already a version of Sam in progress.
I’ve only skimmed this at the moment, but compiling highlights and philosophy from Plan 9 (and adjacent) mailing lists is something I’ve wanted to do for a while, so I’m really happy someone else has had the idea.
Indeed. although the current post only scratches the surface. I regularly mine 9fans for tips and tricks from seasoned practitioners. I use (deadpixi) sam especially when working on remote machines. It is a refreshing change from the frantic typing required on emacs and vi(m) and not having to carry your config across machines. Terminals still need a lot of typing but using @LeahNeukirchen’s tt, which is a Ruby/Tk implementation of the ideas from 9term, has made it tolerable again. Perhaps I should switch to acme fully…
Amazing this still works!
Ruby/Tk was a bit of a bother to build (needed some symlinks to find the libs). Once built, tt is easily one of the most useful v0.1 program on my computers. Thanks!
I would go back to using Acme if it worked properly on “modern” Linux (read: Wayland). It’s easily the most consistent and frictionless development setup I’ve ever used.
ACME really shines on its native OSes that are designed for it, such as Plan 9 and Inferno.
There used to be an inferno instance with ACME called ACME_SAC that could be run in Windows, Linux and OSX which could access the host operating system paths. I really wish that it gets reborn one day.
sadly, VitaNova stopped working on it. But the code is all there. Eventually, I believe almost all of these tools would be ported to Go and “modernized”. There is already a version of Sam in progress.