Re: [Groff] Problems with arcs and angles

At 2017-04-28T15:31:30+1000, John Gardner wrote: > This might be the wrong forum to ask for help with trigonometry, but I > was planning to announce progress eventually anyway. I have no experience with pic, but I faintly recall some trig. Maybe I can help. > Now, this pic code: > > .PS > > "+"

Re: [Groff] bug in macro '.IR' (was ASCII Minus Sign in man Pages).

>> I reported this bug (and in '.IB') in August 2014, #42906 > > It'd be nice if 3 year-old bugs could get some feedback from the > maintenance team. > > What needs to happen to make that possible? A new maintainer. Werner

[Groff] Problems with arcs and angles

Hello! Some time ago, I announced my intent to build a man-page previewer for a text-editor named Atom . Work is coming along nicely: this page was generated using a lightweig

Re: [Groff] Nesting font macros in man pages

This touches on something I experienced recently. I wanted to write a JavaScript module that would help developers generate manual-pages for their projects (because there's a searing lack of manpages in the Node community...). I ended up ditching that idea when I realised developers would still be

Re: [Groff] Nesting font macros in man pages

At 2017-04-27T23:38:23-0400, James K. Lowden wrote: > On Wed, 26 Apr 2017 09:46:43 -0400 > "G. Branden Robinson" wrote: > > > 1. The slavish devotion to two-letter names for things, which like the > >man macro package and the oldest parts of *roff itself, make it > >self-anti-documenting.

Re: [Groff] bug in macro '.IR' (was ASCII Minus Sign in man Pages).

At 2017-04-27T19:11:29+, Bjarni Ingi Gislason wrote: > On Wed, Apr 26, 2017 at 11:54:21AM -0400, G. Branden Robinson wrote: > > At 2017-04-26T15:50:26+0100, Ralph Corderoy wrote: > > [...] > > > > ??? .IR being is just a shorthand for `\f' and `\^' that can be done > > > manually when n

Re: [Groff] Nesting font macros in man pages

On Thu, 27 Apr 2017, James K. Lowden wrote: The troff system was designed to be typed at a keyboard. The dot-on-the-left rule might be ugly, and the requests/macros terse, but the benefit to the user is relatively few keystrokes above those needed for the text. A corollary of this is that i

Re: [Groff] Nesting font macros in man pages

On Wed, 26 Apr 2017 09:46:43 -0400 "G. Branden Robinson" wrote: > 1. The slavish devotion to two-letter names for things, which like the >man macro package and the oldest parts of *roff itself, make it >self-anti-documenting. Having written one user guide in DocBook, I have to disagree

Re: [Groff] Nesting font macros in man pages

On Thu 27 Apr 2017 23:48:29 Steffen Nurpmeso wrote: > Terrible, see the spacing errors surrounding the command list > before the "Substitution" heading! Not your fault of course, but > gr... > > --steffen Well, turns out it WAS my fault! Bug in gropdf, will commit after more testing. Thanks

Re: [Groff] Nesting font macros in man pages

Deri James wrote: |On Thu 27 Apr 2017 20:12:09 Ingo Schwarze wrote: |> Does that still apply to |> |> view-source:http://man.openbsd.org/ksh | |compared with a PDF version:- | |http://chuzzlewit.co.uk/WebManPDF.pl/man:/1/ksh Terrible, see the spacing errors surrounding the command list

Re: [Groff] Nesting font macros in man pages

Ingo Schwarze wrote: |Steffen Nurpmeso wrote on Tue, Apr 25, 2017 at 08:19:21PM +0200: |> the HTML output of mandoc used repeated per-paragraph style |> directives and a CSS file, which caused enormous bloat, last |> time i tried. | |Does that still apply to | | view-source:http://man.ope

Re: [Groff] Nesting font macros in man pages

On Thu 27 Apr 2017 20:12:09 Ingo Schwarze wrote: > Does that still apply to > > view-source:http://man.openbsd.org/ksh compared with a PDF version:- http://chuzzlewit.co.uk/WebManPDF.pl/man:/1/ksh

Re: [Groff] bug in macro '.IR' (was ASCII Minus Sign in man Pages).

On Wed, Apr 26, 2017 at 11:54:21AM -0400, G. Branden Robinson wrote: > At 2017-04-26T15:50:26+0100, Ralph Corderoy wrote: [...] > > ??? .IR being is just a shorthand for `\f' and `\^' that can be done > > manually when needed, e.g. `.TH'. > > FYI, .IR does not give you this "italic correct

Re: [Groff] Nesting font macros in man pages

Hi, Steffen Nurpmeso wrote on Tue, Apr 25, 2017 at 08:19:21PM +0200: > the HTML output of mandoc used repeated per-paragraph style > directives and a CSS file, which caused enormous bloat, last > time i tried. Does that still apply to view-source:http://man.openbsd.org/ksh I spent a few week

Re: [Groff] Applications of \c in man pages in the wild

Hi, G. Branden Robinson wrote on Thu, Apr 27, 2017 at 09:46:27AM -0400: > At 2017-04-27T14:30:33+0200, Ingo Schwarze wrote: >> wow, you definitely demonstrate diligence in investigating existing >> usage. > [...] >> That can be summarized as follows: Legitimate hand-written use is >> almost inex

Re: [Groff] Applications of \c in man pages in the wild

At 2017-04-27T16:53:45+0200, aksr wrote: > On Thu, Apr 27, 2017 at 09:46:27AM -0400, G. Branden Robinson wrote: > > In any event, I checked out Heirloom troff. Unfortunately its CVS > > repository has not seen a commit in almost 6 years. I tried to build it > > using Heirloom devtools; that, unfo

Re: [Groff] Applications of \c in man pages in the wild

On Thu, Apr 27, 2017 at 09:46:27AM -0400, G. Branden Robinson wrote: > In any event, I checked out Heirloom troff. Unfortunately its CVS > repository has not seen a commit in almost 6 years. I tried to build it > using Heirloom devtools; that, unfortunately has not seen a commit in > almost 7 yea

Re: [Groff] Nesting font macros in man pages

At 2017-04-27T04:00:29+, Bjarni Ingi Gislason wrote: > On Mon, Apr 24, 2017 at 11:41:22AM -0400, G. Branden Robinson wrote: > > At 2017-04-24T16:22:37+0100, Ralph Corderoy wrote: > > > .SM affect the next input line as it uses an input trap, `.it'. `\c' > > > doesn't make an input line continu

Re: [Groff] Applications of \c in man pages in the wild

At 2017-04-27T14:30:33+0200, Ingo Schwarze wrote: > Hi, > > wow, you definitely demonstrate diligence in investigating existing > usage. [...] > That can be summarized as follows: Legitimate hand-written use is > almost inexistent, even hand-written abuse is very rare, but unusually > frequent wh

Re: [Groff] Nesting font macros in man pages

Hi, Steffen Nurpmeso wrote on Thu, Apr 27, 2017 at 02:21:10PM +0200: > You have a notion of "callable" and "parsed", and you should be > aware of that or you introduce errors which are hard to find. Wrong. Just assume everything is callable. Actually, mandoc warns if you use the name of a macr

Re: [Groff] Applications of \c in man pages in the wild

Hi, wow, you definitely demonstrate diligence in investigating existing usage. Let's have a look at the result. The only use cases that are (arguably) legitimate are FONT_MACRO_C, PRIVATE_FONT_MACRO_C, SMALL_C, and TILDE_C. Not counting the groff documentation itself (because that might be cons

Re: [Groff] Nesting font macros in man pages

"G. Branden Robinson" wrote: Sorry for answering so late, my daily routine has shifted to night again, almost sunset, and that really makes me frustrated. |At 2017-04-25T20:19:21+0200, Steffen Nurpmeso wrote: ... |>|> c. Show people a mapping from groff's "extended" man macro package to |>|

Re: [Groff] Nesting font macros in man pages

Hi, Bjarni Ingi Gislason wrote on Thu, Apr 27, 2017 at 04:00:29AM +: > On Mon, Apr 24, 2017 at 11:41:22AM -0400, G. Branden Robinson wrote: > > At 2017-04-24T16:22:37+0100, Ralph Corderoy wrote: >>> .SM affect the next input line as it uses an input trap, `.it'. `\c' >>> doesn't make an inpu