sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: Scott Schwartz <schwartz@groucho.cs.psu.edu>
To: byron@netapp.com (Byron Rakitzis)
Cc: arnold@cc.gatech.edu, noel@es.su.oz.au,
	sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: saved replacement texts?
Date: Mon, 23 Nov 1992 19:16:20 -0500	[thread overview]
Message-ID: <92Nov23.191642est.2601@groucho.cs.psu.edu> (raw)
In-Reply-To: Your message of "Mon, 23 Nov 92 17:03:01 EST." <9211232203.AA24462@netapp.netapp.com>


| IMO. e.g., I think that 99% of the time the overlapping windows in 
| sam are useless. 

One thing that bothers me is that only the top window has focus, so
letting them peek out from under is unhelpful.  I wind up tiling them,
or just switching back and forth with button-3.  Multiple toplevel X
windows, are probably a better idea for something like sam.  Mxedit
does that, and it works pretty well.  Epoch doesn't do so well, mostly
because people do heavyweight blocking operations (like reading news!)
in one window which block the others; in emacs, since the windows are
in the same frame, it's more obvious that there is one thread of
control for the lot of them.

It's also annoying that moving a window is implemented by resizing,
which makes it hard to just move it without resizing.



  reply	other threads:[~1992-11-24  0:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1992-11-23 22:03 Byron Rakitzis
1992-11-24  0:16 ` Scott Schwartz [this message]
1992-11-24  2:02 ` noel
1992-11-24  2:11   ` Chris Siebenmann
1992-11-24  2:41     ` Jeremy Fitzhardinge
1992-11-24  2:46       ` Scott Schwartz
1992-11-24  2:41     ` Scott Schwartz
1992-11-24  2:47       ` John Mackin
1992-11-24  3:10         ` Scott Schwartz
  -- strict thread matches above, loose matches on Subject: below --
1992-11-24  5:18 Byron Rakitzis
1992-11-24  3:19 Byron Rakitzis
1992-11-24  4:02 ` John Mackin
1992-11-24  3:05 Byron Rakitzis
1992-11-23 23:31 Arnold Robbins
1992-11-23 21:51 Arnold Robbins
1992-11-23 21:53 ` noel

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=92Nov23.191642est.2601@groucho.cs.psu.edu \
    --to=schwartz@groucho.cs.psu.edu \
    --cc=arnold@cc.gatech.edu \
    --cc=byron@netapp.com \
    --cc=noel@es.su.oz.au \
    --cc=sam-fans@hawkwind.utcs.toronto.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).