From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom To: quanstro@quanstro.net, Russ Cox References: <8661598e52b36f61c8a282f789f40c25@swtch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 In-Reply-To: <8661598e52b36f61c8a282f789f40c25@swtch.com> Subject: Re: [9fans] Plan9Ports libdraw open-in-same-window Message-Id: <20060310152147.E649CCE863@dexter-peak.quanstro.net> Date: Fri, 10 Mar 2006 09:21:47 -0600 Cc: 9fans@cse.psu.edu Topicbox-Message-UUID: 11d914ae-ead1-11e9-9d60-3106f5b1d025 perhaps you're right. i have avoided writing X programs. paul would know better than i. perhaps you're right about creating a single /dev/draw tree. the tradeoff would be a little more bookkeeping within the server, and and more sensitivity to bugs in the server, but it really would mimic plan9. btw, in plan9 is it possible to change any of env variables that an already-running rio uses for new windows? one advantage of the current p9p setup is that 9term -f $font allows one to start a new window with a different font. - erik "Russ Cox" writes | | > to make X happy, you'd want a 1:1 correspondence | > between devdraw servers and windows. | | I do not believe this is true at all. I would want just | one devdraw server for all the windows, so that | there could be a single /dev/draw tree just like in Plan 9. | | By all means try it, but I'm not convinced yet. | At the least it will be useful for drawterm. | | Russ