>> > OPTS_WITH_ARG=`echo $OPTS \
>> > | sed "s/[$OPTS_NO_ARG:]//g"`
>>
>
> There is no reason to get the `groff' options in the
> configuration. So I used again
> `/src/roff/groff/Makefile.sub'.
[I've sent you a separate mail why `:=' and `$(shell ...)' should be
avoided in groff Makefiles.]
>
> > Von: "Werner LEMBERG"
> >
> > > OPTS=`grep ':.*:.*:' groff.cpp \
> > > | sed -e 's/[",]//g'`
> > > OPTS_NO_ARG=`echo $OPTS \
> > > | sed -e 's/[a-zA-Z]://g'`
> > > OPTS_WITH_ARG=`echo $OPTS \
> > > | sed "s/[$BAR:]//g"`
> >
> > Oops! The last two lines should be rather
> >
> > OPTS_WITH_ARG=`e
Hi James,
> At first I tried
>
> ticks at copy "t"
>
> which didn't work
No, `copy' is a top-level command, just like `ticks'. It can't appear
anywhere you'd like t's input; it's not part of a separate
preprocessor, for instance.
> Now I finally understand something that, to me at lea
On Sat, 27 Apr 2013 11:19:01 +0100
Ralph Corderoy wrote:
> > I tried many variations of
> >
> > ticks sh { awk ... }
> >
> > without any luck.
>
> Use `sh' to produce the whole `ticks' line in a temporary file and
> then `copy' to read it in?
Ah, thanks, Ralph!
At first I tried
Hi Doug,
> Is there a tool or trick for getting encapsulated postscript from pic?
> What I want is that the bounding box should have origin 0 0 and be
> just big enough to cover the picture.
As James wrote, I'd use ps2epsi(1) from GhostScript. Moving to (0, 0)
in troff helps with the bounding bo
Hi James,
> Is there's a cool way to pass "sh" output to grap's ticks command?
>
> I'd like to generate my x-axis "ticks" programatically, from the
> data I'm bringing in with "copy". I have a line like this:
>
> ticks bottom out at 6.4000e+01 "\s-1%.0f", 9.05096680e+01 "%.0f", \
> 1.2800
Hi James,
> While I'm in the neighborhood, the grap manual says that labels stack,
> but mine (version 1.41) doesn't seem to:
>
> $ cat t
> .G1
> label top "abc", "def"
> .G2
>
> $ grap t
> grap: syntax error
> Error near line 2, file "t"
> context is:
> label top "abc" >>> , <<< "def"
