User forums > Using Code::Blocks

Custom make commands are never executed

<< < (5/7) > >>

kriegaex:
LC_ALL=C should always work (but do not take it for granted, I am not an expert there).

As for annoying dialogues, usually it works like this: They are shown, have a message and an additional checkbox, saying "don't annoy me again". So the user is free to choose is she likes to be reminded or not. Usually somehwre in the menu you can reset the warning dialogues so they are shown again.

MortenMacFly:

--- Quote from: jens on March 12, 2012, 12:10:30 pm ---But I don't know how reliable this function works.

--- End quote ---
Well shouldn't we simply assume it works reliable? What other options do we have? I don't want to implement another I18N... ;-) I like the idea and would do it this way.


--- Quote from: kriegaex on March 12, 2012, 12:51:38 pm ---As for annoying dialogues, usually it works like this: [...]

--- End quote ---
C::B's annoying dialog already works like that. We just need to add the two-liner to show it, if needed.

thomas:

--- Quote ---C::B's annoying dialog already works like that. We just need to add the two-liner to show it, if needed.

--- End quote ---
No need, this has been in preferences (under environment) for years.

As for localization, I don't think we should be doing anything. No matter what angle you look at it, localization is a lot of shit, both in general and in particular. It goes far beyond replacing "Warning" with "Warnung".
In the light of the trouble involved, I think it's acceptable to expect a developer to run the compiler without localization. It's what 100% of the German developers in the dev team do too, as far as I know :)

MortenMacFly:

--- Quote from: thomas on March 12, 2012, 09:08:49 pm ---
--- Quote ---C::B's annoying dialog already works like that. We just need to add the two-liner to show it, if needed.

--- End quote ---
No need, this has been in preferences (under environment) for years.

--- End quote ---
What has been there? That you get a warning when you issue C::B under a localised environment? I don't think so. The idea here is, that in the case you run C::B under "de_DE" or alike you get an initial warning (i.e. at first startup) that using a localised compiler - which is likely in that case - may screw the regexes / output parsing. We don't have that under "environment", do we?!

The only issue I see is that of course this only applies to compiler actually using localisation and where you actually can disable it. If I think about VC (for example) this is not the case. So the warning should say something like:
"Be aware that using a locale other than neutral / English might break the compiler output parsing of Code::Blocks build system. Either you switch your locale to English, or you need to adjust the RegEx parsing in the advanced compiler options, if needed. This might not apply to compilers other than GCC."

kriegaex:

--- Quote from: MortenMacFly on March 12, 2012, 01:36:58 pm ---C::B's annoying dialog already works like that.
--- End quote ---

I know, this is why I quoted it. I thought the chance to get it this way would be good because the effort would probably be small. ;-)


--- Quote from: thomas ---No matter what angle you look at it, localization is a lot of shit, both in general and in particular.
--- End quote ---

I translate this to "localisation should be done right and is a lot of work". Then I agree. If you do think it is a lot of shit, I strongly disagree. Even though I am fluent in English and have no problem using C::B in English (if it works out of the box in a localised environment, that is), I think localisation is helpful and I enjoy using software in my mother tongue. So do a billion or so other people. Software is made for users, not for the developers who build it (only if the developers care to be the only users). And users run software in the context of a (possibly localised) OS. Not doing localisation because of scarce development resources and other priorities is okay, but not doing it because of an attitude like "it is a lot of shit" is just being lazy and snobby. So as I said, thomas, I guess you probably meant "hard to do" or "a lot of work".

Navigation

[0] Message Index

[#] Next page

[*] Previous page