> # generated automatically by aclocal 1.13.1 -*- Autoconf -*-
>
> Probably, we need to written a scarier Auto-generated file notice?
> All CAPS maybe, with a Do not hand edit notice? :)
You might write to the autotools people, suggesting exactly that :-)
To be serious: A few years ago, I did e
# generated automatically by aclocal 1.13.1 -*- Autoconf -*-
Probably, we need to written a scarier Auto-generated file notice? All CAPS
maybe, with a Do not hand edit notice? :)
On Fri, Sep 5, 2014 at 10:35 AM, Werner LEMBERG wrote:
>
> > I tried to let groff create a data directory for the
Hi Blake,
here are the rules:
- column widths are measured unless specified
[tbl(1), second paragraph below "Table data"]
- measurements result in at least 1n [undocumented]
- column separations default to 3n unless specified
[tbl(1), last but one paragraph]
- "\_" extend from the begin
> I tried to let groff create a data directory for the `refer'
> databases. I changed aclocal.m4, Makefile.in, and configure.ac.
*Never* change `aclocal.m4' manually! This is a generated file. The
source files for `aclocal.m4' are in the `m4' directory (well, not all
of them, but the ones spec
>> I haven't built groff from source for a while. Just tried.
>>
>> ./configure: line 4400: GROFF_CXX_CHECK: command not found
>
> Bernd's commit 9f6f7cf3b0e4d1c615f625eda7c686a483d572a6 appears to have
> badly damaged configure. Running "autoreconf -fi -I m4" fixes it
> (Bernd, the need for "
On Thu, Sep 04, 2014, Colin Watson wrote:
> On Thu, Sep 04, 2014 at 12:50:29PM -0400, Peter Schaffter wrote:
> > I haven't built groff from source for a while. Just tried.
> >
> > ./configure: line 4400: GROFF_CXX_CHECK: command not found
>
> Bernd's commit 9f6f7cf3b0e4d1c615f625eda7c686a483d572
I still can't understand the output of my previous email, however, I now
realize that the output I was looking for is achieved with:
.TS
tab(;);
L L L .
AAA;BBB;CCC
\_;\_;\_
aaa;bbb;ccc
.TE
On Thu, Sep 4, 2014 at 10:01 PM, Blake McBride wrote:
> Greetings,
>
> Playing with tbl, I hit somethi
Greetings,
Playing with tbl, I hit something I can't figure out. I get the same
result with groff and heirloom so it must be me. My input text looks like
this:
.TS
tab(;);
L L L L L .
AAA;;BBB;;CCC
_;;_;;_
aaa;;bbb;;ccc
.TE
The first column is, unexpectedly, wide, i.e. longer than needed.
Th
On Thu, Sep 04, 2014 at 12:50:29PM -0400, Peter Schaffter wrote:
> I haven't built groff from source for a while. Just tried.
>
> ./configure: line 4400: GROFF_CXX_CHECK: command not found
Bernd's commit 9f6f7cf3b0e4d1c615f625eda7c686a483d572a6 appears to have
badly damaged configure. Running "
On Thu, Sep 04, 2014 at 03:35:25PM +0100, Anton Shterenlikht wrote:
> >Date: Thu, 4 Sep 2014 12:31:09 +0200 (CEST)
> >From: Carsten Kunze
> >To: groff@gnu.org
> >
> >You could try
> >
> >.mk A
> >
> >and on the next page
> >
> >.sp |\nA
> >
> >(have not tested that.)
>
> In UNIX Text Processing,
On Thu, Sep 04, 2014, Werner Lemberg wrote:
>
> > contrib/mom: license and Emacs setup; ChangeLog: repair it.
>
> Bernd, I generally applause your efforts on normalizing those issues.
> However, `mom' is actively maintained by Peter, and your changes are
> quite substantial, so please contact
I haven't built groff from source for a while. Just tried.
./configure: line 4400: GROFF_CXX_CHECK: command not found
./configure: line 4401: GROFF_EBCDIC: command not found
./configure: line 4402: GROFF_OS390: command not found
./configure: line 4403: GROFF_X11: command not found
./configure: li
Most files in doc/ have no or strange real copying information.
I will not change anything a them. If someone wants to add
something reasonable, that would be fine.
Bernd Warken
On Thu, Sep 04, 2014, Anton Shterenlikht wrote:
> >Date: Thu, 4 Sep 2014 12:31:09 +0200 (CEST)
> >From: Carsten Kunze
> >To: groff@gnu.org
> >
> >You could try
> >
> >.mk A
> >
> >and on the next page
> >
> >.sp |\nA
> >
> >(have not tested that.)
>
> In UNIX Text Processing, p. 462, the advice i
> > contrib/mom: license and Emacs setup; ChangeLog: repair it.
>
> Bernd, I generally applause your efforts on normalizing those issues.
> However, `mom' is actively maintained by Peter, and your changes are
> quite substantial, so please contact him in advance whether he likes
> your modific
>Date: Thu, 4 Sep 2014 12:31:09 +0200 (CEST)
>From: Carsten Kunze
>To: groff@gnu.org
>
>You could try
>
>.mk A
>
>and on the next page
>
>.sp |\nA
>
>(have not tested that.)
In UNIX Text Processing, p. 462, the advice is
.mk Q
.sp |\nQu
Neither your form nor theirs (with "u" at the end) work.
I
> Von: "Keith Marshall"
>
> And BTW, I also noticed that you changed the FDL document ... an action
> which is EXPRESSLY FORBIDDEN by the document itself. No matter how
> trivial you deem the change, it could be construed as an infringement of
> the licence which that document grants. It would b
>From ra...@inputplus.co.uk Thu Sep 4 12:49:40 2014
>
>Hi Anton,
>
>> Also, in latex figures are treated as floats and the text can move
>> before the figure, even if it's later than the fiture in the src, if
>> there is some space left on the previous page, and the figure does not
>> fit. I'm us
Ralph Corderoy wrote:
> See ascii(7), as others have said, and 10.1 in http://troff.org/54.pdf
> around where it says
I should probably stop skim through this document to look
for command definition, and start reading it from the begin
to the end... :)
Thanks !
Pierre-Jean.
Hi Anton,
> Also, in latex figures are treated as floats and the text can move
> before the figure, even if it's later than the fiture in the src, if
> there is some space left on the previous page, and the figure does not
> fit. I'm using ms and with simple .PS/.PE I cannot achive this
> behavio
You could try
.mk A
and on the next page
.sp |\nA
(have not tested that.)
I use .mk/.rt to place multiple pic drawings
side by side. I noticed that when the .PS/.PE
macros occur at the bottom of the page, and
the drawing does not fit, the drawings appear
on the following page one after another vertically,
no longer aligned.
Is this the expected behavior?
I might have mi
Hi Pierre-Jean,
> I've recently seen the usage of the ^G character as field separator.
> That is a good idea, since it should avoid most possible conflicts
> with user input. But does anyone know what does this character means,
> and why does it seems to be prefered to other control characters ?
23 matches
Mail list logo
