> You were either very lucky or very careful; most CVS repos of any
> age have a lot more cruft in them than this.
:-) It's probably due to my aversion to branches, at least with CVS...
> What happened to the history before 2000?
Honestly, I don't know; see my other e-mail. Looking up the grof
On Thu, Nov 21, 2013, James K. Lowden wrote:
> While I'm in the neighborhood, I wonder if commas in numbers get
> special treatment? Reading over my document, the number 34,800 looked
> bad; the comma was squished over by the eight. The effect was
> especially noticable when the comma trails a 7.
On Wed, 20 Nov 2013 14:59:26 -0500
Doug McIlroy wrote:
> > I can't think of a situation where you would want to mix point sizes
> > on a line.
>
> A fairly common case is small caps, as in acronyms. Another is mixed
> fonts (e.g. using Courier for computer literals) with different
> x-heights
Compared to most CVS conversions this one was almost ridiculously easy;
cvs-fast-export and reposurgeon made short work of it. (I improved
both slightly in the process, which is normal; every repo, even the
easy ones, is a different challenge.)
The git conversion is nearly linear, with one root,
Groff Bug Report
GROFF VERSION:
1.22.2 (current-groff from 17th October 2013)
MACHINE:
laptop (i586)
OS:
GNU/Linux 3.2.46-1-rt67-1; Debian 7.2 (wheezy)
COMPILER:
gcc 4.7.2 (Debian 4.7.2-5)
INPUT FILES:
.../groff-current/src/preproc/preconv/preconv.man
COMMAND LINE:
Groff Bug Report
GROFF VERSION:
1.22.2 (current-groff from 17th October 2013)
MACHINE:
laptop (i586)
OS:
GNU/Linux 3.2.46-1-rt67-1; Debian 7.2 (wheezy)
COMPILER:
gcc 4.7.2 (Debian 4.7.2-5)
INPUT FILES:
.../groff-current/src/preproc/pic/pic.man
COMMAND LINE:
groff -
Groff Bug Report
GROFF VERSION:
1.22.2 (current-groff from 17th October 2013)
MACHINE:
laptop (i586)
OS:
GNU/Linux 3.2.46-1-rt67-1; Debian 7.2 (wheezy)
COMPILER:
gcc 4.7.2 (Debian 4.7.2-5)
INPUT FILES:
.../groff-current/src/preproc/tbl/tbl.man
COMMAND LINE:
groff -
Groff Bug Report
GROFF VERSION:
1.22.2 (current-groff from 17th October 2013)
MACHINE:
laptop (i586)
OS:
GNU/Linux 3.2.46-1-rt67-1; Debian 7.2 (wheezy)
COMPILER:
gcc 4.7.2 (Debian 4.7.2-5)
INPUT FILES:
.../groff-current/src/preproc/refer/refer.man
COMMAND LINE:
gro
Groff Bug Report
GROFF VERSION:
1.22.2 (current-groff from 17th October 2013)
MACHINE:
laptop (i586)
OS:
GNU/Linux 3.2.46-1-rt67-1; Debian 7.2 (wheezy)
COMPILER:
gcc 4.7.2 (Debian 4.7.2-5)
INPUT FILES:
.../groff-current/src/preproc/grn/grn.man
COMMAND LINE:
groff -
Groff Bug Report
GROFF VERSION:
1.22.2 (current-groff from 17th October 2013)
MACHINE:
laptop (i586)
OS:
GNU/Linux 3.2.46-1-rt67-1; Debian 7.2 (wheezy)
COMPILER:
gcc 4.7.2 (Debian 4.7.2-5)
INPUT FILES:
.../groff-current/src/preproc/eqn/eqn.man
COMMAND LINE:
groff -
Steve --
Great musings on the lowly dash.
On Wed, Nov 20, 2013, Steve Izma wrote:
> Yet I'll admit that my idea of dashes is not traditional: I
> consider a dash not to be a punctuation mark affixed to another
> object (e.g., as a period to a sentence or a comma to a phrase),
> but more like an o
Ulrich --
On Thu, Nov 21, 2013, Ulrich Lauther wrote:
> When the text of an ITEM needs more than one line, the spacing beetween these
> lines is larger than that of running text outside the list.
> (I am not talking about line space between items, but inside an item).
>
> Is this behaviour intend
When the text of an ITEM needs more than one line, the spacing beetween these
lines is larger than that of running text outside the list.
(I am not talking about line space between items, but inside an item).
Is this behaviour intended? If so, why? Can I change it?
(This is a difference to lists
13 matches
Mail list logo
