From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from venus.ubs.com ([207.25.52.67]) by hawkwind.utcs.utoronto.ca with SMTP id <24673>; Mon, 17 Nov 1997 18:51:00 -0500 Received: by venus.ubs.com; id LAA23510; Mon, 17 Nov 1997 11:49:50 -0500 (EST) Received: from unknown(192.168.122.22) by venus.ubs.com via smap (3.2) id xma023505; Mon, 17 Nov 97 11:49:42 -0500 Received: from ns1.ny.ubs.com by hedy.ny.ubs.com (SMI-8.6/SMI-SVR4) id LAA28283; Mon, 17 Nov 1997 11:46:33 -0500 Received: from ny.ubs.com (rousseau.ny.ubs.com [161.239.153.13]) by ns1.ny.ubs.com (8.7.3/8.7.3) with ESMTP id KAA21240; Mon, 17 Nov 1997 10:58:15 -0500 (EST) Sender: mkr@ny.ubs.com Message-ID: <3470698F.405334B5@ny.ubs.com> Date: Mon, 17 Nov 1997 10:58:07 -0500 From: "Michael K. Rosenberg" X-Mailer: Mozilla 4.03 [en] (X11; U; SunOS 5.5.1 sun4m) MIME-Version: 1.0 To: Pete Fenelon CC: sam-fans@hawkwind.utcs.toronto.edu Subject: Re: sam for 95/nt References: <3.0.32.19970217162635.006bb15c@oberon.info-com.com> Content-Type: multipart/mixed; boundary="MimeMultipartBoundary" --MimeMultipartBoundary Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit has anyone dealt with this problem? in my opinion, the best solution would be that sam on nt writes a cr/lf when you hit return, and does not show the cr character. this makes the files different from ones created on unix systems, but, makes them consistent with all other text files and text utilities on nt, such as printing utilities. i guess this is what pete meant in his suggestion below. i'm keeping my fingers crossed that there is a better nt version of sam out there somewhere....otherwise, i think i'm going to be stuck with notepad. mike Pete Fenelon wrote: > 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? --MimeMultipartBoundary--