Re: Problem with macros in displays

[Stepan Kasal]

Hello,

On Mon, Nov 29, 2004 at 02:56:08PM +0100, Laurence Finston wrote:
> On Mon, 29 Nov 2004, Stepan Kasal wrote:
> > yes, the @macro support is somewhat kludgy.  In specialized environments,
> > like @example, it tends to break.
> 
> Okay, then I'll just use some (slightly) low-level TeX code,
> if I can't get the macros to work they way I want.

I'm afraid it'll be the most feasible way.

> [...] The problem is lots of erroneous line breaks.
> However, they aren't just at the ends of input lines.

Oh, I see.  @macro reads the body with active ^^M (end-of-line char).
When you expand that in the \obeylines environment, they cause this.

But we have to preserve the end-of-lines in macro body, because many
macros have their paremeter delimited by it.

And the syntax of @macro definition doesn't allow for a body without
end-of-lines.  Argh...

As it stands, it is easiest to do it this way:

@macro foo {arg}
...
@end macro
@tex
\gdef\foo#1{...}
@end tex

> > @quotation doesn't change \parskip.
> 
> This is a quotation from the Texinfo manual:
>    * in the printed output, interparagraph spacing is reduced.

Oh, sorry.  Either I have missed something in texinfo.tex, or the manual
is wrong.  Karl, which end should be fixed?

> > Well, as far as your request ``make @macros work in @display's'' is
> > concerned, it's hard to accomplish and I beleive it's not the right way.

First: my formulation was rather harsh, sorry.
Second: it seems I was wronng, it would be the right way.

But I'm afraid it not easy to accomplish it.  The situation about @macro's
cause much frustration.

> > I believe that we have to pull the other end of the rope: what's wrong
> > with @quotation?
> 
> The text in question isn't a quotation, and I'd like it to be in a display.

OK, my suggestion was silly, sorry.

> What's the policy of these lists on attachments?
> I can attach a gzipped dvi file, if you want to see it.

I meand a short test file, which would produce only one or two pages of
output.  Such a file can be attached, perhaps together with the dvi file.

If you want to show the problem on a bigger manual, you should better
post an URL.

> I want to display the syntax rules for the 3DLDF language

I'd say that as texinfo doesn't have support for syntax rules, you have to
``extend'' the language in a kind.
As far as the dvi (ps) and pdf output are concerned, making a few
specialized TeX macros is probably the most straightforward way.

If your knowledge of plain TeX programing rusted, I'll be glad to advice.
But for real texinfo expertise, Karl is much better then I.

> By the way, which is the appropriate list for this discussion,
> `bug-texinfo' or `help-texinfo'?

I'm not sure.  Any of them perhaps.
When I wrote my previous answer, I set the reply-to field to help-texinfo,
but in this mail you pointed out actual bugs...

OK, this one is sent to bug-texinfo only.

Sorry,
        Stepan