From: mhw@minster.york.ac.uk mhw@minster.york.ac.uk
Subject: Faking it under Unix (was Re: Plan 9: The future)
Date: Mon, 7 Mar 1994 08:13:21 -0500 [thread overview]
Message-ID: <19940307131321.nTrGSJeUy0QKZAZWaetLcF_7Y9PrDHl6KRC07oFRMGU@z> (raw)
> Gary (and
> others) have been asking me about chording too so I've at least thought
> about it.
After doing the chord patch for sam I found it quite easy to do the same
thing for 9term. It relies on the one line change to libframe/frselect.c
to get it to work. I've not mailed it to the list though because I'm not
really happy about the way it works. If you study it closely, cut and paste
in 9term is actually inconsistent with sam in that pasted text does not
stay selected (at least in the version I run). I did a patch where chording
buttons 2 and 3 did cut and paste and found I didn't use it very much after
all. I know run a version where button 3 does send without appending a \n
to the text and this works quite nicely as it support picking things from
the previous text to be entered into the new command. It does annoy a little
when you want to edit some text for input to a command though.
Anyway, I can mail you both patches if you want (they're not that much
different anyway) and you can see what you think. I find 9term is dissimilar
enough from sam to require a slightly different style of working.
Look forward to the new version...
-Mark.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Mark H. Wilkinson <mhw@minster.york.ac.uk> : Research student in user
University of York, England : interface management systems
next reply other threads:[~1994-03-07 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-03-07 13:13 mhw [this message]
-- strict thread matches above, loose matches on Subject: below --
1994-03-06 2:33 Gary
1994-03-05 11:18 James
1994-03-05 6:15 Scott
1994-03-04 17:30 Chris
1994-03-04 15:36 Arnold
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=19940307131321.nTrGSJeUy0QKZAZWaetLcF_7Y9PrDHl6KRC07oFRMGU@z \
--to=mhw@minster.york.ac.uk \
/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).