Code: Select all
# exec defaulthtmlviewer http://linux.die.net/man/${1}
exec defaulthtmlviewer "http://www.google.com/search?&q=man+\"${1}\"+site:linux.die.net&btnI=Search"
Code: Select all
~ > man --help
man, version 1.6e
usage: man [-adfhktwW] [section] [-M path] [-P pager] [-S list]
[-m system] [-p string] name ...
a : find all matching entries
c : do not use cat file
d : print gobs of debugging information
D : as for -d, but also display the pages
f : same as whatis(1)
h : print this help message
k : same as apropos(1)
K : search for a string in all pages
t : use troff to format pages for printing
w : print location of man page(s) that would be displayed
(if no name given: print directories that would be searched)
W : as for -w, but display filenames only
C file : use `file' as configuration file
M path : set search path for manual pages to `path'
P pager : use program `pager' to display pages
S list : colon separated section list
m system : search for alternate system's man pages
p string : string tells which preprocessors to run
e - [n]eqn(1) p - pic(1) t - tbl(1)
g - grap(1) r - refer(1) v - vgrind(1)The mind boggles as to why. I can't think of a single good reason. I can think of some fairly ordinary reasons.8-bit wrote:I was just wondering why the original binary man file was replaced by a script file.
Code: Select all
#! /bin/bash
defaulthtmlviewer "http://www.google.com/search?&q=man+"$1"+site:linux.die.net&btnI=Search"Code: Select all
# man --help
man for puppy linux - 09 Dec 2009
If you like to use original version of man, try '/usr/local/man'.
usage: man [section] nameCode: Select all
# nroff -mandoc -c manpage.n | lessGroff itself is a whole 50K on my Puppy 4.31 installation. There are other external components it may call, but for most cases, just groff is sufficient.amigo wrote:I guess Puppy users could have it both ways. groff is a large set of programs, so having man installed also should not be a burden compared to the size of groff. then, they could simply change the name of the man program to 'real-man' -hehe.
I started using Unix with AT&T System V Release 2 in the 80's, when Linux wasn't a gleam in Linus Torvald's eye. I've been accustomed to typing "man <command>" at a shell prompt and getting a locally installed man page in response. When I first installed Puppy, I said "WTF?". The man command was replaced by a script that tried to pop up a browser to view local HTML documentation, and if it wasn't there, tried to go out the the internet to display a man page in the browser from an external site.Leaving out man-pages is forgivable, if unwise, but leaving out the License/Copying/Copyright files is illegal in most places. And doing it anyway is quite against the open-source principles. People who distribute binaries without making the sources available and including the License should be forced to use Winblows freeware/shareware/proprietary stuff for a while -or they should put in soke months of hard work on a source-based program and release it with a free license (and no other restrictions) and then see how they feel when others distribute their code without including their License/copyright or alter the sources and claim it as their own work....
Yes auriza.auriza wrote:I just want to share the fact that I know in Puppy 4.3.1:
- man command in Puppy is a script
- it searches for html files in /usr/share/doc and it's subdirectories
(e.g. if you type "man abiword" will open-up a browser showing /usr/share/doc/abiword.html)
- if you want to include manpage in your package, convert it to html with man2html command and place it to /usr/share/doc
- if you want to see those converted html manual page in console, you can edit the man script to change the browser to w3m, elinks, etc