On 9/27/20 10:05 PM, Alejandro Colomar wrote:
> Hi Branden,
>
> * G. Branden Robinson via linux-man:
>
> 1)
>
> > .EX
> > .B int fstat(int \c
> > .IB fd , \~\c
> > .B struct stat *\c
> > .IB statbuf );
> > .EE
>
> 2)
>
> > .EX
> > .BI "int fstat(int " fd ", struct stat *" statbuf );
>
Hi Branden,
On 9/27/20 7:46 AM, G. Branden Robinson wrote:
> At 2020-09-24T10:06:23+0200, Michael Kerrisk (man-pages) wrote:
>> Thanks for the interesting history, Branden!
>
> Hi, Michael. And you're welcome! I often wonder if I test people's
> patience with my info dumps but I try to show my
On 2020-09-28 15:48, G. Branden Robinson wrote:
>> There are a few cases: if I want to find declarations of type int,
>> I'd start with:
>>
>> $ grep -rn "int\s"
>>
>> or something like that. "int\~" would break the ability to do that.
>
> That would, among more obscure cases, miss the style
From: Alejandro Colomar
> Sent: 28 September 2020 14:33
...
> There are a few cases: if I want to find declarations of type int,
> I'd start with:
>
> $ grep -rn "int\s"
>
> or something like that. "int\~" would break the ability to do that.
The 'word markers' \< and \> are your friends; look
At 2020-09-28T15:33:21+0200, Alejandro Colomar wrote:
> On 2020-09-28 14:52, G. Branden Robinson wrote:
> > At 2020-09-27T22:05:14+0200, Alejandro Colomar wrote:
> >> 2)
> >>
> >>> .EX
> >>> .BI "int fstat(int " fd ", struct stat *" statbuf );
> >>> .EE
> >>
> >> 3)
> >>
> >>> .EX
> >>> .BI "int
On 2020-09-28 14:52, G. Branden Robinson wrote:
> At 2020-09-27T22:05:14+0200, Alejandro Colomar wrote:
>> Hi Branden,
>>
>> * G. Branden Robinson via linux-man:
>>
>> 1)
>>
>>> .EX
>>> .B int fstat(int \c
>>> .IB fd , \~\c
>>> .B struct stat *\c
>>> .IB statbuf );
>>> .EE
>>
>> 2)
>>
>>> .EX
At 2020-09-27T22:05:14+0200, Alejandro Colomar wrote:
> Hi Branden,
>
> * G. Branden Robinson via linux-man:
>
> 1)
>
> > .EX
> > .B int fstat(int \c
> > .IB fd , \~\c
> > .B struct stat *\c
> > .IB statbuf );
> > .EE
>
> 2)
>
> > .EX
> > .BI "int fstat(int " fd ", struct stat *" statbuf );
>
Hi Branden,
* G. Branden Robinson via linux-man:
1)
> .EX
> .B int fstat(int \c
> .IB fd , \~\c
> .B struct stat *\c
> .IB statbuf );
> .EE
2)
> .EX
> .BI "int fstat(int " fd ", struct stat *" statbuf );
> .EE
3)
> .EX
> .BI "int fstat(int\~" fd ", struct stat *" statbuf );
> .EE
I'd say
At 2020-09-24T10:06:23+0200, Michael Kerrisk (man-pages) wrote:
> Thanks for the interesting history, Branden!
Hi, Michael. And you're welcome! I often wonder if I test people's
patience with my info dumps but I try to show my work when making
claims.
> From time toi time I wonder if the
Hi Branden,
On 9/21/20 4:36 PM, G. Branden Robinson wrote:
> At 2020-09-11T12:58:08+, Walter Harms wrote:
>> the groff commands are ducument in man 7 groff
>> .nf No filling or adjusting of output-lines.
>> .fi Fill output lines
>>
>> (for me) a typical use is like this:
>> .nf
>>
At 2020-09-11T12:58:08+, Walter Harms wrote:
> the groff commands are ducument in man 7 groff
> .nf No filling or adjusting of output-lines.
> .fi Fill output lines
>
> (for me) a typical use is like this:
> .nf
>
> struct timeval {
> time_t tv_sec; /* seconds */
>
On 9/10/20 11:13 PM, Alejandro Colomar wrote:
> Notes: I copied .nf and .fi from futex.2, but they made no visual difference.
> What do they actually do?
>
> Signed-off-by: Alejandro Colomar
Thanks, Alex. Patch applied.
Cheers,
Michael
> ---
> man2/membarrier.2 | 9 +
> 1 file
12 matches
Mail list logo
