From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Wed, 10 Sep 2008 21:22:50 +0100 From: "roger peppe" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> In-Reply-To: <73888427-D829-45C0-B6B5-2E7E0D0DF505@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <138575260809100704j356a9254u1705065b1e791d8d@mail.gmail.com> <73888427-D829-45C0-B6B5-2E7E0D0DF505@mac.com> Subject: Re: [9fans] Acme questions Topicbox-Message-UUID: 0eb27d94-ead4-11e9-9d60-3106f5b1d025 On Wed, Sep 10, 2008 at 7:48 PM, Pietro Gagliardi wrote: > I think double-clicking on the box to the left of the column information > line thingy should do it. erm. you really could have tried this first. it doesn't take much, you know. for the record, i once had a go at implementing a "hide" command within acme, but i never got it stable enough to make available. it would be nice if more of the invariants in the acme code were documented. what i was really aiming towards was a way to allow acme to take up multiple rio windows - the idea would be to allow dragging of acme windows (or columns) between the acme rio windows. that way i could edit a load of related files in a single rio window but avoid cluttering things up when i want to digress into another project for a while (but also avoid the risk of simul-editing a file that you get when starting two acmes at the same time). it could also make the X command more useful than it currently is. in sam, the X command is great because you can edit many related files at the same time without necessarily cluttering the screen with them, but in acme it's a bit of a pain to do a global edit across (say) 100 source files. it's for this sort of thing i end up firing up sam -d, but it's so easy to waste time with files that i'm already editing, etc. at the acme data structure level, i reckoned it shouldn't be too hard - there are multiple Windows per Column, multiple Columns per Row, but there's only one Row. if there were multiple rio windows, each would be represented by a Row, but so far i've always got bogged down in the implementation details, time restrictions and my own brain limitations...