sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: byron@netapp.com (Byron Rakitzis)
To: alan@oldp.astro.wisc.edu, sam-fans@hawkwind.utcs.toronto.edu
Subject: Re:  Lines and last lines.
Date: Tue, 1 Dec 1992 00:08:21 -0500	[thread overview]
Message-ID: <9212010508.AA15071@netapp.netapp.com> (raw)

>My first comment is that [2] is somewhat against sam's philosophy that
>files are arbitrary byte streams; it does impose a structure on the
>file (i.e., that the final character must be \n).

Unfortunately, sam's philosophy is most emphatically not that files are
arbitrary byte streams. e.g.:

; sam -d
B /bin/ls
 -. /bin/ls
?warning: null characters elided

and this is an improvement(!) on the previous situation (pre-unicode?),
which was that any "non-ascii" characters got elided. I'm not sure if
that meant nul+any-characters-with-the-8th-bit-set or what.

Anyway, in case you haven't noticed, I think this is one of sam's more
serious design flaws. It's one of the few reasons why I still want
emacs available on the Unix machines I use. (other reasons: gdb support
and glass tty support, i.e., the Poor Man's Window System.)


             reply	other threads:[~1992-12-01  5:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1992-12-01  5:08 Byron Rakitzis [this message]
  -- strict thread matches above, loose matches on Subject: below --
1992-12-01 19:54 Byron Rakitzis
1992-12-01 19:27 Alan Watson
1992-12-01  7:57 Byron Rakitzis
1992-12-01  7:11 Michael John Haertel
1992-12-01  7:01 Alan Watson
1992-12-01  0:40 Alan Watson
1992-12-01  5:46 ` Chris Siebenmann

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=9212010508.AA15071@netapp.netapp.com \
    --to=byron@netapp.com \
    --cc=alan@oldp.astro.wisc.edu \
    --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).