discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Jason McIntyre <jmc@kerhand.co.uk>
To: discuss@mdocml.bsd.lv
Subject: .Sm issue in (openbsd) ftp.1
Date: Mon, 26 Jul 2010 22:24:42 +0059	[thread overview]
Message-ID: <20100726212506.GD12294@bramka.kerhand.co.uk> (raw)

hi. apologies for the macro abuse... here's some source in ftp.1:

	.Nm ftp
	.Op Fl C
	.Op Fl o Ar output
	.Sm off
	.No ftp:// Oo Ar user : password No @
	.Oc Ar host Oo : Ar port
	.Oc No / Ar file Oo /
	.Oc
	.Sm on
	.Ar ...

groff does this:

	ftp [-C] [-o output] ftp://[user:password@]host[:port]/file[/] ...

and mandoc:

	ftp [-C] [-o output] ftp:// [user:password@]host[:port]/file[/] ...

so, somehow mandoc seems to be ignoring the spacing off call between //
and [user.

jmc
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

             reply	other threads:[~2010-07-26 21:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 21:25 Jason McIntyre [this message]
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

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=20100726212506.GD12294@bramka.kerhand.co.uk \
    --to=jmc@kerhand.co.uk \
    --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).