I propose to start a new file DISTRIBUTIONS in the top directory.
This file will report the maintainers of known distributions.
### DISTRIBUTIONS
OpenBSD - Ingo Schwarze
LinuxMint Debian - Keith Marshall
Debian - Colin Watson
I installed a groff file that I will use in several groff based
man-pages written by me. This is the file contrib/groffer/groffer.tmac
I let it install into the tmacdir.
But now I'm not sure, if this position or naming is correct.
Some idea about the naming and position?
Bernd Warken
On 03/07/14 15:50, Bernd Warken wrote:
> I propose to start a new file DISTRIBUTIONS in the top directory.
> This file will report the maintainers of known distributions.
>
> ### DISTRIBUTIONS
> OpenBSD - Ingo Schwarze
> LinuxMint Debian - Keith Marshall
I am NOT the maintainer of the Linux
Hi Bernd,
Bernd Warken wrote on Thu, Jul 03, 2014 at 04:50:00PM +0200:
> I propose to start a new file DISTRIBUTIONS in the top directory.
> This file will report the maintainers of known distributions.
I'm not opposed to doing that, even though keeping such a list
up to date can be tedious, and
Hello,
(may be off topic)
Why is \} (end of conditional block) considered as a macro argument regarding
the register .$ ?
It may not be best style, but often \} is written behind the last request of a
block. There are warnings for doing this for requests like e.g. .ds, but that
it also increas
Hi Bernd,
Bernd Warken wrote on Thu, Jul 03, 2014 at 06:11:49PM +0200:
> I installed a groff file that I will use in several groff based
> man-pages written by me.
This is a very, very bad idea.
Do not gratuitiously extend the man(7) language.
Actually, that has repeatedly been discussed to deat
Hi Carsten,
Carsten Kunze wrote on Thu, Jul 03, 2014 at 09:11:09PM +0200:
> (may be off topic)
I consider your question perfectly on topic.
> Why is \} (end of conditional block) considered as a macro argument
> regarding the register .$ ?
That looks like a miniature bug to me.
> It may not b
Hi Ingo,
> I consider your question perfectly on topic.
It could unfortunately be off topic in case it is not a groff issue. Heriloom
and Plan 9 have the same behavior. So it could even be possible that this has
also been the case when these conditional blocks had been introduced (roff? 1st
nr
> Von: "Ingo Schwarze"
>
> Delete it outright, and fix the formatting of your documentation
> to use one of the standard ways, please. You are free to choose
> man(7) or mdoc(7), both are available in any modern groff installation.
> You can even use man-ext if you like it (I don't, but opinion
> Why is \} (end of conditional block) considered as a macro argument
> regarding the register .$ ? It may not be best style, but often \}
> is written behind the last request of a block. There are warnings
> for doing this for requests like e.g. .ds, but that it also
> increases .$ is not expec
> > Why is \} (end of conditional block) considered as a macro argument
> > regarding the register .$ ? It may not be best style, but often \}
> > is written behind the last request of a block. There are warnings
> > for doing this for requests like e.g. .ds, but that it also
> > increases .$ is n
>> Please file a bug report so that your question doesn't get lost.
>
> I am not really sure if it would be correct to fix it. It could have
> been a bug in old nroff versions but then it could have been
> intended by the groff author to copy that bug exactly (which I do
> would consider as corre
> In case it's intentional it should be documented...
Yes, that's correct! So I'll report the issue with that note.
--Carsten
13 matches
Mail list logo
