> [...] but live in fear that I have accidentally overridden
> some tremendously important macro in a package that I am
> about to use.
You can guard yourself against accidentally overwriting
existing macros by building a wrapper around "de" which
tests whether the name to be defined already exis
On 04/02/10 20:16:48, Tadziu Hoffmann wrote:
> > [...] but live in fear that I have accidentally overridden
> > some tremendously important macro in a package that I am
> > about to use.
>
> You can guard yourself against accidentally overwriting
> existing macros by building a wrapper around "de"
> Of course, that is a pretty drastic solution -- definitely
> a case of throwing the baby out with the bath water. :-)
Well, if you know the name might already exist and you want
to overwrite it anyway, then make this clear by using ".de!"
instead of ".de".
Joachim Walsdorff wrote:
thanks for spending your time to improve hdtbl. It's a good idea to
seperate hdtbl- and example stuff into hdmisc.tmac respectively
common.roff. But some little things now seem to be wrong.
1) In fonts_x.in und fonts_n.in:
.so examples/common.roff
is missing.
Fix
>> I would support making tbl warnings optional, to be in line with
>> troff, and other reasons, for example if a table is deliberately
>> wider than the line width. A new flag -w to enable warnings?
>
> I was thinking maybe a global option like "nowarn" -- the warnings
> are generally useful, bu
> warning: around line 35: table wider than line width
> warning: around line 35: table squeezed horizontally to fit line length
> warning: around line 367: table wider than line width
> warning: around line 367: column separation set to zero
>
> I've included a patch to include the file name in
> In trying to get "IMG" and "PIMG" to function, I noted that the
> macro definitions seemed to have the arguments confused when
> interpreting the width and height arguments. [...]
Thanks for the report. It would help me tremendously if you could
provide failing minimal examples.
Werner
> I would support making tbl warnings optional, to be in line with
> troff, and other reasons, for example if a table is deliberately
> wider than the line width.
Then you should increase the line width temporarily.
Werner
> No macro, register, or string name within standard macro
> packages will ever end in * . Thus all user created names
> that end in * will never collide with any within the standard
> macro packages.
Nice idea. Have you already verified that no macro provided by any of
t
Mike Bianchi wrote:
On Wed, Feb 03, 2010 at 02:08:47PM -0500, Larry Kollar wrote:
:
This actually brings up something that has been bugging me for a
while,
and I think deserves its own thread: we should come up with some
namespace guidelines for macro packages, especially for intern
Werner LEMBERG wrote:
I was thinking maybe a global option like "nowarn" -- the warnings
are generally useful, but once a particular table has been debugged
you wouldn't want to hear from it again.
This should be quite easy to implement, and I would include it into
groff if someone (you?) is
11 matches
Mail list logo
