From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from symbionics.co.uk ([194.32.100.60]) by hawkwind.utcs.utoronto.ca with SMTP id <24626>; Mon, 17 Feb 1997 11:35:41 -0500 Received: from symnt3.symbionics.co.uk by symbionics.co.uk (4.1/SMI-4.1) id AA03917; Mon, 17 Feb 97 16:35:18 GMT Received: by symnt3.symbionics.co.uk with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.994.63) id <01BC1CF0.8D1BF640@symnt3.symbionics.co.uk>; Mon, 17 Feb 1997 16:35:14 -0000 Message-Id: From: Nigel Roles To: "'sam-fans@hawkwind.utcs.toronto.edu'" Subject: RE: sam for 95/nt Date: Mon, 17 Feb 1997 11:35:13 -0500 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.994.63 Encoding: 33 TEXT I modified the UNIX version to do CRLF translation, N space indentation, and tab to space conversion to observe our company coding standard. Not difficult. --------------- Nigel Roles, Symbionics Ltd.. >---------- >From: Pete Fenelon[SMTP:pete.fenelon@info-com.com] >Sent: 17 February 1997 16:26 >To: sam-fans@hawkwind.utcs.toronto.edu >Subject: sam for 95/nt > >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 >