On Fri, Oct 19, 2007 at 07:53:28PM +0200, Andre Poenitz wrote:
> On Fri, Oct 19, 2007 at 08:28:35PM +0300, Martin Vermeer wrote:
> > On Fri, Oct 19, 2007 at 02:32:27PM +0200, Jean-Marc Lasgouttes wrote:
> > > Enrico Forestieri <[EMAIL PROTECTED]> writes:
> > >
> > > > Moreover, \index is fragile, so any fragile command appearing in its
> > > > argument must be protected. That is to say that
> > > >
> > > > \index{Bibliography ! Bib\TeX}
> > > >
> > > > doesn't work, but
> > > >
> > > > \index{Bibliography ! Bib\protect\TeX}
> > > >
> > > > does work.
> > >
> > > This is easy to fix, then.
> >
> > I actually played around with this. Yes, works in principle, but...
> >
> > > 1/ add protect to \TeX when needed.
> >
> > What does "when needed" mean concretely? I added \protect
> > unconditionally to the \LyX etc. definitions, and it works,
> > but is overkill. How would you do it?
>
> Just 'a bit of overkill' or 'overkill to a degree that it hurts us'?
I am confident that it has no performance implications
whatsoever... just two worries: 1) are there situations where
it is illegal? and 2) we know there are situations where it
isn't enough, like for URL, where we need a verbatim output
alternative anyway.
But I would like to see what Jean-Marc has in mind.
> In the first case I'd say just use \potect unconditionally.
>
> Andre'
- Martin
