User forums > Help

Editor colors ... file?

<< < (2/2)

MortenMacFly:

--- Quote from: dmoore on July 23, 2007, 09:58:38 pm ---would it be possible to enumerate the entire configuration file as a tree so people can export arbitrary bits of it?

--- End quote ---
No, cb_share_config was designed to only copy mature parts that most likely will not result in errors if done so.

For what you want keep in mind that the config file is XML - any good XML sync tool can handle what you want.

With regards, Morten.

Ps.: For the colour_set bit... I'll see what I can do... ;-)
Edit: See r4301... -> Oh, we crossed 4300! *woot*

thomas:

--- Quote from: MortenMacFly on July 23, 2007, 09:50:58 pm ---a) it's not unsupported - ask me to add additional features
--- End quote ---
It is unsupported. The only supported thing that's allowed to modify config files is Code::Blocks.

Anything else is hacking, and unsupported, even if it works. If anything goes wrong, it's the user's problem alone. The same is true for editing the XML in a text editor. While this is certainly possible and will probably work just fine 99.9% of the time (yes, I've been doing it myself), it is not supported.

Regarding making a copy of the lexer files, this is certainly a possible approach. To me, either is the same, since I have never had the need to change a colour set, but I could imagine that there are as many people who prefer having just one file to copy for everything. To be honest, I have no idea which is "better", if any solution can be said better at all.
For now, I wouldn't touch colour sets, since it is not dearly necessary and whether or not one favours the present system, at least it works reliably.
The risk of "improving" something that works reliably to a point where it doesn't work any more *cough* *cough* is unfavourable if we ever plan to bring out a release. There are still enough things to fix that don't work, unluckily.

dmoore:

--- Quote from: thomas on July 24, 2007, 02:22:15 am ---Regarding making a copy of the lexer files, this is certainly a possible approach. To me, either is the same, since I have never had the need to change a colour set, but I could imagine that there are as many people who prefer having just one file to copy for everything. To be honest, I have no idea which is "better", if any solution can be said better at all.
--- End quote ---

with "mature" editors such as vim and emacs, people regularly exchange color sets. I would rather download someone's carefully thought out syntax highlighting than do the painstaking work myself. with that in mind, keeping the style info in separate files would be much easier to manage.


--- Quote ---For now, I wouldn't touch colour sets, since it is not dearly necessary and whether or not one favours the present system, at least it works reliably.

--- End quote ---

agree. another thing to add to the post 1.0 list.

MortenMacFly:

--- Quote from: thomas on July 24, 2007, 02:22:15 am ---
--- Quote from: MortenMacFly on July 23, 2007, 09:50:58 pm ---a) it's not unsupported - ask me to add additional features
--- End quote ---
It is unsupported. The only supported thing that's allowed to modify config files is Code::Blocks.

--- End quote ---
Well I thought using the very same API (the one of C::B itself) made it "supported". If you say that's not true it's unsupported then - I don't mind. Whatever you say, sir, I'll follow. I'm a Lemming. :lol:
With regards, Morten.

Navigation

[0] Message Index

[*] Previous page