9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "erik quanstrom" <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, "Russ Cox" <rsc@swtch.com>
Subject: Re: [9fans] Sam Rewrite (Was: SAM snarf with X)
Date: Sat,  8 Oct 2005 12:46:58 -0500	[thread overview]
Message-ID: <20051008174658.484501301BD@dexter-peak.quanstro.net> (raw)
In-Reply-To: <ee9e417a0510080845s6335c595qd05171a40b9cf2e5@mail.gmail.com>


Russ Cox <rsc@swtch.com> writes

| The die hard sam users would disagree vehemently with you.
| The nice thing about sam is that it's one window, not many,
| making it comfortable to edit a 30-file project without getting
| caught up in managing windows.  

back when i was doing distributed search, i'd have sam running for
months with 200 files in the menu.

the irony was that sam was just perfect for those tedious games
one has to play on commercial projects -- like tweeking the copytight
header in each file. X:.: ,x... is your friend.

| I still believe the chording code that's ifdef'ed out of the
| plan9port version can be made to work.

is there any particular senerio that causes a problem; i'd be
willing to take a stab at this.

i know you've mentioned protocol jam but i can't picture how
the protocol events would be different between b1+b2 and 
menu→cut. clearly, i'm missing something.

| >     4) The unshared snarf buffer issue is gone.
| 
| Again the sam die-hards will disagree with you on this one.

i would like to unshare the buffer; but i'm not intersted
in offending. perhaps this could be switched either via
command line or menu option. (ya, i know. don't kill me 
for the menu option idea.)

| >     5) The select-while-scrolling problem is solved
| >        (perhaps, again, with the simple Athena/XTerm
| >        select mechanism).
| 
| I'm not sure I want to know what this really means, but
| "simple Athena/XTerm" sure sounds like an oxymoron to me.
| 

uh, i really don't think that you need to be this radical. i've got
some code that allows 9term to scroll-select. they're based on
basically the same "struct Text", so i think it's doable.

erik


  parent reply	other threads:[~2005-10-08 17:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2005-10-09  0:11     ` Russ Cox
2005-10-08 18:02   ` erik quanstrom
2005-10-09  9:50 yard-ape
2005-10-09  9:53 yard-ape
2005-10-09 15:41 ` Russ Cox

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=20051008174658.484501301BD@dexter-peak.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@cse.psu.edu \
    --cc=rsc@swtch.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).