David Faure wrote:
> IMHO text editors should (and most do) just ensure a newline is present at
> the end so that this all works without human intervention.
Well, there are cases where you don't want your editor to mess with existing
files that way. The right thing to do is to make this feature a
In unix context that probably makes sense for comparability. Especially for
commandline tools. In any event I use vscode which can silently and this.
Give that it must be there it makes sense to just have it happen on its
own. I already do this with code formatting. Its nice not to have to
constant
"cat file1.cpp file2.cpp > file3.cpp" will be broken in the contexts in which
you don't support that file1.cpp should end with a newline.
IMHO text editors should (and most do) just ensure a newline is present at the
end so that this all works without human intervention.
David.
On lundi 10 déc
Thanks for the reply in my view not treating endof file as newline is a
flaw in the standard itself. But that's not my call for a kde app. I will
not be supporting this outside kde context with regard to source files.
On Mon, Dec 10, 2018, 6:30 AM Boudhayan Gupta Hi Michael,
>
> In Unix, text fil
Hi Michael,
In Unix, text files are defined as a file containing *lines* of text [1].
Necessarily, this means that a character is required to signify the end of
line, which just happens to be the '\n' character.
Practically, this means certain Unix utilities, (although the GNU ones are
smart abou
Why is krazy still checking for newlines at the end of files? Modern tools
don't seem to get tripped up by this.
http://ebn.kde.org/krazy/reports/kdereview/kdiff3/src/index.html
