Opened 12 years ago

Last modified 8 years ago

#112 new defect

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

Reported by: geofft@mit.edu Owned by: nelhage@mit.edu
Priority: minor Milestone:
Component: ui Keywords:
Cc: jgross@mit.edu

Description

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).

Change History (4)

comment:1 follow-up: Changed 10 years ago by jgross@mit.edu

  • Cc jgross@mit.edu added

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.

comment:2 in reply to: ↑ 1 Changed 10 years ago by 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.

comment:3 Changed 8 years ago by adehnert@mit.edu

  • Component changed from internals to ui

comment:4 Changed 8 years ago by adehnert@mit.edu

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

Note: See TracTickets for help on using tickets.