View previous topic :: View next topic |
Author |
Message |
edit_21 Tux's lil' helper
Joined: 19 Nov 2004 Posts: 110
|
Posted: Sat Feb 26, 2005 7:04 pm Post subject: when doing a man command all i see is code! help! |
|
|
Hi all
as it says above if i do a man command like 'man emerge' or whatever , i just get pages of code, nothing ilegable, i stll can do a Q to quit so the codings there but the txt isnt formatted ?
Can anybody shead any light on this pls .
kernel 2.6.10-r4
Thanks
ed21 |
|
Back to top |
|
|
ecoffey Tux's lil' helper
Joined: 16 Jun 2004 Posts: 122 Location: Colorado
|
Posted: Sat Feb 26, 2005 8:26 pm Post subject: |
|
|
what do you mean by 'code'?
maybe a small little post to see what you're talking about? |
|
Back to top |
|
|
vinky Apprentice
Joined: 24 Feb 2005 Posts: 214 Location: Sweden
|
Posted: Sat Feb 26, 2005 8:32 pm Post subject: |
|
|
I have the same problem and its just a lot of unlogic tokens
I think I see somekind of error before the "code" appears but it goes too fast |
|
Back to top |
|
|
ecoffey Tux's lil' helper
Joined: 16 Jun 2004 Posts: 122 Location: Colorado
|
Posted: Sat Feb 26, 2005 8:58 pm Post subject: |
|
|
try this:
Code: | man emerge > /dev/null 2> man.error |
this way all the unintelligible code gets redirected to /dev/null and any errors are redirected to the file man.error
and then post that here |
|
Back to top |
|
|
vinky Apprentice
Joined: 24 Feb 2005 Posts: 214 Location: Sweden
|
Posted: Sat Feb 26, 2005 9:45 pm Post subject: |
|
|
get warnings like:
<standard input>:2: warning: can´t find character with input code 2
and
<standard input>:2: warning [p 1, 0.0i]: cannot adjust line
and
<standard input>:2: warning: numeric token expected (got o) |
|
Back to top |
|
|
ecoffey Tux's lil' helper
Joined: 16 Jun 2004 Posts: 122 Location: Colorado
|
Posted: Sat Feb 26, 2005 10:01 pm Post subject: |
|
|
wtf....
what shell are you using? i don't think i've ever seen those warnings.
the point is that 2> redirects standard error while > redirects standard out, so if you can figure out how to do that... |
|
Back to top |
|
|
Earthwings Bodhisattva
Joined: 14 Apr 2003 Posts: 7753 Location: Germany
|
Posted: Sun Feb 27, 2005 1:14 am Post subject: |
|
|
Moved from Installing Gentoo. |
|
Back to top |
|
|
ebrostig Bodhisattva
Joined: 20 Jul 2002 Posts: 3152 Location: Orlando, Fl
|
Posted: Sun Feb 27, 2005 1:48 pm Post subject: |
|
|
Try the following:
Code: |
export MANPAGER="col -b | view -c 'set ft=man nomod nolist' -"
|
Then do 'man something' and your manpage is now shown formatted in vi and you can page up and down and use search function to find whatever you like. Much better than the default behaviour of man.
Erik _________________ 'Yes, Firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.' |
|
Back to top |
|
|
vinky Apprentice
Joined: 24 Feb 2005 Posts: 214 Location: Sweden
|
Posted: Tue Mar 01, 2005 11:10 pm Post subject: |
|
|
Well that didn´t help me at all
now it exited with:
...
<standard input>:8: warning [p 1, 4.8i]: can´t break line
Error executing formatting pr display command.
System command (cd /usr/share/man && (echo ".pl 1100i"; /bin/cat '/usr/share/man/man1/tar.1.gz'; echo ".\\\"";echo ".pl \n(nlu+10") | /usr/bin/gtbl | /usr/bin/nroff -Tascii -c -mandoc | col -b | view -c 'set ft=man nomod nolist' -) exited with status 127.
No manual entry for tar |
|
Back to top |
|
|
jkonami n00b
Joined: 09 Jul 2003 Posts: 34 Location: Baltimore
|
Posted: Fri Jun 10, 2005 2:39 pm Post subject: |
|
|
Code: |
export MANPAGER="col -b | view -c 'set ft=man nomod nolist' -"
|
This doesn't work for me either, looks like it starts evaluating all the words in the man page? Here's what it did for me:
Code: |
$ man man
Visual needs addressible cursor or upline capability
man: Not an editor command
No lines in the buffer
tbl: Not an editor command
writable: Not an editor command
For: Not an editor command
M: Not an editor command
The: Not an editor command
|
I see this string be used all over the board (same syntax and all) and I'm not sure why it won't work for me. I'm really interested in making it work, any suggestions? |
|
Back to top |
|
|
jkonami n00b
Joined: 09 Jul 2003 Posts: 34 Location: Baltimore
|
Posted: Fri Jun 10, 2005 3:50 pm Post subject: |
|
|
I updated to the latest version of vim and now it works. |
|
Back to top |
|
|
|