RE: Way kewl new bug reportin thingy for 31337 XEmacs h4x0r d00dz

Steve Youngs writes: I like the new bug report format, but wonder if including the users's .emacs file might be going a bit too far. Some people might have plaintext passwords in this file (e.g. in setting the variable `vm-spool-files' for POP access). Admittedly storing plaintext passwords in your .emacs file isn't a great idea, but people may not realize that when they file a bug report their .emacs file is going to get broadcast not only to the mailing list but also archived in the mailing list archives, where it can be read by anybody on the Wild Wild Web... Another thought - we are constantly plagued by people reporting dired and efs bugs to the main list, which always generates the pedantic replies "Please use dired-report-bug" or "Please use efs-report-bug". It would be really great if there were a single function for bug reporting. While it would take a lot to try to determine (either from the backtrace or from the user's description) whether the bug was a dired bug, an efs bug, or an "other" bug, maybe at the very least the new bug report template could include some wording, preferably right near the top, saying: "If this is a bug in the FOO package, please use FOO-report bug; if this is a bug in the BAR package, please use BAR-report bug, else use this bug report form". Daydreaming a bit, one could imagine a "hook" system where different packages added to the report-bug-hook, thereby obviating the need for N different FOO-report-bug functions.... but this sounds like work. Including a bit of text in the template would be easy and would eliminate some amount of frustration.