On Wed, Aug 04, 2004 at 09:30:12AM +0200, Simon L. Nielsen wrote: > On 2004.08.04 00:29:51 -0400, Rahul Siddharthan wrote: > > Evan Dower said on Aug 3, 2004 at 14:05:10: > > > >And it's worth noting that minor incompatibilities like this just > > > >serve to annoy new users (which usually means users from linux-land). > > > >For example, it's annoying that BSD man can't read a manpage by > > > >specifying the full path to a filename (eg, man ./foo.1). > > > > > > Yeah... Why is that? It seems like it would be awfully useful to read man > > > pages without installing them. > > > > I was wrong about calling it BSD man... it's GNU man, but a much older > > version than what current linux systems ship. > > > > I can work on a patch for this specific feature when I get some time. > > Before I start, is there any reason people may think this is a bad > > idea? > > Well, it can be done without a patch... I use the following tcsh alias > so I can just write 'manf foo.1' : > > groff -Wall -Tascii -te -mandoc !^ | less > You need to use ``-mtty-char -man'' to get the correct output. (-man or -mandoc doesn't matter.) Cheers, -- Ruslan Ermilov ru_at_FreeBSD.org FreeBSD committer
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:04 UTC