From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from oberon.info-com.com ([194.72.127.140]) by hawkwind.utcs.utoronto.ca with SMTP id <24620>; Mon, 17 Feb 1997 11:28:59 -0500 Received: from goose.info-com.com (localhost [127.0.0.1]) by oberon.info-com.com (8.7.5/8.7.2) with SMTP id QAA15328 for ; Mon, 17 Feb 1997 16:26:38 GMT Message-Id: <3.0.32.19970217162635.006bb15c@oberon.info-com.com> X-Sender: pete@oberon.info-com.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Mon, 17 Feb 1997 11:26:39 -0500 To: sam-fans@hawkwind.utcs.toronto.edu From: Pete Fenelon Subject: sam for 95/nt Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="MimeMultipartBoundary" --MimeMultipartBoundary Content-Type: text/plain; charset="us-ascii" In summary -- a lovely piece of work. Just what we've all been waiting for. One minor caveat, though -- under 95 (don't know about NT) it adopts the Unix-y (and indeed right-thinking) LF as newline.... which means it's not ideal for editing Windows text files which use CR/LF -- (A) it shows the CR half of CR/LF as a CR character and (B) it makes it a tad tricky to use files produced with Sam with utilities that aren't wise to the rest of the world's conventions on newline... I suppose this is the *logically* correct behaviour, but to push Sam as an editor which the Windows-user community will use, perhaps it should do the wrong but *visually* sensible thing :) Thoughts -- would it be difficult to bodge sam to treat CR/LF as one rune under Windows? pete -- Pete Fenelon, Infocom UK Ltd. pete.fenelon@info-com.com --MimeMultipartBoundary--