On Fri, Dec 05, 2014 at 03:06:08PM +, Ralph Corderoy wrote:
> > Is this included into any of the man pages. I tried to find, but
> > couldn't, but I haven't searched all of groff man pages.
>
> I don't think all of groff's GNU info information is duplicated in the
> man pages.
Man pages were
Hi Anton,
> Is this included into any of the man pages. I tried to find, but
> couldn't, but I haven't searched all of groff man pages.
I don't think all of groff's GNU info information is duplicated in the
man pages. Unfortunately, GNU projects mandate using info even if the
project is another
>From mbian...@foveal.com Fri Dec 5 14:58:42 2014
>
> u stands for "basic unit" ...
>
> From https://www.gnu.org/software/groff/manual/html_node/Measurements.html
>
> gtroff (like many other programs) requires numeric parameters to
> specify various measurements. Most numeric parame
>From d...@oxytropis.plus.com Fri Dec 5 14:30:08 2014
>>
>> The only thing I don't understand is
>> what is "u" in
>>
>> lw(\n[w1]u)
>
>The default unit for the value in the w() modifier is en; so in my
>example w1 has value (in nroff) 144000 and if you leave u off it will
>be evaluated in en's (
u stands for "basic unit" ...
From https://www.gnu.org/software/groff/manual/html_node/Measurements.html
gtroff (like many other programs) requires numeric parameters to
specify various measurements. Most numeric parameters9 may have a
measurement unit attached. Thes
Thank you, that's what I was looking for.
The only thing I don't understand is
what is "u" in
lw(\n[w1]u)
tbl says:
u,UMove the corresponding column up one half-line.
which I don't need, but if I remove "u",
the formatting becomes completely broken.
In my case I get good results wit
The following method works ( give an example):
.sp 1i
.ie n .nr w1 2i
.el .nr w1 .5i
.TS
tab(@);
lw(\n[w1]u) l l.
Hello@World@Nice
Day@Today
.TE
Denis
On Thu, 04 Dec 2014 07:57:50 -0800 (PST)
Anton Shterenlikht wrote:
> I want to make a document that can give good
> ascii and Postscript result
And I would add to this that 'tbl' does not interpret troff requests
(if it sees any in the 'tbl' contents, after the initial formatting
setup, then it simply passes them through to the next link in the chain).
In fact, what 'tbl' does not like in Anton's attempt at .ie/.el is
the fact that it int
> I want to make a document that can give good
> ascii and Postscript results. I found that I need
> to adjust the formating of tables. I'm trying to
> to this with .ie/.el like this:
>
>10 .TS H
>11 expand,center;
>12 .ie t lw(0.5i) lw(0.01i) lw(0.5i) lw(2.5i) lw(1.4i).
>13
The issue is that tbl processes the entire file before groff sees it.
The data follow is typically
tbl From tbl(1) ...
w,WMinimal column width value. Must be followed either by a
troff(1) width expression in parentheses or a unitless integer.
If
I want to make a document that can give good
ascii and Postscript results. I found that I need
to adjust the formating of tables. I'm trying to
to this with .ie/.el like this:
10 .TS H
11 expand,center;
12 .ie t lw(0.5i) lw(0.01i) lw(0.5i) lw(2.5i) lw(1.4i).
13 .el lw(1i) lw(0.
Hi,
Larry Kollar wrote:
> It's defined in groff(7), and in sec. 5.3 of the texinfo doc. Logical
> OR is a colon:
>
> .if \n[EULA]=1:\n[EULA]=3 \{\
>
> It would have been interesting to ask Joe O why a colon instead of a
> pipe here. Anyway, I use constructs like this all the time in my docs.
P
On 01/06/10 21:41:24, Werner LEMBERG wrote:
> > However, I have recently written (as a learning exercise) a macro
> > that automatically indented, nested, aligned, and numbered
> > paragraphs.
>
> This is rather easy to handle by using indirect macro calls. Here an
> outline of a solution:
Thank
> What I would oh-so-love to be able to do is
>
> .if \n[EULA]=1 || \n[EULA]=3
>
> I wandered through the groff docs and didn't see any way to do that.
>
> A) Is there a way?
Yes, of course. groff uses `:' and `&' for C's `||' and `&&'
operators. This, for example, is in m.tmac:
.if (\
> However, I have recently written (as a learning exercise) a macro
> that automatically indented, nested, aligned, and numbered
> paragraphs. The macro takes an optional single argument:
> 1
> a
> A
> i
> I
> 0
>
>
> Arguments 1, a, A, i, and I set the type of numbering; "0" finishes
> the the
Larry McVoy wrote:
.if !\n[EULA]=0 \{\
.if !\n[EULA]=1 \{\
.if !\n[EULA]=2 \{\
.if !\n[EULA]=3 \{\
.ab No EULA defined
.\}
.\}
.\}
If I remember correctly, EULA will return 0 if not previously
defined, so you'll never reach the abort. You can do this in one line:
.if !rEULA .ab No EULA de
On 01/06/10 17:49:04, ted.hard...@manchester.ac.uk wrote:
> > While you are at it, would you please include "elif" in your patch.
> There are already (as well as ".if") ".ie" for "if-else", "&" for
> "and" and ":" for "or".
>
> See 'info groff' under
>
> * Request Index::
> --> * ie:
On 01-Jun-10 04:42:55, Robert Thorsby wrote:
> On 01/06/10 14:16:28, Larry McVoy wrote:
>> What I would oh-so-love to be able to do is
>>
>> .if \n[EULA]=1 || \n[EULA]=3
>>
>> I wandered through the groff docs and didn't see any way to do that.
>>
>> A) Is there a way?
>> B) If not, if I s
On 01/06/10 14:16:28, Larry McVoy wrote:
> What I would oh-so-love to be able to do is
>
> .if \n[EULA]=1 || \n[EULA]=3
>
> I wandered through the groff docs and didn't see any way to do that.
>
> A) Is there a way?
> B) If not, if I send in a patch to do that would the team be open to
>
Hi folks,
We, er, I, use groff to create multiple documents from one. Here's our
header (search for === to skip this):
.ig
** README FIRST **
Notes for people unfamiliar with this file format:
Line breaks are very important, if you work on this work on it with an
edito
20 matches
Mail list logo
