From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Sun, 28 Aug 2005 20:36:52 -0400 From: Russ Cox To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] p9p: SAM snarf with X In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: Topicbox-Message-UUID: 80e4f2ec-ead0-11e9-9d60-3106f5b1d025 > would it be utter sacrilege and or a complete waste of time > to add some acme features to samterm like: >=20 > 1. sharing the snarf buffer with the window system. > 2. cording >=20 > 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). =20 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=20 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 >=20 > x:0x....: |tr 'A-Z' 'a-z' >=20 > gave me "addresses out of order". sam was happy with it. > the text i had selected was like this: >=20 > {0x00AA, 0x00AA, "whatever",}, > {0x00BB, 0x00BB, "whatever2",}, this is probably a real bug. russ