discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Kristaps Dzonsons <kristaps@bsd.lv>
To: discuss@mdocml.bsd.lv
Subject: Re: more spacing badness
Date: Wed, 15 Sep 2010 17:53:58 +0200	[thread overview]
Message-ID: <4C90EC16.8010002@bsd.lv> (raw)
In-Reply-To: <20100910211434.GA17432@bramka.kerhand.co.uk>

> from vi(1):
> 
>      ex [-FRrSsv] [-c cmd] [-t tag] [-w size] [file ...]
>      vi [-eFRrS] [-c cmd] [-t tag] [-w size] [file ...]
>      view [-eFrS] [-c cmd] [-t tag] [-w size] [file ...]
> 
> i wanted to format those nicely (in my opinion anyway) so i tried to put
> a double space between "vi" and its args. current code does this:

I gather you're trying to align to the maximum length Nm token.  I agree
it looks better.  Something to think about later, maybe.

> so i tried:
> 
> 	.Nm vi\ \&
> 
> old and new groff produce:
> 
> 	vi  [-eFRrS] [-c cmd] [-t tag] [-w size] [file ...]
> 
> but mandoc seems to inject a tab:
> 
> 	vi    [-eFRrS] [-c cmd] [-t tag] [-w size] [file ...]

My last commit fixes this in a general way.  The problem was "\ \&"
being read as the string length.  Now string length calculations (for
-Tascii, -Tpdf, and -Tps) all take into account escapes.  This lifts a
long-standing feature request in the TODO.

Thanks,

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

  reply	other threads:[~2010-09-15 15:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10 21:14 Jason McIntyre
2010-09-15 15:53 ` Kristaps Dzonsons [this message]
2010-09-21 23:05   ` Ingo Schwarze
2010-09-22  7:09     ` Jason McIntyre
2010-09-22  8:11       ` 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=4C90EC16.8010002@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).