Re: [xmonad] Issue 551 in xmonad: XMonad.Prompt.Man.manPrompt uses `manpath -g`, -g appears to be an invalid option

Updates: Status: Fixed Comment #4 on issue 551 by vogt.a...@gmail.com: XMonad.Prompt.Man.manPrompt uses `manpath -g`, -g appears to be an invalid option http://code.google.com/p/xmonad/issues/detail?id=551 I don't have a system with the other man to test, but it works if one of the two calls to getCommandOutput gives an empty String: Mon Jul 15 23:05:36 EDT 2013 Adam Vogt * Fix issue 551 by also getting manpath without -g flag. Instead of taking Ondrej's approach of figuring out which man (man-db or http://primates.ximian.com/~flucifredi/man/) is used by the system, just try both sets of flags. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

Comment #5 on issue 551 by ondrej.g...@gmail.com: XMonad.Prompt.Man.manPrompt uses `manpath -g`, -g appears to be an invalid option http://code.google.com/p/xmonad/issues/detail?id=551 Until this fix gets into a release, here's a simple workaround that does not require hacking XMonad in any way: Put the attached manpath script into your private script directory in your PATH (it must precede the original manpath) and make it executable Example: 1. put it in ~/bin/ (`mkdir -p ~/bin; mv ~/Downloads/manpath ~/bin/`) and make it executable (`chmod a+x ~/bin/manpath`) 2. put 'export PATH="~/bin:${PATH}"' in your ~/.bashrc (`echo 'export PATH="~/bin:${PATH}"' >> ~/.bashrc`) Attachments: manpath 454 bytes -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings
participants (1)
-
codesite-noreply@google.com