Red Hat Bugzilla – Bug 131977
'bashbug' command referred to but not present
Last modified: 2007-11-30 17:10:48 EST
Description of problem: In the bash man and info pages, and in bash's --help output, it is mentioned that bugs should be reported via a command called 'bashbug', but the command doesn't actually exist in the bash package. Version-Release number of selected component (if applicable): bash-3.0-9 Additional info: Running 'locate bashbug' on a recent full rawhide install reveals the following files: /usr/share/man/fr/man1/bashbug.1.gz/usr/share/man/ja/man1/bashbug.1.gz (man-pages-ja-20040815-1) /usr/share/man/fr/man1/bashbug.1.gz (man-pages-fr-0.9.7-10) If the bashbug utility won't be returning to the bash package, those packages should probably have bugs filed on them.
Uh, the 'following files' are really: /usr/share/man/ja/man1/bashbug.1.gz (man-pages-ja-20040815-1) /usr/share/man/fr/man1/bashbug.1.gz (man-pages-fr-0.9.7-10)
It's removed for multilib.
Building fixed bash package now.
OK, I have a bashbug-64 now. Not sure why it's called that, since it's a shell script, but hey. bashbug-64 spawns xemacs when run in X. Looking in the script, it tries 4 flavors of emacs before anything else that will normally exist. Personally I'm a vim user (not to start a flamewar, emacs genuinely confuses me), but maybe we could make, say, nano the default? Not everyone knows how to use either emacs or vi, but nano is a really easy-to-use editor.
It's easy for someone who doesn't like emacs to just use: EDITOR=vim bashbug
Ah, you're right. I should be exporting that anyway. Thanks :)