Re: Multiline editing breaks if the previous output doesn't end in newli
From:
Alex fxmbsw7 Ratchev
Subject:
Re: Multiline editing breaks if the previous output doesn't end in newline
Date:
Sun, 30 Oct 2022 22:40:42 +0100
On Sun, Oct 30, 2022, 21:21 Albert Vaca Cintora <albertvaka@gmail.com>
wrote:
> On Sun, Oct 30, 2022 at 7:54 AM Martin D Kealey <martin@kurahaupo.gen.nz>
> wrote:
> >
> > This sounds like a bug in whatever is producing the output. POSIX text
> files have a newline terminating every line; that description includes
> streams going through pipes and tty devices if they purport to be text.
> >
>
> There are many reasons why one could end up with text in a terminal
> that doesn't end in a newline. A couple of them are:
> - An app is killed in the middle of writing its output (eg: because of
> a sigterm/sigkill).
> - A file that isn't a POSIX text file is printed to the terminal.
>
> So I think this should still be handled by bash.
>
i coded a files tree to bash code via gawk reading and printing bash code
i did noeol no newline at end
logically , cause , who wants var='from file\n'
>