Re: [groff] Now online: gropdf / grops previewer

Thanks for the kind words! =) > this previewer is only a part of the online troff > editor you are working on isn't it? Ah no, it's not an online, interactive version of Troff, if that's what you're thinking. =) It's an extension for a text editor named Atom , which is like

Re: [groff] groff as the basis for comprehensive documentation?

Hi Ralph, Ralph Corderoy wrote on Wed, Apr 25, 2018 at 05:00:01PM +0100: > Ingo Schwarze wrote: >> I work on mdoc(7) manual pages a lot, and i almost never look at any >> kind of output to see whether the final formatting comes out in the >> desired visual form. While writing, i exclusively

Re: [groff] groff as the basis for comprehensive documentation?

On Wed, Apr 25, 2018 at 10:49:25PM +0100, Ralph Corderoy wrote: > Subject: Re: [groff] groff as the basis for comprehensive documentation? > > > When I write, I only want to think about the words on the screen and > > the structure of my argument > > And when you've finished writing, do you not

Re: [groff] groff as the basis for comprehensive documentation?

Hi Steve, > When I write, I only want to think about the words on the screen and > the structure of my argument And when you've finished writing, do you not look at an output and spot problems due to concentrating on the content? It's also troff input, e.g. `.\&', and although that shouldn't

Re: [groff] groff as the basis for comprehensive documentation?

On Wed, Apr 25, 2018 at 03:58:33PM -0400, Steve Izma wrote: > When I write, I only want to think about the words ... > and the structure of my argument ... May I add a big Amen! -- Mike Bianchi

Re: [groff] groff as the basis for comprehensive documentation?

On Wed, Apr 25, 2018 at 05:00:01PM +0100, Ralph Corderoy wrote: > Subject: Re: [groff] groff as the basis for comprehensive documentation? > > > I work on mdoc(7) manual pages a lot, and i almost never look at any > > kind of output to see whether the final formatting comes out in the > > desired

Re: [groff] groff as the basis for comprehensive documentation?

Hi Ingo, > I work on mdoc(7) manual pages a lot, and i almost never look at any > kind of output to see whether the final formatting comes out in the > desired visual form. While writing, i exclusively think about the > logical structure of the text and the semantic function of each word > and

[groff] 02/03: pic2graph(1): Document -v option.

gbranden pushed a commit to branch master in repository groff. commit 720a45e7dda716a6e295cf4176d5a5b69811318d Author: G. Branden Robinson Date: Wed Apr 25 09:20:51 2018 -0400 pic2graph(1): Document -v option. Also use .SY more idiomatically when

[groff] 01/03: pic2graph: Handle embedded whitespace in temp dir.

gbranden pushed a commit to branch master in repository groff. commit 266bf8ff4f80024710462d6996cae2db97406c3b Author: G. Branden Robinson Date: Wed Apr 25 00:34:44 2018 -0400 pic2graph: Handle embedded whitespace in temp dir.

[groff] 03/03: pic2graph: Refactor temp directory handling.

gbranden pushed a commit to branch master in repository groff. commit b1cd3b77a48f56c319b8642234f39b21e260e0c3 Author: G. Branden Robinson Date: Wed Apr 25 10:18:44 2018 -0400 pic2graph: Refactor temp directory handling.