>From experience, Sam's command window provides a more consistent experience with the rest of the system. Acme on the other hand pretends to have individual command windows (more like command lines) for every file open. Sam has some form of "tiling", but not as automatic as Acme. Sam also has a remote editing protocol, unlike Acme. I liked Sam not only for those reasons, but also because of what Charles said - you can script Sam with sam -d, allowing it to integrate into other parts of the system.
It's too bad there has not been a clean rewrite of Sam, like Rob has mentioned in his paper. On Thu, May 19, 2016 at 4:26 PM, Mark Lee Smith <nety...@gmail.com> wrote: > I'm was merely explaining my understanding of the context so that I could be > corrected if I was wrong on any point. I didn't mean to explain Acme to you. > While I replied to you (I believe I did), please understand my question in > the light of the thread, as it were, a whole. > > Thanks, everyone, for the answers! > > > On Thu, 19 May 2016 at 21:38 <cinap_len...@felloff.net> wrote: >> >> mark, why do you explain acme to me? >> >> -- >> cinap >> >
