> would it be utter sacrilege and or a complete waste of time
> to add some acme features to samterm like:
>
> 1. sharing the snarf buffer with the window system.
> 2. cording
>
> i've been thinking about this for a while, but haven't gotten
> to it.
the two-half structure of sam (+samterm) makes these
interesting, but i think both are possible. to do the snarf
thing i think you could just change samterm (it knows enough
to know when something has just been cut or is about to be
pasted).
to add chording (presumably cording has something to
do with processing /sys/log), there is some code that is
marked with if(chording) in the plan9port version of samterm,
but rob got it to hang so i disabled it. rob said that his earlier
attempts had locking problems too. i stared at the code for
a while and couldn't figure out what could be wrong (i started
with steve's code and tweaked it a little) and gave up. i use
acme anyway. the problem is that the races are hard to
tickle but really frustrating when you hit one while editing
something important.
> maybe the answer is "use acme, then". but often i want sam.
> it's a lot easier to do some complicated, scripted editing
> with sam than anything else. i like having a terminal-like
> window for editing.
i just open sam when i have a collection of files to do
a lot of regexp work with. even if acme had what you
ask for above, the ~~sam~~ window is missing.
> btw, this command with acme
>
> x:0x....: |tr 'A-Z' 'a-z'
>
> gave me "addresses out of order". sam was happy with it.
> the text i had selected was like this:
>
> {0x00AA, 0x00AA, "whatever",},
> {0x00BB, 0x00BB, "whatever2",},
this is probably a real bug.
russ
