Hello,
and sorry for the late reply.
G. Branden Robinson wrote in
<20201101035740.2azpyoxgyrd6ozdl@localhost.localdomain>:
|Hi, Steffen. Coming back to an old item of business.
|
|At 2020-09-29T19:12:00+1000, G. Branden Robinson wrote:
|> At 2020-09-28T22:57:37+0200, Steffen Nurpmeso wrote:
Hi, Steffen. Coming back to an old item of business.
At 2020-09-29T19:12:00+1000, G. Branden Robinson wrote:
> At 2020-09-28T22:57:37+0200, Steffen Nurpmeso wrote:
> > Rereading the first messages of the thread ... i reiterated one of
> > Ingo's statements in fact.
>
> Yes, I think the earlier d
At 2020-09-28T22:57:37+0200, Steffen Nurpmeso wrote:
> G. Branden Robinson wrote in
> <20200927063701.vj6bg474km3ofpfh@localhost.localdomain>:
> |At 2020-09-16T01:21:14+0200, Steffen Nurpmeso wrote:
> |> I am all with Tadziu Hoffmann in this thread.
> |
> |Did Tadziu comment on this thread? I
G. Branden Robinson wrote in
<20200927063701.vj6bg474km3ofpfh@localhost.localdomain>:
|At 2020-09-16T01:21:14+0200, Steffen Nurpmeso wrote:
|> C64 had no login. And DMR would not have used it.
|> I am all with Tadziu Hoffmann in this thread.
|
|Did Tadziu comment on this thread? I don't see
At 2020-09-19T16:01:22-0500, Dave Kemper wrote:
> Straying away from man-page considerations and comparing these two
> approaches in general:
>
> The .string* requests also have the advantage of handling alphabetic
> Latin-1 characters and the roff escapes that represent them (though
> .stringup f
At 2020-09-16T01:21:14+0200, Steffen Nurpmeso wrote:
> C64 had no login. And DMR would not have used it.
> I am all with Tadziu Hoffmann in this thread.
Did Tadziu comment on this thread? I don't see any such message in the
list archive in my mail folder... :-?
> I see. For Ingo's mandoc it wi
On 9/15/20, G. Branden Robinson wrote:
> At 2020-09-16T00:13:30+1000, John Gardner wrote:
>> .if n \{\
>> .tr aAbBcCdDeEfFgGhHiIjJkKlLmMnNoOpPqQrRsStTuUvVwWxXyYzZ
>> \\$1
>> .tr aabbccddeeffgghhiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz
>> .\}
>
> Oh, no! I went to the trouble of implementing new reque
G. Branden Robinson wrote in
<20200915183356.3xt3ywitpzifixm2@localhost.localdomain>:
|At 2020-09-15T13:59:04+0200, Steffen Nurpmeso wrote:
|> Just out of interest: why do you change an omnipresent idiom that
|> is in use for standard section headers in Unix manual pages since
|> at least four
>
> Oh, no! I went to the trouble of implementing new requests
(.stringup, .stringdown) to keep people from having to type
(or copy and paste) messes like the above
Oops, I completely forgot we added that recently. My bad. :(
On Wed, 16 Sep 2020 at 04:34, G. Branden Robinson <
g.branden.robin
Hi, Steffen!
At 2020-09-15T13:59:04+0200, Steffen Nurpmeso wrote:
> Just out of interest: why do you change an omnipresent idiom that
> is in use for standard section headers in Unix manual pages since
> at least fourty years?
As Ingo noted, this was discussed on this list some time ago.
https
For output destined for terminal display, it's easy to uphold this
convention:
.if n \{\
.tr aAbBcCdDeEfFgGhHiIjJkKlLmMnNoOpPqQrRsStTuUvVwWxXyYzZ
\\$1
.tr aabbccddeeffgghhiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz
.\}
The important part is that the source argument be expressed using "proper"
capitalis
Hallo Ingo.
Ingo Schwarze wrote in
<20200915133505.gi1...@athene.usta.de>:
|Hi Steffen,
|
|Steffen Nurpmeso wrote on Tue, Sep 15, 2020 at 01:59:04PM +0200:
|
|> Just out of interest: why do you change an omnipresent idiom that
|> is in use for standard section headers in Unix manual pages s
Hi Steffen,
Steffen Nurpmeso wrote on Tue, Sep 15, 2020 at 01:59:04PM +0200:
> Just out of interest: why do you change an omnipresent idiom that
> is in use for standard section headers in Unix manual pages since
> at least fourty years? This commit changes the world and will
> affect the genera
13 matches
Mail list logo
