From: "Josh N. Pritikin" <jpab+@andrew.cmu.edu>
To: rc@archone.tamu.edu
Subject: Re: Reactive Keyboard
Date: Mon, 16 Mar 1992 13:19:38 -0600 [thread overview]
Message-ID: <wdlDH_u00VpJ8CYVJK@andrew.cmu.edu> (raw)
In-Reply-To: <9203161203.AA04226@piggy.ucsb.edu>
> perhaps fd passing? fd#10 (<--some well-known number) would be a pipe
> to/from the editor where you could write() changes in cwd? (fd 3 is
> used by Dan Bernstein's pty package, for /dev/tty, btw.)
Yah. I was going to suggest a similar mechanism.
> we're sort of going off the subject of rc here, but hopefully, enough
> of us are concerned about making *modular* (not in the shell) line
> editing interfaces that we can have some talk about it. besides, rc
> is perfect, already, right?? :-)
That's why I brought it up. rc is pretty much exacly what I want in a
shell (except for its lack of job control :-) but I would never
consider using it without emacs like editing functions. I feel that
something like rk provides this without bloating rc with unnecessary
features. From this point of view, rk and similar hacks seems quite
relivent to this list.
Currently, I don't know enough about the tty to try hacking rc-rk
communication in but it sounds like an interesting project if I have
time.
( Josh Pritikin jpab+@andrew.cmu.edu
( It might be hot in Pittsburgh, but at least it's humid.
next parent reply other threads:[~1992-03-16 19:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9203161203.AA04226@piggy.ucsb.edu>
1992-03-16 19:19 ` Josh N. Pritikin [this message]
1992-03-16 20:02 ` schwartz
1992-03-16 1:14 Josh N. Pritikin
1992-03-16 4:59 ` schwartz
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=wdlDH_u00VpJ8CYVJK@andrew.cmu.edu \
--to=jpab+@andrew.cmu.edu \
--cc=rc@archone.tamu.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).