On 14.03.25 02:11, Tadziu Hoffmann wrote:
> Every empty line in the input will also result in an empty line
> in the output and will thus inhibit filling of text. Make sure
> you don't have any empty lines in your input file.
>
> I'm just mentioning this because your emails here on the list
The attached "sample.groff" does not flow together lines, following a .PP,
expected to compile a paragraph. Yet going the whole .RP trip, for conformity's
sake, in groff_primer.ms, *does* spuriously flow together successive \n
terminated lines *without* a .PP or .LP, and that's even more useless
On 14.03.25 16:29, Damian McGuckin wrote:
> On Fri, 14 Mar 2025, dvalin--- via GNU roff typesetting system discussion
> wrote:
>
> > It seriously looks like the most productive way forward is to go back to
> > raw troff, or failing to find the secret sauce there, look f
On 14.03.25 07:29, dvalin--- via GNU roff typesetting system discussion wrote:
> It is probable that a neutral terminator for .SH, .LP, and .PP scope, could
> be all that is needed. Then "as presented" code or command lines will neither
> be wrapped nor bolded. I'll s
Aaargh. Here's the missing attachment..RP no \" Title page, "no" repeats on next pags.
.nr PL 8i \" Else filling overruns A5 length.
.nr PO 0.5 \" Halve the default left margin. (in)
.nr HM 0.4 \" Smaller header margin.
.nr FM 0.4
On 14.03.25 13:45, G. Branden Robinson wrote:
> At 2025-03-14T09:00:50+0000, dvalin--- via GNU roff typesetting system
> discussion wrote:
...
> > Yes, at "4.6.5.3 Paragraphs" I read "Alternatively, a blank input line
> > breaks the output line and vertically
On 14.03.25 00:25, G. Branden Robinson wrote:
> At 2025-03-14T04:52:59+0000, dvalin--- via GNU roff typesetting system
> discussion wrote:
> > The attached "sample.groff" does not flow together lines, following a
> > .PP, expected to compile a paragraph. Yet going
On 14.03.25 09:33, Robert Goulding wrote:
> On Fri, Mar 14, 2025 at 9:14 AM dvalin--- via GNU roff typesetting system
> > AHA! Squirrelled away under "4.6.5.8 Keeps, boxed keeps, and displays",
> > there's a non-wrapping paragraph, i,e, .LD. That fixes the unwanted
> > wrapping, and .SH overru
On 14.03.25 11:06, Robert Goulding wrote:
> A display (introduced by .LD) needs a closing .DE macro. And I would also
> close a heading macro with a paragraphing macro. Yes, your method may get
> visually the right results, but it may be unpredictable, since some
> housekeeping behind the scene
On 11.04.25 06:24, G. Branden Robinson wrote:
> At 2025-03-30T22:23:58+, Lennart Jablonka wrote:
> > It’s implementation-defined whether \+ behaves like literal + or like
> > \{1,\}. (The same applies to \? and \|; I didn’t find uses of those.)
> > As it happens, OpenBSD treats it as liter
Using:
$ groff --version
GNU groff version 1.23.0
Spurious warnings:
test.grf:6: Invalid horizontal alignment 'f': must be 'b', 'c', 'l' or 'r'.
test.grf:8: Invalid horizontal alignment 'v': must be 'b', 'c', 'l' or 'r'.
and faulty output are triggered by a:
groff -k -Tpdf -ms -m hdtbl -dpap
Many thanks, Branden.
On 20.04.25 20:18, G. Branden Robinson wrote:
...
> The warnings in category "tab" suggest to me a macro programming error
> in hdtbl itself, since no tab characters occur in your input.
Dunno if this helps narrow it down, but if the same problem table row is
input in th
On 21.04.25 02:51, Dave Kemper wrote:
> On Sun, Apr 20, 2025 at 8:54 PM Ingo Schwarze < schwa...@usta.de > wrote:
> > So just deleting it would still be the best option even now.
>
> A better option is deprecating it
> ( http://savannah.gnu.org/bugs/?64772 ). It could emit a warning that
> i
On 12.03.25 23:31, Dave Kemper wrote:
> Hi, and welcome to the world of groff!
Thank you. Each new utility is an adventure, even if more than a little
perplexing at the outset.
> Tackling your second issue first:
...
> To get italics in basic troff, try this:
> This is
> .ft I
> italic stu
Hi,
My first ever lines of groff, output as default postscript, do render -
partially.
$ groff --version
GNU groff version 1.22.4
$ more /tmp/sample.groff
This is
.I "italic stuff" ,
I hope.
$ groff -ms /tmp/sample.groff > /tmp/sample.ps
troff: fatal error: can't find macro file s
OK, le
On 08.06.25 07:12, G. Branden Robinson wrote:
> [1] CSTR #116 doesn't seem to have a general name for these dotted
> suffixes, or at least not one I'm crazy about. Kernighan does call
> them "corners" (and "compass points") (§5), but these terms seem to
> me to apply poorly to ".c[
$ groff --version
GNU groff version 1.23.0
$ echo .pfp | groff -T ps
$
So no fonts installed, I guess. Reading UnixTextProcessing.pdf¹ gives only a
glancing reference to groff pseudofonts. An initial scan of "man grops",
yielding the "FONT INSTALLATION" section fleetingly looked promising. Bu
17 matches
Mail list logo
