From: ori@eigenstate.org
To: 9fans@9fans.net
Subject: Re: [9fans] htmlroff -ms footnotes
Date: Fri, 06 Oct 2023 13:46:40 -0400 [thread overview]
Message-ID: <922F26CC43173123CA268EE066B84F51@eigenstate.org> (raw)
In-Reply-To: <22409446b2fe5aea7947421b34871cf2@9srv.net>
Quoth a@9srv.net:
> Working on a little one-page report, I noticed htmlroff wasn't
> outputing my footnotes. Looking at the papers in /sys/doc, it
> seems htmlroff produces them properly when they're in the
> abstract, but not in the main body.
>
> Anybody looked at this or know why?
no, but do you have an example to reproduce it?
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T530822947a31ba06-M99ab62c023197f18c8a955a9
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2023-10-06 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 16:45 a
2023-10-06 17:46 ` ori [this message]
2023-10-06 20:59 ` a
2023-10-07 1:59 ` umbraticus
2023-10-07 2:06 ` umbraticus
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=922F26CC43173123CA268EE066B84F51@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9fans@9fans.net \
/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).