Ledges Forum

[MichaelC]

hm... Listener makes sense I guess but as I said, I don't see a reason to change the terminology again?

[MichaelC]

Includes relevant discussion: https://gist.github.com/26dc674c0062f128c1ab

[callumacrae]

Could we please stop posting long IRC conversations? I doubt that I'm not the only one who doesn't have time to read through it all.

At the very least, a summary would be nice.

[igorw]

Could we please stop posting long IRC conversations? I doubt that I'm not the only one who doesn't have team to read through it all. At the very least, a summary would be nice.

+1

[A_Jelly_Doughnut]

Could we please stop posting long IRC conversations? I doubt that I'm not the only one who doesn't have time to read through it all.

+1 -- and/or post it somewhere other than gist that does word-wrapping (hello 1993 )

[callumacrae]

Could we please stop posting long IRC conversations? I doubt that I'm not the only one who doesn't have time to read through it all.

+1 -- and/or post it somewhere other than gist that does word-wrapping (hello 1993 )

It's designed for code, not conversations - code shouldn't be wrapped

[MichaelC]

Just press the raw button and it wraps it.

Anyway, I'll still post links but I'll make sure to add a summary in future.

[naderman]

One can also just post the log in a code tag right here. But indeed summaries help a lot.

[MichaelC]

One can also just post the log in a code tag right here. But indeed summaries help a lot.

For long logs it saves having lots of clutter in the topics.

[naderman]

That is really only made worse by posting links. If you think it's clutter, don't post it, not in link form either. Otherwise code tag doesn't get too long cause it collapses. Links require that you visit some extra page just to understand what is going on in the topic. It's really rather bad for reviewing a topic later if you find (potentially even broken) links to important parts of discussion that others refer to. Anyway back to the topic