Hi Ingo,
On 3/20/22 10:48, Ingo Schwarze wrote:
> Hi Alex,
It seems your emails didn't reach me directly.
But the email from the mailing list arrived to my other mailbox.
Hummm.
After that, I checked again, and I found your email in the SPAM folder...
#$%* gmail!
> Alejandro Colomar (man-pages)
Hi Branden,
On 3/20/22 18:43, G. Branden Robinson wrote:
> At 2022-03-20T13:57:18+0100, Ingo Schwarze wrote:
>> To summarize, i certainly wouldn't want to warn about these
>> mini-issues in mandoc -T lint. Admittedly, warnings in groff accept a
>> significantly higher rate of noise and false posi
At 2022-03-20T13:57:18+0100, Ingo Schwarze wrote:
> To summarize, i certainly wouldn't want to warn about these
> mini-issues in mandoc -T lint. Admittedly, warnings in groff accept a
> significantly higher rate of noise and false positives than in mandoc
> -T lint,
Excuse me? If you are referri
Hi, Branden!
On 3/20/22 15:07, G. Branden Robinson wrote:
> Hi, Alex!
>
> At 2022-03-19T17:07:09+0100, Alejandro Colomar (man-pages) wrote:
>> While fixing style issues in the man-pages project,
>> I'm finding a few recurrent issues that I think you could warn about:
>>
>> Unnecessary quotations:
Hi Ingo,
At 2022-03-20T12:41:28+0100, Ingo Schwarze wrote:
> G. Branden Robinson wrote on Sun, Mar 20, 2022 at 09:52:37PM +1100:
> > If you wanted to write this without using any aliases,
> > you could adopt groff syntax.
> >
> > +to "\fI[a\[a aa]\[a ga]\[a ad]\[a a^]\fP", that is,
>
> While tha
Hi, Branden!
On 3/20/22 11:52, G. Branden Robinson wrote:
>
> Sure! The punctuation does get a bit bewildering.
>
[...]
Thanks for the great explanation!
>
> Now, for the part people actually care about, which is how to fix it:
> take the escape character off of that `.
>
> You thus want
>
At 2022-03-20T10:48:56+0100, Ingo Schwarze wrote:
> > When a double-quoted word is not space-separated from an adjacent
> > word, it's not considered a different argument _except_ if if is the
> > first argument.
>
> That description is inaccurate. It has nothing to do with whether
> or not it is
Hi, Branden!
On 3/20/22 10:36, G. Branden Robinson wrote:
> At 2022-03-20T01:29:32+0100, Alejandro Colomar (man-pages) wrote:
> Ralph's description, as I parse it, is correct. I'll speak to the
> broader issue of documentation coverage of the matter.
>
>> Could you please improve the documentati
At 2022-03-20T12:59:38+0100, Ingo Schwarze wrote:
> But since modern manual pages are mostly written and maintained
> by people used to younger languages, i still think the following
> advice is useful to avoid confusion of modern manual page maintainers:
> If you quote a macro argument, always pro
Hi Ralph,
On 3/20/22 09:32, Ralph Corderoy wrote:
> Hi Alex,
>
> - If an argument starts with a " then it ends at the next " which isn't
> the start of a "" or at the end of the line if there isn't a single ".
> - If an argument does not start with a " then the " within it are
> literal and t
Hi, Alex!
At 2022-03-19T17:07:09+0100, Alejandro Colomar (man-pages) wrote:
> While fixing style issues in the man-pages project,
> I'm finding a few recurrent issues that I think you could warn about:
>
> Unnecessary quotations:
>
> [
> .I "foo bar"
> .IR foo "bar"
> ]
That is going to be hard
Hi Alex,
Alejandro Colomar (man-pages) wrote on Sat, Mar 19, 2022 at 05:07:09PM +0100:
> While fixing style issues in the man-pages project,
> I'm finding a few recurrent issues that I think you could warn about:
>
> Unnecessary quotations:
>
> [
> .I "foo bar"
> .IR foo "bar"
> ]
In how far a
Hi Ralph,
Ralph Corderoy wrote on Sun, Mar 20, 2022 at 10:06:14AM +:
> Ingo Schwarze wrote:
>> but the roff(7) manual in the mandoc package says this:
> ...
>> Leaving out the terminating double quote character at the end of
>> the line is discouraged.
> I think that's idiomatic and
Hi Branden, hi Alex,
G. Branden Robinson wrote on Sun, Mar 20, 2022 at 09:52:37PM +1100:
> If you wanted to write this without using any aliases,
> you could adopt groff syntax.
>
> +to "\fI[a\[a aa]\[a ga]\[a ad]\[a a^]\fP", that is,
While that is arguably neat, please be aware that it is sign
Hi, Alex!
At 2022-03-20T01:04:17+0100, Alejandro Colomar (man-pages) wrote:
> Michael introduced the following commit, which is incorrect (triggers
> a groff(1) error; see below). Do you know what is intended here?
> Could you please propose a fix?
Sure! The punctuation does get a bit bewilderi
Hi Ingo,
> but the roff(7) manual in the mandoc package says this:
...
> Leaving out the terminating double quote character at the end of
> the line is discouraged.
I think that's idiomatic and an early thing one learns about troff's
‘strings’ compared to programming languages in order to
Hi Alex,
Alejandro Colomar (man-pages) wrote on Sun, Mar 20, 2022 at 01:29:32AM +0100:
> I've met some undocumented (or I couldn't find it) behavior
> of double quotes ("),
I did not check the authoritative GNU troff documentation yet,
but the roff(7) manual in the mandoc package says this:
M
At 2022-03-20T01:29:32+0100, Alejandro Colomar (man-pages) wrote:
> Hi Branden,
>
> I've met some undocumented (or I couldn't find it) behavior of double
> quotes ("), which might be a bug in groff(1):
Hi Alex!
Ralph's description, as I parse it, is correct. I'll speak to the
broader issue of d
Hi Alex,
- If an argument starts with a " then it ends at the next " which isn't
the start of a "" or at the end of the line if there isn't a single ".
- If an argument does not start with a " then the " within it are
literal and the argument ends just before the next space or the end of
the
19 matches
Mail list logo
