From: john@csplan9.rit.edu
To: 9fans@cse.psu.edu
Subject: Re: [9fans] managing windows in rio
Date: Fri, 8 Feb 2008 11:47:38 -0500 [thread overview]
Message-ID: <55101bb24882790e01d7dc223c961ccd@csplan9.rit.edu> (raw)
In-Reply-To: <32d987d50802080358u1cab115agb4d0b5152c1d55de@mail.gmail.com>
benavento@gmail.com wrote:
>
>> 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?
>
> middle click, "scroll"
Or, if you really want, start rio with the -s option; you can modify your
lib/profile to do that.
>
>> 6. to make rc auto-complete with the [tab] key, instead of the [ins] key?
>
> why would you want that, get use to the system, this is a new world
> don't go to Laos and expect everyone speak english.
All "please god must every newbie ask these same questions" hostility aside,
when you consider that Plan 9 rebinds Caps Lock to be Control, typing
^F for completion is actually pretty handy.
>> Are there...
>>
>> 1. any (configurable or otherwise) keyboard shortcuts in acme/rio?
>
> no
Actually, it has ^A and ^E to go to the start and the end of the current
line, respectively. The reason for 'smacme' is that Ron got annoyed without
keyboard shortcuts, saw that there were already the (undocumented?) ^E and
^A commands, and went ahead and added some more bits.
>> 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)?
>>
> read its man page
>
Yes, the man page is always a good idea. Also... you only have to hit ^D
once. If you've been running a program within acme, it will then print
out a command you can send to rc to kill that program.
John
next prev parent reply other threads:[~2008-02-08 16:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 17:22 lejatorn
2008-02-07 17:25 ` andrey mirtchovski
2008-02-07 17:44 ` lejatorn
2008-02-07 17:45 ` Lluís Batlle
2008-02-07 17:59 ` john
2008-02-07 19:11 ` Steve Simon
2008-02-07 19:17 ` john
2008-02-07 19:45 ` Axel Belinfante
2008-02-08 9:47 ` Eris Discordia
2008-02-08 11:17 ` Martin Neubauer
2008-02-08 11:28 ` Anthony Sorace
2008-02-08 11:58 ` Federico G. Benavento
2008-02-08 12:58 ` Anthony Sorace
2008-02-08 13:04 ` erik quanstrom
2008-02-08 13:22 ` Eris Discordia
2008-02-08 13:31 ` erik quanstrom
2008-02-08 13:34 ` roger peppe
2008-02-08 14:26 ` Michael Andronov
2008-02-08 14:36 ` roger peppe
2008-02-08 19:18 ` Russ Cox
2008-02-08 16:47 ` john [this message]
2008-02-08 17:08 ` Uriel
2008-02-08 19:21 ` Russ Cox
2008-02-21 9:28 ` Mathieu L.
2008-02-21 10:24 ` Christian Kellermann
2008-02-21 10:47 ` lejatorn
2008-02-21 16:12 ` ron minnich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55101bb24882790e01d7dc223c961ccd@csplan9.rit.edu \
--to=john@csplan9.rit.edu \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).