don't render zephyr markup in non-zephyrs and non-bodies

[geofft@mit.edu]

If I send @b(foo) to myself in a Jabber message, or in a zephyr instance, it renders in bold as opposed to as a literal @b(foo).

[jgross@mit.edu]

Is this necessarily a defect? I've used this feature, e.g., to bold/underline something I sent from aim to a friend using aim over zephyr.

[andersk@mit.edu]

Replying to jgross@…:

Is this necessarily a defect? I've used this feature, e.g., to bold/underline something I sent from aim to a friend using aim over zephyr.

Uh, yes, this is necessarily a defect. If you want to send bold text using the AIM protocol, you should use the AIM protocol’s way to send bold text, and the recipient should decode it using the AIM protocol’s way to receive bold text. You should not make up a random other protocol and rely on the recipient supporting your random other protocol.

More importantly, this bug interferes with perfectly legitimate message containing @ characters used in certain ways.

alexmv / work / alexmv  16:28  (moose.)
    It's particularly bad when talking abotu de-referencing array
    references in perl:
    my @foo = @{ [ 1, 2, 3 ] };
          vs
    my @foo =  [ 1, 2, 3] ;
    ...is a big difference.

[adehnert@mit.edu]

It would be somewhat nice if the fix to this did not break using Alias to color classnames.