From: hc05@summitis.com
To: sam-fans@hawkwind.utcs.toronto.edu (Sam mailing list)
Subject: 9term/9wm hacks
Date: Fri, 28 Apr 1995 16:41:53 -0400 [thread overview]
Message-ID: <9504282038.AA13616@cheetah> (raw)
>Subject: 9wm/9term cmdpipes
>X-Face: Iqsa(US9p?)Y^W+6Ff[Z]<t?\A!eaL'DG{20*#{C1;'Ct&}L}B^/1(aYI@hP)4!<}7D=2gm
> 8!$T`8QNfK<te\20%A\`wm*wa2"^Up*Qs"X}KeV*3XeB2te&sKp*t`N;^BDh[6=K{ZBE=O>rM"uFE)
> lFDjag1e]\/#2
>Content-Type: text
>Content-Length: 30278
> 8!$T`8QNfK<te\20%A\`wm*wa2"^Up*Qs"X}KeV*3XeB2te&sKp*t`N;^BDh[6=K{ZBE=O>rM"uFE)
> lFDjag1e]\/#2
>
>A while ago, I mentioned some hacks I'd done to 9term to add a
>command pipe, like sam's. Rich $alz commented that 9wm could do
>with something similar, and I couldn't resist. This is the
>result, including patches for both 9term and 9wm. There are
>probably bugs, but they work ok for me. :-) A README file
>is included.
>
>Steve
I've loaded the patches to both 9term & 9wm on an RS/6000 running AIX
3.2.5. 9term worked fine, but I had trouble with 9wm. I lost the
ability to use the mouse to anything but bring up the root menu or a
9menu. The mouse would not work for scrolling, selecting text, or
bringing up a window. I had to write to the pipe to bring up an xterm
so I could exit. I otherwise like the idea, though, and am not
complaining. I think I'll use the 9term pipe to see if I can work elm
from a 9menu.
Thanks,
Beirne
--
-------------------------------------------------------------------------------
Beirne Konarski | Reading maketh a full man, conference a
beirnek@summitis.com | ready man, and writing an exact man.
"Untouched by Scandal" | -- Francis Bacon
-------------------------------------------------------------------------------
next reply other threads:[~1995-04-28 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-04-28 20:41 hc05 [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-05-01 8:18 Steve_Kilbane
1995-02-07 12:59 Steve_Kilbane
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=9504282038.AA13616@cheetah \
--to=hc05@summitis.com \
--cc=sam-fans@hawkwind.utcs.toronto.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).