9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Humm <hummsmith42@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] troff: we are not htmlroff
Date: Sun, 5 Dec 2021 02:36:22 +0000	[thread overview]
Message-ID: <YawlprSf0nmvqZ/r@beryllium.local> (raw)
In-Reply-To: <CG6Z0S4G9DBD.VWTIAL5MO9CQ@eshonai>

Quoth Noam Preil:
>The issue is that we don't correctly detect, in normal roff, that 
>we're NOT htmlroff, not the inverse?

Correct.

In normal troff, we don’t know that `h` can be used as condition in an 
`.if` request.  What we perhaps should do is to handle any character 
we don’t know as false.  What we do instead is weird and wonky 
unexpected behavior.  Some stuff gets executed when it shouldn’t.  
Some stuff doesn’t get executed when it should.  The current troff 
behavior on `.if h` and `.if !h` is complete garbage.

What this patch does is not to improve troff’s general behavior on 
unknown conditions, but to let it know `h` is false.

>Is this related to the differing behavior with conditionals between 
>troff and htmlroff?

	; troff -a # same with htmlroff
	.de xx
	.tm a
	..
	.if 0 \{\
	.de xx
	.tm b
	..
	.\}
	.xx
	a       ← output

I guess htmlroff(6) is wrong.

-- 
Humm

  reply	other threads:[~2021-12-05 10:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-27 19:43 Humm
2021-12-04 23:23 ` Humm
2021-12-04 23:46   ` Sigrid Solveig Haflínudóttir
2021-12-05  1:24     ` Humm
2021-12-05  1:48       ` Sigrid Solveig Haflínudóttir
2021-12-05  0:46   ` Noam Preil
2021-12-05  1:19     ` Noam Preil
2021-12-05  2:36       ` Humm [this message]
2021-12-05 13:22         ` Noam Preil
2021-12-05  1:19     ` Humm
2021-12-05  0:00 ` ori

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=YawlprSf0nmvqZ/r@beryllium.local \
    --to=hummsmith42@gmail.com \
    --cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).