From: John (For the colours are many, but the light is one.) Mackin <john@ civil.su.oz.au>
To: The sam Mailing List <sam-fans@hawkwind.utcs.toronto.edu>
Subject: Re: saved replacement texts?
Date: Mon, 23 Nov 1992 21:47:06 -0500 [thread overview]
Message-ID: <199211241347.8224.sam.babaz@civil.su.oz.au> (raw)
In-Reply-To: <92Nov23.214208est.2625@groucho.cs.psu.edu>
Just for the sake of argument, he could have done what rms did with
emacs, namely replace the current window with the new one. (Maybe I'm
just hopelessly tainted, but I think a number of emacs' features are
reasonable. :-)
Scott,
This suggestion, I am afraid, is just plain stupid, emacs or no.
You don't want the command window replaced with the window you just
said B about.
Pike did an excellent job designing the sam interface. The single
click to place the usual edit window is just what you want. Sometimes,
you want to put the command window in the middle of the top-level
window, and have edit windows above and below. If you want them to
overlap, you can, although as has been observed here before, tiling
is usually more useful.
It's not broken and doesn't need any fixing.
OK,
John.
next prev parent reply other threads:[~1992-11-24 2:51 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
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 [this message]
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=199211241347.8224.sam.babaz@civil.su.oz.au \
--to=john@civil.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).