tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
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)
Date: Mon, 16 Oct 2023 18:03:16 +0200	[thread overview]
Message-ID: <ZS1exKaPW2xNpmPj@asta-kit.de> (raw)
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


  parent reply	other threads:[~2023-10-16 16:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-16 13:17 Alejandro Colomar
2023-10-16 14:52 ` Ingo Schwarze
2023-10-16 15:20   ` Jan Stary
2023-10-16 15:43     ` Ingo Schwarze
2023-10-16 16:03     ` Ingo Schwarze [this message]
2023-10-16 17:10   ` Alejandro Colomar
2023-10-16 17:16     ` Alejandro Colomar
2023-10-16 17:28     ` Alejandro Colomar
2023-10-17 19:02       ` Ingo Schwarze
2023-10-17 21:39         ` Alejandro Colomar
2023-10-18  0:04           ` Ingo Schwarze
2023-10-18 11:32             ` Alejandro Colomar
2023-10-18 14:48             ` Ingo Schwarze
2023-10-18 14:56               ` Alejandro Colomar
2023-10-18 16:20             ` Ingo Schwarze
2023-10-18 18:52               ` Alejandro Colomar
2023-10-19 11:59             ` Ingo Schwarze
2023-10-19 12:48               ` Alejandro Colomar

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=ZS1exKaPW2xNpmPj@asta-kit.de \
    --to=schwarze@usta.de \
    --cc=hans@stare.cz \
    --cc=tech@mandoc.bsd.lv \
    /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;
as well as URLs for NNTP newsgroup(s).