From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Sam Rewrite (Was: SAM snarf with X)
Date: Sun, 9 Oct 2005 11:41:08 -0400 [thread overview]
Message-ID: <ee9e417a0510090841g4622b1b7j2039e70075fe853a@mail.gmail.com> (raw)
In-Reply-To: <4348e8a3.Z3VcQ6SVX949XbvL%yard-ape@telus.net>
> Alright, but I'm not sure I get it. Can you give an example?
> I imagine Acme can boast a single, absolute UI policy
> only because it's a more general tool; sam(term) is just
> an editor, and so is always being used inside another
> UI setting---even if it's rio.
Rio and sam are different window managers.
If you've used both I fail to understand how you wouldn't
notice -- automatically expanding windows, the menu for
switching windows, etc. They're different. I also know people
who run sam under "standard" window managers like
those that come with Gnome. I'm sure they don't want
their sam windows to behave like the rest of gnome.
Like Erik posted, do you really want to turn 200 text editor
windows over to Gnome and expect it to do something sensible?
> Granted. *Old* Athena/XTerm, then: set dot with button
> one click, scroll, extend dot with button three click.
I thought this behavior (which, I believe, originated with PARC's 3-button
mouse and was the reason that the Mac went for the simpler 1-button
mouse) had been long acknowledged as a mistake.
On the other hand if you can make scrolling selection work like
in rio, that's the right thing to do.
For what you want, though, you can use the k command to set
a mark and then move the cursor and run ',. (or .,') to select the
region.
Russ
next prev parent reply other threads:[~2005-10-09 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-09 9:53 yard-ape
2005-10-09 15:41 ` Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-09 9:50 yard-ape
2005-10-08 12:44 yard-ape
2005-10-08 13:01 ` Uriel
2005-10-08 15:17 ` Steve Simon
2005-10-08 15:45 ` Russ Cox
2005-10-08 15:51 ` Charles Forsyth
2005-10-08 17:46 ` erik quanstrom
2005-10-09 0:11 ` Russ Cox
2005-10-08 18:02 ` erik quanstrom
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=ee9e417a0510090841g4622b1b7j2039e70075fe853a@mail.gmail.com \
--to=rsc@swtch.com \
--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).