User forums > Nightly builds
The 16 June 2013 build (9158) is out.
ToApolytoXaos:
--- Quote from: MortenMacFly on June 18, 2013, 08:12:21 pm ---
--- Quote from: ToApolytoXaos on June 18, 2013, 01:31:02 am ---it remains highlighted until to enter semicolon at the end of your current line, or use the arrows to interrupt it.
--- End quote ---
What platform, btw? I cannot reproduce on Windows, at least. I've used exactly the code you have shown...?!
--- End quote ---
On Debian testing with latest updates MortenMacFly.
ToApolytoXaos:
--- Quote from: jens on June 18, 2013, 10:11:15 pm ---To reproduce:
* "Brace completion" checked in the settings.
* In the editor type printf( followed by ".
* You get printf("|") (the pipe-symbol is the caret's place).
* The right quote and the right parenthesis are green highlighted.
* Type another " .
* Now you get printf(""|) .
* All characters you type now are also green highlighted until you type (e.g.) another quote or a right parenthesis
--- End quote ---
Actually, to reproduce it, try to use printf() as you have shown on third point, but instead of typing another double quote, use your right arrow to move your cursor next to right quote, add a comma to add your variable parameter and see the green highlight persisting to continue.
NOTE: You can try the same with std::cout << ("") and as soon as you use right arrow and enter comma next to double quote, it does exactly the same.
Jenna:
svn r9078 seems to be the first bad revision ("* SDK: major update to core component wxScintilla: Pumped underlying scintilla to v3.3.1").
ToApolytoXaos:
OK, the svn9161 that I have currently compiled produces the same issue.
When you run the updates, can you please tell me which plugin or part of project should I compile within C::B, so I could save a bit of CPU cycles and unnecessary energy?
Another thing is that when I run C::B within terminal without & at its end, I can see how parser works and works pretty fast, actually faster than loading the IDE from "run" command and use it accordingly. Usually with the latter option, most of the times parser would hang and force me to reparse the entire project which is a bit of annoying.
Is there a reason for such behavior?
ollydbg:
--- Quote from: LETARTARE on June 18, 2013, 05:41:30 pm ---I found some possible improvements:
--- End quote ---
Thanks for the contribution, as some devs said before, we need patch files.
--- Quote ---1- FILES WITHOUT TARGETS
'CC Test' : 'src\plugins\codecompletion\'
- 'cctest\test.h'
--- End quote ---
I think this is by design, E.g. some code snippet cause our Parser hang. To debug this kind of issue, we use a CCTest project, and you just simply copy the code snippet to "test.h", and let the CCTest app to parse it. Now, if "test.h" cause Parser hang issue, then we even can't open CCTest correctly.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version