TextPad doesn't seem to honor Unix file endings only

Raven · Post by **Raven** » Wed Nov 08, 2006 8:24 pm

I have all my configurations set for Unix files. Yet, no matter what I try, TP always adds an extra line at the bottom of the file. What's the trick to making it work correctly?

Post by **MudGuard** » Wed Nov 08, 2006 9:55 pm

Configure - Preferences - Editor

Uncheck "Automatically terminate the last line of the file"

Raven · Post by **Raven** » Sun Nov 12, 2006 5:21 pm

Perfect! Thanks!

ben_josephs · Post by **ben_josephs** » Sun Nov 12, 2006 7:18 pm

I don't understand your requirement. The subject of your post is TextPad doesn't seem to honor Unix file endings only. In Unix systems all records of a text file must end with a new line character; so a non-empty text file must end with a new line character. Many Unix applications require this and will not perform as the user intended if they are presented with a text file that ends with an unterminated record.

Raven · Post by **Raven** » Sun Nov 12, 2006 8:03 pm

My requirements are as I stated. The applications I work with do not require the new line. In fact some of the text files that have new lines will cause the php applications to fail.

crackwitz · Post by **crackwitz** » Sun Nov 19, 2006 3:42 am

then your php "application" is broken.

each line is to be terminated with \n (unix) or \r (mac) or \r\n (windows).

and terminating a line properly has nothing to do with "unix file endings". i know of compilers that bitch if you have your last line unterminated...

your original post sounded like you thought that "unix file ending" meant "last line not terminated by \n"... so that is probably what confused some of us.

Raven · Post by **Raven** » Sun Nov 19, 2006 6:21 am

crackwitz wrote:then your php "application" is broken.

each line is to be terminated with \n (unix) or \r (mac) or \r\n (windows).

and terminating a line properly has nothing to do with "unix file endings". i know of compilers that bitch if you have your last line unterminated...

your original post sounded like you thought that "unix file ending" meant "last line not terminated by \n"... so that is probably what confused some of us.

After responding on the 12th that my original issue was resolved, I would have thought this was done. Regardless of what you think, the PHP application is not broken. To make such a statement is ludicrous. My circumstances and environment require no empty lines or spaces after the closing ?>. Period - EOL.