User forums > General (but related to Code::Blocks)
Annoying CVS issue
mandrav:
Found it and fixed it.
A new editor option was added: "Ensure consistent EOL".
This used to be hardcoded to "true" by default and caused a EOL-conversion for the document when saved. Now it's a separate option, off by default, and works as expected :D
rickg22:
Hmmm... that's very interesting. Anyway this option enabled in Linux was what was causing the problem? (Now that i think of it, is it safe to have it in windows?)
mandrav:
--- Quote from: rickg22 on September 07, 2005, 08:50:13 pm ---Hmmm... that's very interesting. Anyway this option enabled in Linux was what was causing the problem? (Now that i think of it, is it safe to have it in windows?)
--- End quote ---
As I said, when saving the file it forced a conversion of EOLs. This caused the problems I have described...
I don't want to be forced anything by the editor, so I added the option. Simple as that :)
knue:
Hi, I am devloping a project on linux und windows and worked with the 1.0-RC1 version and had the same problems with EOLs. I assumed that this is a CB because I didnt have problems when using other editors. Now I am using a newer CVS-Verions which has the "ensure consistent EOL" options. But I am totally confused. Here my questions:
1. How does Window handle EOL?
2. What is the UNIX standard?
3. What does CVS with this?
4. How do I have to setup CB in win to handle that properly?
5. How do I have to setup CB in linux to handle that properly?
6. Is there a tool to convert EOLs so I can fix the "corrupt" files of my project?
Thx for replying
thomas:
1. \r\n (corrected by Rick)
2. \n
3. Insert \r before \n when converting from Linux to Windows, and stripping \r in the opposite case
4.+5. Ask Rick ;) But I believe you must DISABLE that option
6. unix2dos (comes with MinGW and is a standard tool under Linux)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version