public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Deri <deri@chuzzlewit.myzen.co.uk>,
	"G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: groff <groff@gnu.org>, linux-man <linux-man@vger.kernel.org>
Subject: Re: [BUG] gropdf, tbl: Completely broken table (was: Ping^1: Chapters of the manual (was: Bug#1018737: ...))
Date: Sun, 18 Dec 2022 12:25:54 +0100	[thread overview]
Message-ID: <a82b66ad-0c73-aaea-c6d5-2e5596d12438@gmail.com> (raw)
In-Reply-To: <1889004.IobQ9Gjlxr@pip>


[-- Attachment #1.1: Type: text/plain, Size: 993 bytes --]

Hi Deri,

On 12/17/22 22:26, Deri wrote:
> Hi Alex,
> 
> This is a bug in my perl script which assembles the Linux Manpage Book,
> nothing to do with groff, tbl or gropdf, just a bad habit I have of scrubbing
> leading spaces before parsing a line, normally fine, but disastrous when the
> space is intended to protect a full stop being the first character.

Ahh, makes sense.

I thought it could be a bug in groff, since I had seen the same issue last year, 
I think with grohtml (but I'm talking from memory).  Maybe Branden remembers.

> 
> For this reason, if you find issues with the book it probably is not relevent
> to the groff list, since it is more likely to be an issue with code which is
> just a few hours old. Any faults, or changes you would like, please send to
> me, since it is not relevent to the groff list.

Understood!

I'm impatient to see that script :)

Cheers,

Alex

> 
> Cheers
> 
> Deri

-- 
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-12-18 11:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220906191320.447t5awx3rcb5d5b@illithid>
     [not found] ` <a7b8c6b3-a8e8-6ab7-6cf4-118446849a9c@gmail.com>
     [not found]   ` <dca0e251-7481-7f1e-4077-0ddee070a357@gmail.com>
     [not found]     ` <20220906204245.hzhq2s7yha6zzgrh@illithid>
     [not found]       ` <30e80fe0-f0ce-d6cd-ee40-28692e5a5f82@gmail.com>
     [not found]         ` <5c1e8620-e4ff-c79a-1d4e-11f797276726@gmail.com>
     [not found]           ` <20221116234049.GA1229865@if>
     [not found]             ` <f306a83a-306d-e3d0-5d25-bf07da3da59f@gmail.com>
2022-11-17  0:28               ` Chapters of the manual (was: Bug#1018737: /usr/bin/rst2man: rst2man: .TH 5th field shouldn't be empty) Alejandro Colomar
2022-12-11 16:40                 ` Ping^1: " Alejandro Colomar
2022-12-11 19:05                   ` Michael Haardt
2022-12-11 19:21                     ` Alejandro Colomar
2022-12-11 21:10                       ` Michael Haardt
2022-12-12  0:34                       ` Douglas McIlroy
2022-12-12 11:39                         ` Alejandro Colomar
2022-12-12  8:58                     ` Ralph Corderoy
2022-12-12 13:19                   ` G. Branden Robinson
2022-12-12 13:57                     ` Andries E. Brouwer
2022-12-12 13:39                 ` Colin Watson
2022-12-12 13:48                   ` Alejandro Colomar
     [not found] ` <1719285.QkHrqEjB74@pip>
     [not found]   ` <01989003-349f-fb6b-f460-89106b82bc34@gmail.com>
     [not found]     ` <2176657.1BCLMh4Saa@pip>
2022-12-17 11:51       ` Ping^1: " Alejandro Colomar
2022-12-17 13:19         ` [BUG] gropdf, tbl: Completely broken table (was: Ping^1: Chapters of the manual (was: Bug#1018737: ...)) Alejandro Colomar
2022-12-17 16:08           ` G. Branden Robinson
2022-12-17 21:26             ` Deri
2022-12-18 11:25               ` Alejandro Colomar [this message]
2022-12-18  5:49             ` [BUG] gropdf, tbl: Completely broken table Ralph Corderoy
2022-12-18 11:01               ` Alejandro Colomar
2022-12-18 11:46             ` [BUG] gropdf, tbl: Completely broken table (was: Ping^1: Chapters of the manual (was: Bug#1018737: ...)) Alejandro Colomar
2022-12-19  5:32               ` groff 1.23.0.rc2 status report (was: [BUG] gropdf, tbl: Completely broken table) G. Branden Robinson
2022-12-19 12:58                 ` Deri
2022-12-19 16:39                 ` Alejandro Colomar
2022-12-19 16:59                   ` patching suffixes(7) (was: groff 1.23.0.rc2 status report) G. Branden Robinson
2022-12-19 19:10                     ` Alejandro Colomar
2022-12-19 19:54                       ` prehistory branch (was: patching suffixes(7) (was: groff 1.23.0.rc2 status report)) Alejandro Colomar
2022-12-19 20:05                         ` Alejandro Colomar
2022-12-20  3:40                       ` patching suffixes(7) (was: groff 1.23.0.rc2 status report) G. Branden Robinson
2022-12-20 10:12                         ` Alejandro Colomar
2022-12-19 16:51                 ` groff 1.23.0.rc2 status report (was: [BUG] gropdf, tbl: Completely broken table) G. Branden Robinson
2022-12-17 21:37         ` Ping^1: Chapters of the manual (was: Bug#1018737: /usr/bin/rst2man: rst2man: .TH 5th field shouldn't be empty) Deri

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a82b66ad-0c73-aaea-c6d5-2e5596d12438@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=deri@chuzzlewit.myzen.co.uk \
    --cc=g.branden.robinson@gmail.com \
    --cc=groff@gnu.org \
    --cc=linux-man@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox