From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham
	autolearn_force=no version=3.4.4
Received: (qmail 27420 invoked from network); 16 Oct 2023 16:03:20 -0000
Received: from bsd.lv (HELO mandoc.bsd.lv) (66.111.2.12)
  by inbox.vuxu.org with ESMTPUTF8; 16 Oct 2023 16:03:20 -0000
Received: from fantadrom.bsd.lv (localhost [127.0.0.1])
	by mandoc.bsd.lv (OpenSMTPD) with ESMTP id 0d7a6628
	for <ml@inbox.vuxu.org>;
	Mon, 16 Oct 2023 16:03:19 +0000 (UTC)
Received: from scc-mailout-kit-02.scc.kit.edu (scc-mailout-kit-02.scc.kit.edu [129.13.231.82])
	by mandoc.bsd.lv (OpenSMTPD) with ESMTP id e1651300
	for <tech@mandoc.bsd.lv>;
	Mon, 16 Oct 2023 16:03:19 +0000 (UTC)
Received: from hekate.asta.kit.edu ([2a00:1398:5:f401::77])
	by scc-mailout-kit-02.scc.kit.edu with esmtps (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
	(envelope-from <schwarze@usta.de>)
	id 1qsQ3q-006F2J-0b;
	Mon, 16 Oct 2023 18:03:18 +0200
Received: from login-1.asta.kit.edu ([2a00:1398:5:f400::72])
	by hekate.asta.kit.edu with esmtp (Exim 4.94.2)
	(envelope-from <schwarze@usta.de>)
	id 1qsQ3p-0005mW-IM; Mon, 16 Oct 2023 18:03:17 +0200
Received: from schwarze by login-1.asta.kit.edu with local (Exim 4.94.2)
	(envelope-from <schwarze@usta.de>)
	id 1qsQ3o-000V6G-SM; Mon, 16 Oct 2023 18:03:16 +0200
Date: Mon, 16 Oct 2023 18:03:16 +0200
From: Ingo Schwarze <schwarze@usta.de>
To: Jan Stary <hans@stare.cz>
Cc: tech@mandoc.bsd.lv
Subject: Re: mandoc -man -Thtml: unwanted line break after bullet (.IP)
Message-ID: <ZS1exKaPW2xNpmPj@asta-kit.de>
References: <ZS031GrGpzbAuwpn@debian>
 <ZS1OHqdIbZyF3ROu@asta-kit.de>
 <ZS1UswPaKCTw_10G@www.stare.cz>
X-Mailinglist: mandoc-tech
Reply-To: tech@mandoc.bsd.lv
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ZS1UswPaKCTw_10G@www.stare.cz>

Hi Jan,

sorry for not realizing before sending my first reply how easy it is
to actually test this.  So here is a second reply:

Jan Stary wrote on Mon, Oct 16, 2023 at 05:20:19PM +0200:
> On Oct 16 16:52:14, schwarze@usta.de wrote:

>> as expected, the "final text" follows on the same line.

> For completeness: it doesn't, in lynx.
> But that's on lynx, which seems to make the break after <dt>

   $ ktrace lynx tmp.html  # once in lynx, hit the "q" and "y" keys
   $ kdump | grep css     
     <link rel="stylesheet" href="mandoc.css" type="text/css" media="all"\
   $ ls -al mandoc.css
     -rw-r--r--  1 schwarze  wsrc  8920 Mar 17  2022 mandoc.css

So, lynx(1) sees the link element in the input file,
the CSS file is present in the right place and readable,
but lynx(1) does not even attempt to read it.

So, not really a surprise that whitespace does not work at all
in lynx(1).

Yours,
  Ingo
--
 To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv