Re: FVWM website: WAS: [Re: FVWM code moved to Github]

2016-04-04 Thread Jason L Tibbitts III
> "JS" == Jaimos Skriletz writes: JS> So to complete the switch the fvwm.org domain needs to be pointed JS> at/redirected to github.io. That's easy for me to do, but before I make any changes. JS> I think pointing fvwm.org at github would be preferable as

Re: FVWM website: WAS: [Re: FVWM code moved to Github]

2016-04-04 Thread Jaimos Skriletz
On Mon, Apr 4, 2016 at 11:31 AM, Jason L Tibbitts III wrote: > > "JS" == Jaimos Skriletz writes: > > JS> So to complete the switch the fvwm.org domain needs to be pointed > JS> at/redirected to github.io. > > That's easy for me to do, but

Re: FVWM website: WAS: [Re: FVWM code moved to Github]

2016-04-04 Thread Thomas Adam
On Mon, Apr 04, 2016 at 11:56:47AM -0600, Jaimos Skriletz wrote: > https://help.github.com/articles/using-a-custom-domain-with-github-pages/ > https://help.github.com/articles/setting-up-your-pages-site-repository/ I say we trial this, as it's the simplest change, without additional overhead, and

RFH: manpages in markdown

2016-04-04 Thread Thomas Adam
Hi all, I've started to look at moving away from using docbook for man page generation, and instead using markdown as the base format which can then be converted to nroff and HTML, etc. Using markdown for this seems sensible---using just nroff (or my preference, mdoc) is one solution, but not as