From: Richard <ru@ohio.river.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] command history
Date: Fri, 14 Jul 2000 16:24:35 -0700 [thread overview]
Message-ID: <200007142324.QAA08780@ohio.river.org> (raw)
In-Reply-To: <200007142137.RAA26997@smtp3.fas.harvard.edu>
I wrote:
> it also has a bunch of affordances --delete_word and such-- for editing
> a command line --a task that in the Plan 9 style is done with a mouse
> and Rio.
Russ Cox writes:
>^w will delete the current word,
>in the editors and in rio. and ^u
>the current line.
good point. so let me clarify. ile recognized the following commands,
some of which are not in the Plan 9 style because they do things the
mouse can easily do, like move the cursor.
what is slightly Plan 9ish about ile is that it "sits between"
the terminal emulator and the shell (or any other cooked-mode program).
this got me thinking that a Plan-9 port of ile could sit between
a rio window and rc (or any other line-at-a-time program). just
a suggestion.
^B - backward_char
^E - end_of_line
^F - forward_char
^K - erase_to_end_of_line
^L - retype_line
^N - forward_history
^P - backward_history
^R - search_backward_history
^V - quote
^T - transpose_chars
del - delete_char
^M - add_to_history
^J - add_to_history
^U - erase_line
^X - delete_char_under
esc b - backward_word
esc f - forward_word
esc del - delete_word
esc esc - complete_file
esc s - complete_file_full
esc p - query_path
esc d - show_files
esc u - upper_word
esc l - lower_word
esc c - capitalize_word
esc [ A - backward_history (up arrow)
esc [ B - forward_history (down arrow)
esc [ C - forward_char (right arrow)
esc [ D - backward_char (left arrow)
next prev parent reply other threads:[~2000-07-14 23:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-14 21:37 Russ Cox
2000-07-14 23:24 ` Richard [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-14 19:44 Russ Cox
2000-07-14 14:16 Stephen C. Harris
2000-07-14 21:03 ` Richard Uhtenwoldt
2000-07-14 21:25 ` Richard Uhtenwoldt
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=200007142324.QAA08780@ohio.river.org \
--to=ru@ohio.river.org \
--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).