9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: yard-ape@telus.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Sam Rewrite (Was: SAM snarf with X)
Date: Sun,  9 Oct 2005 02:53:39 -0700	[thread overview]
Message-ID: <4348e8a3.Z3VcQ6SVX949XbvL%yard-ape@telus.net> (raw)

Russ Cox wrote:

> 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.

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.  Rob apparently designed the behaviour for consistency with it's original setting, but woudn't it be simpler if it was determined automatically by its setting?  From "The Text Editor Sam":

	"...the most obvious [problem] is that it is poorly integrated
	into the surrounding window system. By design, the user interface
	in sam feels almost identical to that of mux, but a thick wall
	separates text in sam from the programs running in mux."

>>    3) Mouse is (gasp!) configurable...
> 
> If you want xemacs, you know where to find it.

Ouch!

> I'm not sure I want to know what this really means, but
> "simple Athena/XTerm" sure sounds like an oxymoron to me.

Granted.  *Old* Athena/XTerm, then: set dot with button one click, scroll, extend dot with button three click.

>> 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.

Thanks, I'll check that out.

>>    6) Redo!
> 
> This is already implemented.

Ah!---Seems my $MANPATH has been pointing to an obsolete sam.1!  This is a very nice surprise.

(Not sure who posted this bit):

> 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.

I've thought the command line switch would be nice, too.

Thanks again,

Derek


             reply	other threads:[~2005-10-09  9:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-09  9:53 yard-ape [this message]
2005-10-09 15:41 ` Russ Cox
  -- 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=4348e8a3.Z3VcQ6SVX949XbvL%yard-ape@telus.net \
    --to=yard-ape@telus.net \
    --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).