(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.
It *does* interpolate the string register value, but only
at *troff* runtime. (Well, actually it's not the .so
request that does the interpolation
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
On Tue, Aug 22, 2006 at 02:42:47PM +0100, Keith MARSHALL wrote:
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
Werner LEMBERG wrote:
just an idea: the problem would go away if the `.so' request could
be told (by a second argument to the request) to rerun all necessary
preprocessors on the sourced file before inserting it (the
preprocessors could be those specified in the groff call or
explicitely
(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.
Werner
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
On 18-Aug-06 Joerg van den Hoff wrote:
hi,
looking at the docs and the archives I did'nt find this:
if there are preprocessor directives in a sourced file and
the file name is specified in a string register in the
document errors result.
say I have to files `t2' and `t3' which are to be
(Ted Harding) wrote:
On 18-Aug-06 Joerg van den Hoff wrote:
hi,
looking at the docs and the archives I did'nt find this:
if there are preprocessor directives in a sourced file and
the file name is specified in a string register in the
document errors result.
say I have to files `t2' and `t3'
On 18-Aug-06 Joerg van den Hoff wrote:
[...]
Ted,
it does, thanks a lot. I see the problem now: `soelim' (which
is the first preprocessor called anyway) silently ignores the
`.so' request including the string register and that's why the
`.so' survives until troff gets into gear after the
I have sometimes (slightly mad idea ... ) considered (at
least experimentally) re-writing relevant macros such as
.PS/.PE, .TS/.TE, .EQ/.EN so that they automatically
write out what occurs between the start and end to a file,
run the appropriate preprocessor program on the file,
and read
just an idea: the problem would go away if the `.so' request could
be told (by a second argument to the request) to rerun all necessary
preprocessors on the sourced file before inserting it (the
preprocessors could be those specified in the groff call or
explicitely specified to the `.so'
10 matches
Mail list logo
