From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <509071940802080328kc09fefcn32355757f891e1af@mail.gmail.com> Date: Fri, 8 Feb 2008 06:28:05 -0500 From: "Anthony Sorace" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] managing windows in rio In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080207172246.GG4218@gluon> Topicbox-Message-UUID: 4ba9e06c-ead3-11e9-9d60-3106f5b1d025 On Feb 8, 2008 4:47 AM, Eris Discordia wrote: > I have had similar questions about ways to streamline my Plan 9 experience > since like... a week ago (that is when I began using it). For starters, I'd suggest that if you've been using it for a week, you've not been using it long enough to properly internalize the interface. It's designed to become transparent - to be used without thinking about it - but that takes a little bit of time. Once you're there, however, you'll likely be faster than with other interfaces. That being said, there are answers to some of these questions which may keep you happy. :-) > 1. to change the focus except by mouse? Probably not in the way you're thinking of, but yes. Rio exports a file system interface which permits manipulation of windows. This is useful for programatically changing the focus, but there isn't a set of key bindings, which may be what you're thinking of. > 2. to change acme's chording behavior? No. But what would you like to change about it? > 3. to change acme's focus model from point-to-type to click-to-type? -b, the bartflag. Undocumented and, last i heard officially, experimental. It worked well for me for the week or so i tried it. > 4. to recall commands typed in an rc session without resorting to the > middle mouse button (snarf+paste)? I believe the scripts " and "" (good luck googling for that!) in /n/sources/contrib/rsc may do what you want. Note how they do what they do without adding any stupid terminal awareness to rc, or shell-specific functionality to rio. > 5. to make rc auto-scroll for programs that output many pages of text, e. > g. a du on a deep directory tree, and to not block them after a single > page? rc does not scroll; rio scrolls. Read rio's man page. > 6. to make rc auto-complete with the [tab] key, instead of the [ins] key? I don't believe so, thank god. Having to fight to get a friggin' tab when i want one is probably the "feature" of some modern unixes that irritates me most (not counting lacking features like private namespaces). > 7. to make rc auto-complete commands and not only file/directory names? > 8. to make the [del] key delete the character at the caret as it does in > many other environments? Not without mucking with the code. > 9. to search a manual page while reading it, and not by piping it through > grep? Not in rio. What you're looking for is called "look"; i believe there's been patches historically, and certainly enough people have looked for it. I've taken to reading man pages in acme, where that's easy, unless i'm just looking for a particular invocation. > 1. any (configurable or otherwise) keyboard shortcuts in acme/rio? No. Again, live with it for a bit. If you're still not convinced, google smacme. > 2. alternatives to mouse navigation and, particularly, text selection in > acme? Again, acme exports a namespace which provides much of this functionality, but there aren't a set of key bindings. The system is designed to be used with a mouse. > 3. ways to quit acid without deleting its window or hitting [ctrl]+[d] > twice, which ends up deleting the window and all the scrollback buffer > with it (I could not find a quit() function in the manual page)? I'm not certain what your issue here is, but a single ^D is enough to quit acid for me, and it doesn't kill the background.