[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ugly @predefined sections in PDF
From: |
Werner LEMBERG |
Subject: |
Re: ugly @predefined sections in PDF |
Date: |
Wed, 19 Nov 2008 15:48:06 +0100 (CET) |
> There are only a couple of instances where this looks particularly
> bad. Could we instead change just those instances so each of
> predefined commands is on a separate line? Is this possible? It
> would certainly be easier!
It's not clear to me why this would be `easier'. Assume that later on
a new command is inserted or removed. The editor would have to check
the PDF output whether the result is fine. In case I use @predefined
... @endpredefined, the result is *always* fine.
In general, I prefer a generic solution to a specific one, given that
in this particular case it's really easy to do -- inserting a couple
of @endpredefined doesn't hurt IMHO, and macros without arguments are
always expanded fine with any of the texinfo-to-something translators.
But maybe it's just me who thinks along this direction, so please
comment.
Werner
- ugly @predefined sections in PDF, Werner LEMBERG, 2008/11/19
- Re: ugly @predefined sections in PDF, Trevor Daniels, 2008/11/19
- Re: ugly @predefined sections in PDF,
Werner LEMBERG <=
- Re: ugly @predefined sections in PDF, Trevor Daniels, 2008/11/19
- Re: ugly @predefined sections in PDF, Till Rettig, 2008/11/19
- Re: ugly @predefined sections in PDF, Trevor Daniels, 2008/11/19
- Re: ugly @predefined sections in PDF, Jonathan Kulp, 2008/11/19
- Re: ugly @predefined sections in PDF, Till Rettig, 2008/11/19
- Re: ugly @predefined sections in PDF, Werner LEMBERG, 2008/11/19
- Re: ugly @predefined sections in PDF, Trevor Daniels, 2008/11/20