[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [groff] groff as the basis for comprehensive documentation?
From: |
Ralph Corderoy |
Subject: |
Re: [groff] groff as the basis for comprehensive documentation? |
Date: |
Mon, 16 Apr 2018 14:56:54 +0100 |
Hi John,
> Does anybody else here manage to line-wrap their commit messages at
> *precisely* 72-characters without the aide of hyphenation or justification?
> ;-) Or is it just me?
I find myself sometimes breaking a line after a comma or full stop,
without starting a new paragraph, if the line is still a good length.
Rather than vim's `gwap', or fmt(1), say.
It's convenient for later edits being isolated in their ripple effect.
I think Bell Labs book authors often did this when using ed(1) as the
edits were line based and the edit often wanted to work on a clause.
Does anyone here know a fmt(1)-er that tries to do this?
fmt(1) alternatives I know are
https://en.wikipedia.org/wiki/Par_(command)
http://search.cpan.org/~neilb/Text-Autoformat-1.74/lib/Text/Autoformat.pm
The latter can easily be run from the command line,
not just used as a module in Perl.
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
Re: [groff] groff as the basis for comprehensive documentation?, Ralph Corderoy, 2018/04/16
- Re: [groff] groff as the basis for comprehensive documentation?, Ingo Schwarze, 2018/04/16
- Re: [groff] groff as the basis for comprehensive documentation?, John Gardner, 2018/04/16
- Re: [groff] groff as the basis for comprehensive documentation?,
Ralph Corderoy <=
- Re: [groff] groff as the basis for comprehensive documentation?, John Gardner, 2018/04/16
- Re: [groff] groff as the basis for comprehensive documentation?, Ralph Corderoy, 2018/04/16
- Re: [groff] groff as the basis for comprehensive documentation?, G. Branden Robinson, 2018/04/21
Re: [groff] groff as the basis for comprehensive documentation?, Ralph Corderoy, 2018/04/16
Re: [groff] groff as the basis for comprehensive documentation?, Larry Kollar, 2018/04/18