Shell Programming and Scripting

Well I didn't know that a line HAS to contain a newline after it end... good to know either way.

Regarding "my output" like I stated:
It was due to being me misinterpreting the code I was shown on a 4" inch mobile device display... Looking at the output on a 17" Screen made me realize the "tab" issue.

thanks for this script. This thread is now resolved and can be closed.

By chance i saw that awk completes an incomplete last line.

Code:

awk 1 *.sh > ../final.sh

Some implementations of awk complete an incomplete line; others ignore any partial line. The standards only define the behavior of awk when the input files are text files. By definition, a text file that is not an empty file contains a <newline> character as the last character in the file.

You say there are awk versions that skip an incomplete line?
Most implementations of wc do so. But awk?

As I said before, the standards only specify the behavior of awk when its input files are text files. Text files have the following constraints:And I have seen awk implementations that ignore incomplete lines.

The wc utility, on the other hand, is defined to work on any file type; not just text files. If you look at the standards, wc -l prints a count of <newline> characters found in a file; not the number of lines in a file.

If we want to be really anal and follow the strict definition of a text file, it may or may not contain a terminator (NL/CR/LF) at the end.

Awk might think differently of course.

--
OFFTOPIC: I'm amazed by how many pages of discussion a simple "cat *" command can generate.