doc words with
doc words like
newlines in sourcefiles
browsing around in the code, I noticed that most files have inconsistent line endings. In other words, a lot of files contain both CRLF and LF (windows and unix style) line endings.
This is pretty annoying, since at least vim reads the file as a unix style file, so all the "CR" characters show up as "^M" (this would not be a problem when only CRLF is used).
Anyway, is anyone aware of this problem and could it perhaps be fixed? It would recommend using unix endings, since most webservers use that format.
Sorry, i am using UltaEdit did not know about this problem. I guess i should build a script for converting them all to unix line endings on delivery (nice job for the script that takes care of the copyright messages).
I im kind of busy right now, i don't think i will create a new delivery any time soon to resolve this issue.
Sorry for the inconvenience.
> Sorry, i am using UltaEdit did not know about this problem. I
> guess i should build a script for converting them all to unix
> line endings on delivery (nice job for the script that takes
> care of the copyright messages).
I think the problem is not ultra-edit, but the fact that you work on the unreleased files :-)
AFAICS, the problem files are CRLF (Windows) files, except for the copyright lines at the top (which are LF). A few files are fully LF. This means that the unreleased files you work with are OK, but inserting the unix-style copyright header breaks it. So, it would probably be enough to just convert all the files to unix line endings once and tell your ultraedit to save as unix by default? Also, do you use any version control system? I know that subversion can take care of line endings automatically, for example.
Add a Reply
Loading form, please wait
The website will not send you an e-mail when a reply is added to this topic
Back to Topics List