Possible workaround: pre-filtering input with s/\t/ /gseems like the right thing. I can't imagine anyone expecting TAB to actually do anything else in this context (especially since whatever it might be won't work in regular browsers anyway).
In reply to Re^3: CB bug: cutting off text after TAB
by wrog
in thread CB bug: cutting off text after TAB
by LanX
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |