9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Federico G. Benavento" <benavento@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] managing windows in rio
Date: Fri,  8 Feb 2008 08:58:23 -0300	[thread overview]
Message-ID: <32d987d50802080358u1cab115agb4d0b5152c1d55de@mail.gmail.com> (raw)
In-Reply-To: <op.t567mdajc6yvfe@computer>

> 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).
>
> Plan 9 interfaces I have seen (rio itself, the window to rc, acme) are too
> mousy, and I used to (and still do) curse Windows (and adore *BSD) for
> just that reason. The line editor, ed, on the other hand makes good use of
> the keyboard, but I really preferred the vi (vim, actually) way; I know,
> vi was originally built around ed.
>
we live in the 21th century

> Here are (some of) my questions:
>
> Is there some way (other than messing with the code)...
>

> 1. to change the focus except by mouse?
> 2. to change acme's chording behavior?
> 3. to change acme's focus model from point-to-type to click-to-type?

1, 2, 3: change the code

> 4. to recall commands typed in an rc session without resorting to the
> middle mouse button (snarf+paste)?

russ has to useful scripts " and "" one prints the last comand the other
executes it. what they do is grepping /dev/text

> 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"

> 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.

> 7. to make rc auto-complete commands and not only file/directory names?

different OS & paradigm == different behavior

> 8. to make the [del] key delete the character at the caret as it does in
> many other environments?

<del> in rio interrupts the program being run

> 9. to search a manual page while reading it, and not by piping it through
> grep?
>

read man pages in acme and just use Look or right click in the word you
want to search

> Are there...
>
> 1. any (configurable or otherwise) keyboard shortcuts in acme/rio?

no

> 2. alternatives to mouse navigation and, particularly, text selection in
> acme?

no

> 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

> Notes on the Plan 9 way of interfacing (the user side of it, of course)
> are also welcome. Perhaps there are better/faster ways to do things that I
> am not aware of.


use the system, it's not supposed to feel like "home", it's a
different environment,
hence it has a different behavior. so try to be a bit open minded here

--
Federico G. Benavento


  parent reply	other threads:[~2008-02-08 11:58 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 [this message]
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
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=32d987d50802080358u1cab115agb4d0b5152c1d55de@mail.gmail.com \
    --to=benavento@gmail.com \
    --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).