From: Elliott.Hughes@genedata.com Elliott.Hughes@genedata.com
Subject: [9fans] using sam
Date: Sat, 22 Aug 1998 17:28:35 +0200 [thread overview]
Message-ID: <19980822152835.oUIouRcbp_g8P7zlpoRv0iXK8qqSfR5Bgc30glfN5r4@z> (raw)
> The mouse paradigm works really well when I want to do
> something that involves selecting arbitrary blocks of
> text, but I find that I keep having to reach for the mouse
> when I want do simple things like move the cursor, which I
> find slows down my editing.
It was easy to add the left and right cursor keys to acme. forsyth
had a problem with this (and reckoned that rob did too) but I didn't
much care. When others asked me for this, I added it. It turned
out that I didn't use it much myself. Now I use wily (which has
cursor keys by default) I find I cursor about a bit more. I can't
fully explain this discrepancy.
> Cut and paste is a bit more tedious than just using vi in
> combination with X's swipe and paste with middle button.
> I guess I am looking for an 'insert highlighted text at
> cursor' key or menu option.
What you really want is acme's chorded cut & paste. It's the One
True Way. Didn't Plan 9 sam have this? 8.5 did, I'm sure.
> Perhaps I should be leaving myself in the sam window more?
Try acme. I used to have my profile start acme rather than 8.5, and
would only quit to use mothra or 5s ;-)
> Once there, I find I frequently have trouble getting it to accept
> commands. Half the time it just accepts my command as text to be
> stored in the buffer, so somehow I need a quick way of getting my
> cursor to the end of the buffer where presumably commands will be
> accepted (preferably without more mouse reaching)...
There's the "Send" command on the menu. Write your command
where you like, select it and "Send". Or select it using button 3 in
acme.
> Is all of this normal behaviour, or is there a problem with
> my sam setup?
It's all fairly normal. sam and acme both require a certain amount
of "user adjustment" (as does much of Plan 9) but, at least for
acme, it's certainly worth it. I couldn't live without wily on Unix
having gotten used to acme on Plan 9. Never really had much
time for sam, but then I never explored structural regexps which
were, I suppose, it's real advantage.
--
http://users.ch.genedata.com/~enh/
next reply other threads:[~1998-08-22 15:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-22 15:28 Elliott.Hughes [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-08-25 21:45 Digby
1998-08-25 20:35 Digby
1998-08-25 19:06 geoff
1998-08-25 8:41 steve_kilbane
1998-08-25 0:53 Gary
1998-08-24 21:07 forsyth
1998-08-24 19:35 Digby
1998-08-23 19:38 Digby
1998-08-23 18:42 Digby
1998-08-23 15:52 forsyth
1998-08-23 10:04 Elliott.Hughes
1998-08-22 23:02 forsyth
1998-08-22 21:19 Digby
1998-08-22 14:09 Digby
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=19980822152835.oUIouRcbp_g8P7zlpoRv0iXK8qqSfR5Bgc30glfN5r4@z \
--to=elliott.hughes@genedata.com \
/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).