> Hence my question about whether there really is no way I could use a
> set of escapes instead of a request...
No, there is really no way to have a user-defined escape. If you want
that, please use TeX. :-)
Werner
Werner LEMBERG <[EMAIL PROTECTED]>, 2008-02-26 09:33 +0100:
> > Hence my question about whether there really is no way I could use a
> > set of escapes instead of a request...
>
> No, there is really no way to have a user-defined escape. If you want
> that, please use TeX. :-)
I'm not prepared
Tadziu Hoffmann <[EMAIL PROTECTED]>, 2008-02-25 10:36 +0100:
> > Is there a way I could modify it so that the filled box
> > extends all the way across the whole line length? (i.e.,
> > from the left margin / page offset to the right margin).
>
> Sure. You mean like this?:
[...]
> (If the boxed t
After checking the docs, it doesn't seem like groff offers a register or any
other way for checking if it is being run in unsafe mode. Would this not be a
good idea? I have some macros that use unsafe requests to create and update an
index. I'd like for these macros to be silent or issue may
> After checking the docs, it doesn't seem like groff offers a
> register or any other way for checking if it is being run in unsafe
> mode.
Check the \n[.U] register.
I'll add something to the docs to make it easier to find it.
Werner
> > After checking the docs, it doesn't seem like groff offers a
> > register or any other way for checking if it is being run in
> > unsafe mode.
>
> Check the \n[.U] register.
BTW, this has been introduced in version 1.19.1.
Werner
On Tue, Feb 26, 2008 at 02:01:57PM +0900, Michael(tm) Smith wrote:
> Subject: Re: [Groff] nroff vs. troff conditional using escapes?
>
> So I think what would actually best for me to try to do is have
> my app always generated the \c before and after the string, and to
> preserve any whitespace th
Thanks!
Now, unless I'm misreading the intent, the documented \n[.U] is ascribed
behavior opposite to what actually happens. According to the manual, "If
gtroff is called with the -U command line option, the number register .U is set
to 1, otherwise to zero."
On groff 1.19.3 (on Solaris), I u
> Now, unless I'm misreading the intent, the documented \n[.U] is
> ascribed behavior opposite to what actually happens. According to
> the manual,
Oops! Fixed in the CVS. groff now behaves as documented.
Werner
On Tuesday 26 February 2008 03:53, Clarke Echols wrote:
> Michael(tm) Smith wrote:
> > .PP
> > For more information, see the preceding section (
> > .t-or-n "Description" "DESCRIPTION"
> > ) or the
> > .t-or-n "Introduction" "INTRODUCTION"
> > section for this document.
> >
> > And if I
10 matches
Mail list logo
