sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: Nigel Roles <ngr@symbionics.co.uk>
To: "'sam-fans@hawkwind.utcs.toronto.edu'"
	<sam-fans@hawkwind.utcs.toronto. edu>
Subject: RE: sam for 95/nt
Date: Mon, 17 Feb 1997 11:35:13 -0500	[thread overview]
Message-ID: <c=GB%a=_%p=Symbionics%l=SYMNT3-970217163513Z-645@symnt3.symbionics. co.uk> (raw)

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
>


             reply	other threads:[~1997-02-17 16:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-02-17 16:35 Nigel Roles [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-02-18  4:02 arnold
1997-02-17 17:15 Pete Fenelon
1997-02-17 17:01 erik quanstrom
1997-02-17 16:54 rsc
1997-02-17 16:26 Pete Fenelon
1997-11-17 15:58 ` Michael K. Rosenberg

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='c=GB%a=_%p=Symbionics%l=SYMNT3-970217163513Z-645@symnt3.symbionics. co.uk' \
    --to=ngr@symbionics.co.uk \
    --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).