From: Chris Siebenmann <cks>
To: sam-fans
Subject: Re: saved replacement texts?
Date: Mon, 23 Nov 1992 21:11:38 -0500 [thread overview]
Message-ID: <92Nov23.211144est.2806@hawkwind.utcs.toronto.edu> (raw)
In-Reply-To: noel's message of Mon, 23 Nov 92 21:02:03 -0500. <199211240202.25949.out.badag@es.su.oz.au>
Automatic placement of new windows probably isn't the default because
Pike didn't have a good way to do it, especially in sam (it's also
somewhat against the model). I don't really see how to fix that.
- cks
next prev parent reply other threads:[~1992-11-24 2:11 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 [this message]
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.211144est.2806@hawkwind.utcs.toronto.edu \
--to=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).