Ok, Let me explain this a little. I don't like this "One X to rule them all" concept, recreating complete interfaces. I would prefer to use one gui, and make the programs integrate in it, rethinking some concepts if necessary.
Been able to modify the label is fundamental for this. It's a way to identify the program and show its state. Just the same sam does inside its own duplicated interface. The correct way to do this is respecting the program design. That's why the label must be changed in the samterm side. This little change allows you to open a file with one instance of sam, another file with another instance (just not use plumb to edit...) and be able to identify them, using the gui you already have, rio. And if for example you open another file because you need them stuck side by side (but this should be done by gui, not by the editor...) you still can rename the label manually to reflect the change. The next step is add an option (or better an environment variable) to use the rio snarf buffer directly. If you don't see the point of this, just ignore this thread. I'm sharing this patch just in case someone is so frustrated as me with this design, nothing more. By the way, sam -r allows you to edit remotely a file in a unix system, not only with p9p sam, samterm will drive even the old sam from pkgsrc. Running samterm locally is way more efficient than using X forwarding. Regards, adr. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tf1e211daf823c0e0-M4075dd8b5bd996932f445643 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
