News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

The 16 November 2013 build (9455) is out.

Started by killerbot, November 16, 2013, 07:59:18 PM

Previous topic - Next topic

ToApolytoXaos

Question: Why after I close a project from C::B, then close C::B itself, and reopen it each file's end-of-line mode converts to Windows? That's happening only under GNU / Linux :/

oBFusCATed

Can you describe the exact steps needed to reproduce this with a hello world project?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

ToApolytoXaos

Yeah, just create a simple project, add a file naming it main.c or main.cpp, add some code in it, compile it, run it, save / close the project, then close codeblocks, reopen it and see the balloon tip at bottom right corner saying about opening different line ending.

oBFusCATed

This tooltip warns you that the file has mixed EOLs.
Can you enable the visibility of the EOL characters and to check what is the default style, and on which lines the EOLs differ.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

ToApolytoXaos

Indeed with C header / source files the header name includes UNIX end of line, whereas the body and the C++ files are using Windows end of line.

In settings / editor is set to auto.

oBFusCATed

Are the line with wrong EOL typed by you or are they autogenerated by a wizard (file or project)?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

ToApolytoXaos

#51
Quote from: oBFusCATed on November 29, 2013, 08:35:22 PM
Are the line with wrong EOL typed by you or are they autogenerated by a wizard (file or project)?
I don't mess with EOL at all; it's the wizard's job to handle such things. Also, I went to Tweaks and changed the EOL and upon close and reopen the file, it still holds the old EOL :/

oBFusCATed

Set "Ensure consistent EOL" in the editor settings and you're ready to go.
Probably the wizards doesn't change the EOLs for template files.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

stahta01

#53
Windows NON PCH (Precompiled Header) build issue.

I am testing some rarely built projects for wxWidgets 3.0 issues and got error building ModPoller Optional Plugin.

Tim S.


Index: src/plugins/modpoller/ModPoller.h
===================================================================
--- src/plugins/modpoller/ModPoller.h (revision 9479)
+++ src/plugins/modpoller/ModPoller.h (working copy)
@@ -13,6 +13,7 @@
#endif

#include <cbplugin.h>
+#include <editormanager.h>

class ModPoller : public cbPlugin
{
C Programmer working to learn more about C++.
On Windows 10 64 bit and Windows 11 64 bit.
--
When in doubt, read the CB WiKi FAQ. [url="http://wiki.codeblocks.org"]http://wiki.codeblocks.org[/url]

oBFusCATed

(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

ToApolytoXaos

Quote from: oBFusCATed on November 29, 2013, 09:35:32 PM
Set "Ensure consistent EOL" in the editor settings and you're ready to go.
Probably the wizards doesn't change the EOLs for template files.
Done so; the issue remains the same. Oh well, I will try to ignore it then, unless it becomes really annoying.

oBFusCATed

You have to change the file in order for the "ensure eol" logic to trigger. It won't fix all files in the project.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

dirk_1980

#57
Hi,

maybe it is a bug or i have forgotten to turn something on.

After i have made a update i have seen this, maybe it was the same in the last version i used


If i write code like:
#define TEST
#ifdef TEST
....   // this code is not active in the Editor (wrong colour)
#endif

If i write this:
#define TEST 1
#if (TEST == 1)
....   // this code is active in the Editor (right colour)
#endif

Is it a Bug or is it my mistake?
Dirk

oBFusCATed

Works for me with both variants. Are you using this nightly build?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

dirk_1980