Because some people like the tag/command line per window (acme) and others like the single command window (sam)?
You certainly won't see sam and acme merged into a single UI that satisfies everyone.
I occasionally use sam as a stream editor, but I couldn't imagine doing all my work in it. The cut and paste mechanic feels so awkward compared to acme's.
It's just different. I started out using sam and only switched to acme to get button 3 while editing HTML, or for editing very large files, and then I got hooked. Even so, these days I do probably 50% acme on local files, 50% sam -r on faraway files, and I don't notice the cut and paste issue in sam. (It probably helps that I type ESC to cut, so my middle button menu is usually on paste already.) I have toyed with the idea of building up some sam protocol tools, including a multiplexor and a version of acme that uses a remote sam as a back end.
Say...Does anyone know of a patch for OS X that makes chording work? Then I could bind to copy and paste properly.
See #define chording in http://swtch.com/usr/local/plan9/src/cmd/samterm/main.c Some people have seen it cause deadlocks. Others apparently use it all the time without problem. I can't understand how it could cause a deadlock if the non-chording code is correct, but maybe the non-chording code avoids whatever race is going on because there are fewer clicks flying around. Russ
