I've been playing with fish, and it's pretty cool, but there are some problems with the packaging.
When you install fish, it wants to install 63 manpages. Of those, 29 have the same name as manpages (or symlinks) that come with bash. Because of this, most of the packages I've seen just skip these manpages; some instead conflict with bash, making them useless. Oliver Falk's RPM for Fedora 8 excludes 29 manpages; Dag Wieers' RPM for RHEL5 excludes 54; the old Fedora 7 RPM couldn't be installed because it tried to overwrite files owned by bash. This is an ages-old problem for any non-standard shell-every shell does something slightly different for while, and they all want to have manpages for it, so "man pushd" generally ends up showing the manpage for the system's default shell, not the one for your current shell. And nobody wants to read bash-builtins.1 to find about about fish's pushd. I can think of two solutions, but they both somewhat suck. What I do locally is install the manpages to some place like /usr/local/share/fish/man/man1, then have fish.config add this to the MANPATH (and likewise for zsh and other shells). But MANPATH is bad, and this isn't the kind of thing a general-purpose package is going to want to do. Oliver Falk suggested renaming both the tools/scripts and their associated manpages to have fish pre-/postfixed to them. Your fish.config could set up functions to alias pushd to fish-pushd, etc. Then add a man-wrapper function that turns man pushd into man fish-pushd, and you're done. But it's pretty ugly. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
