From: Joerg Sonnenberger <joerg@britannica.bec.de>
To: tech@mdocml.bsd.lv
Subject: Re: line termination in manuals
Date: Sat, 22 Jan 2011 21:05:17 +0100 [thread overview]
Message-ID: <20110122200516.GA26592@britannica.bec.de> (raw)
In-Reply-To: <20110122195656.GE12520@iris.usta.de>
On Sat, Jan 22, 2011 at 08:56:56PM +0100, Ingo Schwarze wrote:
> deraadt@ pointed out that, if somebody would compile mandoc
> on Windows, the C library would take care of different
> conventions regarding line termination.
Actually, it wouldn't. We explicitly read the file as whole or mmap it
and separate it at \n. I don't see a good reason why we couldn't just
drop \r before \n and accept both silently.
Joerg
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2011-01-22 20:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 19:56 Ingo Schwarze
2011-01-22 20:05 ` Joerg Sonnenberger [this message]
2011-01-22 21:28 ` Ingo Schwarze
2011-01-22 21:35 ` Joerg Sonnenberger
2011-01-22 22:18 ` Ingo Schwarze
2011-01-22 22:28 ` Kristaps Dzonsons
2011-01-22 22:29 ` Joerg Sonnenberger
2011-01-22 22:59 ` Ingo Schwarze
2011-01-24 23:16 ` Kristaps Dzonsons
2011-01-25 0:09 ` Ingo Schwarze
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=20110122200516.GA26592@britannica.bec.de \
--to=joerg@britannica.bec.de \
--cc=tech@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).