Mike Bianchi wrote:
>>> (it just would be nice if the `.so' request _could_ interpolate the
>>> string register value)
>>
>> Indeed, but I don't see how to do that properly.
>
> Maybe soelim(1) could recognize that the argument is not a file name
> ( \ being a dead giveaway ) and simply leave the reference in place for
> interpretation by groff?
This is exactly what happens, at present.
> As long at the referenced file does not require preprocessor
> interpolation ...
...in which case, `soelim' isn't really required, in the first place; it
doesn't become necessary, until you have content in a `.so'd file, which
*does* require interpretation by a preprocessor.
> And maybe have groff recognize a special form of .so :
>
> .so filename [ preprocessor_command_line ]
>
> .e.g.
> .ds filename FILENAME
> .so \*[filename] "tbl - | eqn -"
> implies
> cat FILENAME | tbl - | eqn -
> or equivalently
> <FILENAME tbl - | eqn -
May appear attractive, at first glance, but still inevitably suffers
from the limitations Tadziu mentioned -- each `.so' so deferred is
processed in isolation, and normally global declarations such as
.EQ
delim ##
.EN
don't propagate as expected.
Regards,
Keith.
_______________________________________________
Groff mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/groff
