save/copy messages in message window?

[takeshimiya]

Everything is right as is now.

What could be improved is put a checkbox or an item in the contextual menu for changing enable full command-line logging.
I tend to change it from time to time (I try to have always disabled, but for some testings, ie. testing if the compiler is setup ok, or if backticks are expanding correctly, I enable it), so a setting for doing this more accesible would be great.

[mandrav]

But if you give them the ability to copy the beautified messages, then people will really do so.
As people post "Compiling foo.cpp" now when asking for help building something, they will now post beautified error messages. I don't think that is any good.

OK, I see the fault in your thinking: you only think about us and the support we offer in these boards.
But, please, stop for a while and think of a feature as exactly that: a feature, something that boosts productivity (at least for those who need it). When we add a feature, we don't add it for us but for the users.
If we were to think only about ourselves, most of current C::B features would not have been implemented unless we really needed them. Does this sound nice to you?

Regarding the specific feature discussed here:
When you tell a user to post his "build log", you expect he does that. If he posts the "build messages" then you have every right not to help him any further, if you don't feel the need to clarify. He doesn't deserve our help if he fails to do what he was asked to do. It's as simple as that.
Hence, I see no reason for this debate to continue...

[mandrav]

i would propose to set "full comandline logging" as default setting anyways

There's a reason for the default setting being "simple logging": It helps new users (mostly newbies) and makes C::B look a little more user-friendly. Believe it or not, long command-lines can intimidate new users (if they 're coming from the windows land). We don't want that.
And most importantly: it's a setting you can easily change once and never have to worry about it anymore.

[tiwag]

i would propose to set "full comandline logging" as default setting anyways

There's a reason for the default setting being "simple logging": It helps new users (mostly newbies) and makes C::B look a little more user-friendly. Believe it or not, long command-lines can intimidate new users (if they 're coming from the windows land). We don't want that.
And most importantly: it's a setting you can easily change once and never have to worry about it anymore.

ok i understand your preference,

now to something completely different ... 
would you accept a third logging option,
which sends short build messages to the build-log by default,
and only if an error has occured the complete compiler or linker commandline ?

if you'd accept such an option, i would implement it.

[takeshimiya]

OK, I see the fault in your thinking: you only think about us and the support we offer in these boards.
But, please, stop for a while and think of a feature as exactly that: a feature, something that boosts productivity (at least for those who need it). When we add a feature, we don't add it for us but for the users.
If we were to think only about ourselves, most of current C::B features would not have been implemented unless we really needed them. Does this sound nice to you?

Little off-topic, but that's a perfect description of thomas attitude. It's like more inclined of a customer-client thinking instead of a community thinking.

I've noted this to you before, thomas, on a personal message which you never replied. I really don't like when you say everytime to the people here "no this, no that".

Instead you could said 'I' will not do that, or something less dissapointing than a simple 'no', like "you 'll have to wait until we close most bugs and after other imporant things". That keeps people with hopes and a smile, at least.

[Michael]

Well, it is possible since revision 2312.

Sorry, but how?

I have built C::B rev2312 both in Windows and in Linux (Ubuntu 5.10), but I do not have a context menu in the "Build messages" tab. Should I do something special to activate this menu?

Thank you.

Best wishes,
Michael

[mandrav]

Well, it is possible since revision 2312.

Sorry, but how?

I have built C::B rev2312 both in Windows and in Linux (Ubuntu 5.10), but I do not have a context menu in the "Build messages" tab. Should I do something special to activate this menu?

Thank you.

Best wishes,
Michael

Not "on" the tab, but "in" the messages list

[tiwag]

Well, it is possible since revision 2312.

Sorry, but how?

I have built C::B rev2312 both in Windows and in Linux (Ubuntu 5.10), but I do not have a context menu in the "Build messages" tab. Should I do something special to activate this menu?

Thank you.

Best wishes,
Michael

Not "on" the tab, but "in" the messages list

it doesn't work for me too ( be sure i tried also ""in" the messages list" ) 

[Michael]

Not "on" the tab, but "in" the messages list

Yes, I have tried both on the tab and on the messages list, but without result.

Best wishes,
Michael

[thomas]

Little off-topic, but that's a perfect description of thomas attitude.

Actually it is a misunderstanding of my intent, but never mind that.

I've noted this to you before, thomas, on a personal message which you never replied. I really don't like when you say everytime to the people here "no this, no that".

In fact, you are the only person who regularly gets to hear "No" without further comment from me. And it will stay like that.
I could explain why that is so, but honestly, I am not willing to spend the time for that, for it is in vain. Actually I did not intend to answer to this post either, but was convinced to do so anyway.

[takeshimiya]

I've noted this to you before, thomas, on a personal message which you never replied. I really don't like when you say everytime to the people here "no this, no that".

In fact, you are the only person who regularly gets to hear "No" without further comment from me. And it will stay like that.
I could explain why that is so, but honestly, I am not willing to spend the time for that, for it is in vain.
Actually I did not intend to answer to this post either, but was convinced to do so anyway.

I don't have any problems with that personally, note that I was talking about other persons, not me.
Agree to disagree?

[mandrav]

Not "on" the tab, but "in" the messages list

Yes, I have tried both on the tab and on the messages list, but without result.

Best wishes,
Michael

Hmm, seems I forgot to commit? :lol:

[Michael]

Not "on" the tab, but "in" the messages list

Yes, I have tried both on the tab and on the messages list, but without result.

Best wishes,
Michael

Hmm, seems I forgot to commit? :lol:

Ah, ok :lol:.

Best wishes,
Michael

[tiwag]

Not "on" the tab, but "in" the messages list

Yes, I have tried both on the tab and on the messages list, but without result.

Best wishes,
Michael

Hmm, seems I forgot to commit? :lol:

no you didn't forget 

the problem is, that there is some interaction with the DragScroll V0.19 plugin,
when i deactivate the DragScroll plugin i get the Message-log's Popupmenu too.

[Pecan]

the problem is, that there is some interaction with the DragScroll V0.19 plugin,
when i deactivate the DragScroll plugin i get the Message-log's Popupmenu too.

Wups! I'll have a look at this and fix it.
Are we talking about Windows or Linux?

thanks
pecan