Hi Branden,
G. Branden Robinson wrote on Tue, Dec 11, 2018 at 07:31:35PM -0500:
> At 2018-12-11T18:44:50+0100, Ingo Schwarze wrote:
>> So i think there are good reasons for avoiding ASYNCHRONOUS EVENTS.
>> It certainly isn't a standard section in manual pages.
> I think your argument has merit,
Hi Branden,
G. Branden Robinson wrote on Tue, Dec 11, 2018 at 06:52:34PM -0500:
> At 2018-12-11T17:42:49+0100, Ingo Schwarze wrote:
>> I fully agree that less(1) is essential for man(1) display.
>> Not only because it allows moving backwards, but even more so
>> because it allows searching in cta
At 2018-12-11T18:44:50+0100, Ingo Schwarze wrote:
> POSIX provides a technical standard, not documentation; only some
> parts of the form happens to be similar to manual pages, but not
> the purpose, structure, or conventions.
This is true, and yet I feel I perceive more parallels than you do.
How
At 2018-12-11T18:14:11+0100, Ingo Schwarze wrote:
> A small patch clarifying, within the manual page itself, what the manual
> page is, and what it is not, as far as Peter thinks that is useful and
> currently lacking, would be OK before release, i think,
I'm happy to defer whatever Peter and Bert
At 2018-12-11T17:42:49+0100, Ingo Schwarze wrote:
> Hi Branden,
Hello again!
> G. Branden Robinson wrote on Tue, Dec 11, 2018 at 10:11:02AM -0500:
> I fully agree that less(1) is essential for man(1) display.
> Not only because it allows moving backwards, but even more so
> because it allows sear
At 2018-12-11T23:13:00+0100, Bertrand Garrigues wrote:
> On your local repo, you should be able to re-order the list of your
> commits with:
>
> git rebase -i HEAD~
Yup, I've done an interactive rebase before. :)
> and then moving the "pick " lines to place the wanted commit at the
> bott
On Tue, Dec 11 2018 at 11:13:00 PM, Bertrand Garrigues
wrote:
> Hi Branden,
>
> On Mon, Dec 10 2018 at 05:55:10 PM, "G. Branden Robinson"
> wrote:
>> At 2018-12-10T23:24:50+0100, Bertrand Garrigues wrote:
>>> You can push no_more_makefile.comm.diff. As Peter has just modified the
>>> texinfo
Hi Branden,
On Mon, Dec 10 2018 at 05:55:10 PM, "G. Branden Robinson"
wrote:
> At 2018-12-10T23:24:50+0100, Bertrand Garrigues wrote:
>> You can push no_more_makefile.comm.diff. As Peter has just modified the
>> texinfo doc by refering to "Collection of Installation Directories" that
>> you pat
Branden --
On Tue, Dec 11, 2018, G. Branden Robinson wrote:
> I'm happy to aid with the maintenance of groff_mom(7), as my
> predilections and neuroses seem to have led me to stumble into an
> unofficial role as a groff man page editor, but a synoptic view of
> mom is beyond my current competence.
On Tue, Dec 11, 2018, Ingo Schwarze wrote:
> At this point, i think the full cleanup Peter intends to do is
> better delayed until after release.
Agreed. IIRC--I'm too lazy to look--I started the thread by saying
it was a low priorty issue. :)
> A small patch clarifying, within the manual page
Hi,
G. Branden Robinson wrote on Tue, Dec 11, 2018 at 08:58:28AM -0500:
> At 2018-12-05T12:35:12+0100, Ulrich Lauther wrote:
>> In my opinion, a man page should contain (at most) NAME, SYNOPSIS,
>> COPYRIGHT, DESCRIPTION, OPTIONS, ARGUMENTS, INVOCATION, but not
>> LANGUAGE.
> I'm going to have c
Hi,
all of the below seems very well said to me.
I managed to delay my reply to Peter's thorough explanation of his
design of mom and its documentation sufficently to let the thread
become somewhat stale. As Branden alluded in his other mail, some
degree of arguing past each other may also be in
Hi Branden,
G. Branden Robinson wrote on Tue, Dec 11, 2018 at 10:11:02AM -0500:
> At 2018-11-30T14:18:05-0500, Peter Schaffter wrote:
>> My phrasing is at fault. By "isn't an improvement," I meant to
>> convey that alpabetic arrangement of the macros diminishes the
>> usefulness of such a list,
At 2018-11-30T14:18:05-0500, Peter Schaffter wrote:
> My phrasing is at fault. By "isn't an improvement," I meant to
> convey that alpabetic arrangement of the macros diminishes the
> usefulness of such a list, which benefits from being grouped into
> categories.
At the risk of being unfair to In
At 2018-12-01T09:27:03-0500, Doug McIlroy wrote:
> Software that inherently defies concise description is suspect on
> its face.
Ingo made a similar point not long ago when he and I were arguing past
each other.
I agree with this--such a property is definitely grounds for suspicion,
_but_...
> I
At 2018-11-29T21:57:27-0500, Peter Schaffter wrote:
> I revisited groff_mom(7) recently. I didn't write it and I've
> always felt it was there for the sake of completeness. I'd
> like to revise it, scrapping the alphabetic listing of macros and
> strings entirely. All it does is partially duplic
At 2018-12-11T15:20:45+0100, Werner LEMBERG wrote:
> > I only mention this because it's an error that has crept into our
> > documentation before (and which I've fixed).
> >
> > "Cf." means "compare" (Latin: "confere"). People seem to use it as if
> > it were a synonym of "q.v." ("quod vide" -> *
>> Cf. this message on the TeXLive mailing list.
>>
>> https://tug.org/pipermail/tex-live/2018-November/042697.html
>
> I only mention this because it's an error that has crept into our
> documentation before (and which I've fixed).
>
> "Cf." means "compare" (Latin: "confere"). People seem t
At 2018-12-05T12:35:12+0100, Ulrich Lauther wrote:
> Peter, I couldn't agree more to what you are saying.
>
> In my opinion, a man page should contain (at most) NAME, SYNOPSIS,
> COPYRIGHT, DESCRIPTION, OPTIONS, ARGUMENTS, INVOCATION, but not
> LANGUAGE.
I'm going to have come out against this.
At 2018-12-03T06:27:35+0100, Werner LEMBERG wrote:
> > Sounds interesting, but what is it exactly? I've skimmed through
> > his home page (https://www.math.utah.edu/~beebe/) but haven't seen
> > any mention of that.
>
> Cf. this message on the TeXLive mailing list.
>
> https://tug.org/pipermai
20 matches
Mail list logo
