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.2800e+02 "%.0f", 1.810193
> 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 ra
> 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=`echo $OPTS \
>> I think a perl program is far too heavy to search these lines in
>> groff.cpp:
>>
>> while ((opt = getopt_long(
>> argc, argv,
>>
>> "abcCd:D:eEf:F:gGhiI:jkK:lL:m:M:n:No:pP:r:RsStT:UvVw:W:XzZ",
>> long_options, NULL))
>>
>> and to extrac
> Von: "Werner LEMBERG"
>
> >> > noarg: abceghijklpstvzCENRSUVXZ
> >> > witharg: FmTfwWMdrnoPDKLI
> >>
> >> Couldn't groffer parse `groff --help's output at run-time?
> >
> > That's what I've done so far. But that takes extra calling time.
> > As the `groff' options don't change after installati
>> > noarg: abceghijklpstvzCENRSUVXZ
>> > witharg: FmTfwWMdrnoPDKLI
>>
>> Couldn't groffer parse `groff --help's output at run-time?
>
> That's what I've done so far. But that takes extra calling time.
> As the `groff' options don't change after installation, it makes
> sense to make them availab
> Von: "Ralph Corderoy"
>
> > `grog' and `groffer' (maybe something else in the future) need the
> > information of the options used by `groff'.
>
> Out of curiosity, why? :-)
grog generates a commandline based on `groff', so it must be clear which
options are real.
groffer uses `grog' and ge
Hi Bernd,
> `grog' and `groffer' (maybe something else in the future) need the
> information of the options used by `groff'.
Out of curiosity, why? :-)
> The Perl program reads from `groff.cpp' the function `synopsis' that
> contains information of the `groff' options. From this there
> inform
I recently installed the groff extension in Tiny Core linux and ran into a
problem with fonts. Documents were fine with roman font, but italics and
bold requests were seemingly completely ignored. I suspect this is a problem
somewhere in the environment since the requisite files all seem to be in
Hi Bernd,
> Would it make sense to add `; \' to all internal lines in the not
> generated Makefiles?
Echoing Keith's "No" it would make sense to not have them unless they're
something like an if-statement or a change to the environment, e.g.
current working directory, is needed by later commands.
Hi maouinin,
> Everything went fine until I tried to change fonts ( nothing major--
> just bold and italics). The requests just seem to be
What happens? Your sentence doesn't seem to finish? Does groff produce
PostScript without complaining? Is it the viewing of that on the screen
where the fo
Tiny Core Linux is a minimal linux distribution that I have been using for
some time when I travel. I have it installed on a usb thumb drive, which I
take with me instead of a computer. I recently installed the groff extension
and started to do some work with that. Everything went fine until I tri
Tiny Core Linux is a minimal linux distribution that I have been using for
some time when I travel. I have it installed on a usb thumb drive, which I
take with me instead of a computer. I recently installed the groff extension
and started to do some work with that. Everything went fine until I tri
13 matches
Mail list logo
