Re: cat.1 forward refs

2016-07-09 Thread Ted Unangst
Jason McIntyre wrote: > therefore the pattern is currently to say it explicitly. we could > do both, but that adds verbosity. it's a trade off, no? i wouldn;t > be against documenting both bits of information, but i'm not sure > it's really worth it. > > i think it'd be wrong to lose the info abou

Re: cat.1 forward refs

2016-06-26 Thread Jason McIntyre
On Sun, Jun 26, 2016 at 09:30:15PM -0400, Ted Unangst wrote: > I find it confusing to read a man page that constantly tells me that this > option is like some other option. I have to go read the other option, then > return here and reparse what's different. In my unimpeachable opinion, the > text f

cat.1 forward refs

2016-06-26 Thread Ted Unangst
I find it confusing to read a man page that constantly tells me that this option is like some other option. I have to go read the other option, then return here and reparse what's different. In my unimpeachable opinion, the text for each option should be self contained, with references to other opt