Red Hat Bugzilla – Bug 174983
comp calls "no" instead of "prompter"
Last modified: 2007-11-30 17:11:18 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7 Description of problem: with no editor: in .mh-profile, comp complains about a non-existent programme "no" Version-Release number of selected component (if applicable): nmh-1.1-11.fc4 How reproducible: Always Steps to Reproduce: 1.comp 2. 3. Actual Results: Outputs unable to exec no: No such file or directory and exits with 1 Expected Results: should run prompter and prompt with To: etc. Additional info: "comp -editor prompter" works as expected. Adding a line "editor: prompter" also works around the bug. Given that it searches the path for a programme called "no", if one were to exist, the effect would not be as I describe above. Could be far worse!
That should read 'Adding a line "editor: prompter" to one's .mh-profile also works around the bug.'
If you wish to solve the problem yourself, simply rebuilding the src.rpm on your system should work. I need to add a BuildRequires on /bin/vi (which should already exist on your running system, and be picked up properly during the build). I'll get some new packages into the build system later today.
rebuilding it did work, though it defaults to vi, which I try to avoid. Surely a default of prompter would be better? You wouldn't need a dependency on vi then.
vi is the nmh default, which I think is a good choice. Most users without much customization may be confused by prompter. I'm under the impression that if you're using prompter, you know enough to define which editor you wish to use. nmh-1.1-12.fc[345] is currently making its way through the extras build system, and I have fixed this issue upstream as well.