From: Charles Forsyth <charles.forsyth@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] A few questions about sam
Date: Thu, 22 Jul 2021 20:18:28 +0100 [thread overview]
Message-ID: <CAOw7k5h1Mbz2KuEF01rY4N+fbHV-3bEuER9SfPm2a0EMtJghWQ@mail.gmail.com> (raw)
In-Reply-To: <20210722191053.o75rwrxssyb74pbp@nohostname>
[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]
>/tmp/x: ?warning: last char not newline
is a warning you get when you try to write a file that doesn't end with a
newline, the other message:
> I sometimes get the "?newline expected" error,
is provoked by a syntax error in a command in the sam (command) window. For
instance, try typing
qx
(and a newline)
it expects nl after q
On Thu, Jul 22, 2021 at 8:14 PM mcz <emcze@ya.ru> wrote:
> > * Must every sam file end with a newline? I.e. even files with simple
> text?
>
> No, I don't think sam cares.
>
> > I sometimes get the "?newline expected" error,
>
> In sam version I use, it's just a warning. The file is saved without
> newline at
> the end, unless I add it there.
>
> > which I would like to avoid if possible.
>
> The best way to avoid the warning about the missing newline character is
> to add
> the missing newline character.
>
> Some programs (POSIX world, ANSI C) assume that every line ends with
> newline
> character, so most editors add it for you if it's missing. Sam apparently
> thinks it's good to have it, but doesn't get in your way if you don't add
> it.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T60b5c1929a63b077-Mee00a57a34c332edd0a4e2a0
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 3091 bytes --]
next prev parent reply other threads:[~2021-07-22 19:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 13:38 revcomninos
2021-07-22 13:57 ` Sigrid Solveig Haflínudóttir
2021-07-22 14:59 ` revcomninos
2021-07-22 19:10 ` mcz
2021-07-22 19:18 ` Charles Forsyth [this message]
2021-07-22 19:24 ` Charles Forsyth
2021-07-22 20:18 ` revcomninos
2021-07-22 23:45 ` Silas McCroskey
2021-07-23 4:47 ` revcomninos
2021-07-23 5:42 ` Silas McCroskey
2021-07-23 9:53 ` revcomninos
2021-07-27 0:56 ` Ethan Gardener
2021-07-27 6:34 ` revcomninos
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=CAOw7k5h1Mbz2KuEF01rY4N+fbHV-3bEuER9SfPm2a0EMtJghWQ@mail.gmail.com \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
/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).