From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <aca3641bbc421285e43c25cfd7b694b5@proxima.alt.za>
References: <CAOEdRO2soYHKPwoHWvgC1mXauiDwiX04LF575SXARUVCCa4JgQ@mail.gmail.com>
	<aca3641bbc421285e43c25cfd7b694b5@proxima.alt.za>
Date: Wed, 12 Aug 2015 16:22:19 +0200
Message-ID: <CAOEdRO01ijZDkjaZXb+X=CARzhF+8ruFFi1jYCoZBBp29M_4iw@mail.gmail.com>
From: Rudolf Sykora <rudolf.sykora@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [9fans] p9p sed vs linux sed
Topicbox-Message-UUID: 6684cfb8-ead9-11e9-9d60-3106f5b1d025

On 12 August 2015 at 15:47,  <lucio@proxima.alt.za> wrote:
> You can't write a file in vi that does not end in a newline.

You, however, can do it pretty easily with cat.
(Sam asks you if you mean it, acme just does it.)

> So, I vote that text handling utilities should deal with all lines in
> text files uniformly,even the last one.

I encountered the problem when I selected a couple of words in acme
which I wanted to bracket with sed with something like

| sed 's/^/</' | sed 's/$/>/'

and suddenly you see...

On the other hand, as you say, it's a matter of taste.
(If the behaviour is not prescribed.)

R Sykora