Shell Programming and Scripting

If you check that c.sh exists an is not empty and tail -1 c.sh| wc -l returns 0

then this file meet the condition you are looking for.
So checking for zero is not sufficient but if brought with a test -s then it should work doesn't it ?
At least, that was what i wanted to point out in my previous post.

The files can be zero or non-zero size.

"ALL i want is a single line command that will print all filenames in the current directory along with the file last line where the file doesn't end with a newline"

A tested working solution as answer will be appreciated

Files with the last newline character missing are not proper UNIX format. Awk just processes such a file as if the file did have a closing newline. So inside an awk script it cannot be detected whether or not it was present in the file..

You would need to use another way to detect whether it is present, or just convert all files to proper format, for example:

Code:

awk 1 file > newfile

GNU sed or BSD sed could use in-place editing, something like:

Code:

sed -i'.bak' '' file

--
Alister is right though, that does not work with POSIX awk or nawk on Solaris and HPUX for example. That page does not include an example where $0 is used in the END section BTW..

I believe what you should expect from this forum is proposals, suggestions, and consultancy so you can come up with a solution yourself AND test it by yourself. Anything beyond that is nice but not a given.
However . . . -- this is a proposal that works on my linux box BUT it does not cope with empty files. Please feel free to use and test it or dump it...

Code:

for i in *.sh; do  [ '0a' != $(od -An -tx1 -j$(( $(stat -c%s $i) - 1 )) $i) ] && { echo -ne $i"\t"; tail -n1 $i; } done
a.sh    apple$

The $ sign is the next command prompt as no newline char is output - as requested.

Yes, it does. Look for Print the last line of a file (emulates "tail -1") 2/3 down the page.
awk.info Handy One Liners

As has already been pointed out, any attempt to process an incomplete line at the end of a file with awk may or may not work. The standards say that tail (when using options that count lines), grep, and sed as well as awk produce unspecified results if the input files they process are not text files. (And, by definition, a non-empty text file's last character is a <newline>.)

A side note on the discussion about $0 in END actions in awk: The standards are silent about whether $0, $1, ... $NF are valid in END actions. However they require that FILENAME, FNR, and NR have the values they had for the last line read when used in END actions. They also require that:
Since NF has to be preserved, I don't see why $0 through $NF woudn't also be preserved under the same conditions; but the standards don't require awk to do so.

Rudi has given you a script that will work on some systems, but it won't work on OS X, Solaris, or several other UNIX and UNIX-like systems.

The following script doesn't use anything that isn't specified by the standards, so it should work on almost any system. It was tested using ksh, but should work for any POSIX conforming shell.

This script will tell you if a file is missing the terminating <newlin>, but it does not attempt to print the incomplete line. Although I could do that in a shell script, if I had a REAL need to portably print incomplete lines, I'd do it in C; not shell.

Code:

for i in *.sh
do
        if [ ! -e "$i" ] || [ ! -r "$i" ]
        then    printf "%s: not a readable regular file\n" "$i"
        elif [ ! -s "$i" ]
        then    printf "%s: empty file\n" "$i"
        else    # Use 012 below for ASCII, 045 for EBCDIC
                if ! tail -c -1 "$i" | od -b | grep -Fq ' 012'
                then    printf "%s: missing <newline>\n" "$i"
                fi
        fi
done

OK you're right, my bad.. So yes the example on that page is incorrect, in the sense that it will not work with every awk..