From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@cse.psu.edu Subject: Re: [9fans] Acme 3-1 From: rog@vitanuova.com MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Date: Tue, 18 Feb 2003 12:12:42 +0000 Topicbox-Message-UUID: 674433de-eacb-11e9-9e20-41e7f4b1d025 > 3-1 and 2-1 are already defined: they cancel button 3 and button 2 actions. > I would object to giving them another meaning. i thought 2-1 appended the most recently selected text as an argument to the executed command (and 2-3 cancels the b2 action). i use this for Edit commands (and was confused a moment ago because it doesn't work in Mail windows). as far as i can see 3-1 is the only button chord that's currently redundant (has the same meaning as 3-2): 1 select 2 execute 3 look 1-2 cut 1-3 paste 2-1 execute with args 2-3 cancel execute 3-1 cancel look 3-2 cancel look that's not an argument for giving it a new meaning! i do sometimes wish for a way to express plumbing preferences dynamically (e.g. when starting a new copy of acme and wishing that a) text files would open in the new copy and b) that other plumbing would still work). i wondered if perhaps it might make sense for an application to be able to write a "priority" message to the plumbing "send" file - plumbing messages would be then routed to that app in preference to others (a plumbing message would be sent to only one app, rather than fanning out as currently). an application could send the "priority" message when its window was raised. this might provide behaviour that seemed reasonably natural. what currently depends on the fan-out behaviour of plumbing? (mail/fs, i guess, when messages are deleted, but that's very slow, and works without plumbing anyway).