From: Kristaps Dzonsons <kristaps@bsd.lv>
To: discuss@mdocml.bsd.lv
Subject: Re: .Sm issue in (openbsd) ftp.1
Date: Tue, 27 Jul 2010 00:28:59 +0200 [thread overview]
Message-ID: <4C4E0C2B.4030003@bsd.lv> (raw)
In-Reply-To: <4C4E0783.1060902@bsd.lv>
Kristaps Dzonsons wrote:
> Kristaps Dzonsons wrote:
>> Jason,
>>
>> Can you send me a list of files with the craziest `Sm' invocations you
>> konw of? I have a fix for this and want to make sure it doesn't puke
>> in other cases.
>
> ...nevermind. I'm running through all `Sm' manuals by hand and
> comparing the output (there aren't that many). Looks good so far. Every
> `Sm' seems to be rendered properly.
Jason et al.,
I've committed a fix for this.
Please test this on your complex `Sm' cases. I looked over a few dozen
manuals with this macro (including the biggies, grep, sh, ed, etc.) and
didn't see any issues.
Thanks,
Kristaps
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2010-07-26 22:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 21:25 Jason McIntyre
2010-07-26 21:33 ` Jason McIntyre
2010-07-26 21:56 ` Kristaps Dzonsons
2010-07-26 22:09 ` Kristaps Dzonsons
2010-07-26 22:28 ` Kristaps Dzonsons [this message]
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=4C4E0C2B.4030003@bsd.lv \
--to=kristaps@bsd.lv \
--cc=discuss@mdocml.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).