Browse lookup

[Jay R. Ashworth]

On Wed, May 26, 2004 at 09:29:39PM -0400, Kenneth Brody wrote:
> GCC Consulting wrote:
> [...]
> > To see why this was happening, I checked the product master for this item.  What
> > I found was the in the description field, which is displayed in the browse, it
> > contained ...L\I CD.  The color change occurred at the L\I.
> > 
> > The other thing I found was that for other backslash combinations the backslash
> > was deleted from the display.
> >                 Tex\Trix
> >                 Tuf\Trix
> > 
> > Have any of you seen this?
> 
> How else could you embed backslash codes?
> 
> If you want to disable this handling within browse lookups, set the
> config variable PFBRWSLASH=OFF.

If I correctly understand all the pertinent data, I submit that this
constitutes the programmers of browse lookup confusing the requirement
to evaluate \ escapes in the *format*, with the extremely unlikely
event that someone would want such escapes in the data being
interpreted -- I don't believe that any *other* data display routines
interpret such escapes in the data they display; do they?

Cheers,
-- jra
-- 
Jay R. Ashworth                                                jra at baylink.com
Member of the Technical Staff     Baylink                             RFC 2100
The Suncoast Freenet         The Things I Think
Tampa Bay, Florida        http://baylink.pitas.com             +1 727 647 1274

        "They had engineers in my day, too."  -- Perry Vance Nelson