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 >>> .BI "int fstat(int " fd ", struct stat *" statbuf ); >>> .EE >> >> 3) >> >>> .EX >>> .BI "int fstat(int\~" fd ", struct stat *" statbuf ); >>> .EE >> >> I'd say number 2 is best. Rationale: grep :) >> I agree it's visually somewhat harder, but grepping is way easier. > > I don't see how (2) is any tougher to grep than (3)...? > > If I'm grepping, I'm usually concerned with things like > variable/function names and not with punctuation, so if I were grepping > for the above function signature I'd probably write: > > $ grep 'fstat.*fd.*statbuf' man2/* > > ...which would catch either of the above just fine. > > Am I missing something? > > Regards, > Branden > 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. Regards, Alex
