CW> I'm sure I've asked you this before, but once again: please stop filing CW> bugs against man-db about warning messages on individual manual pages.
Ah no wonder: CW> man-db (2.5.0-1) unstable; urgency=low CW> - Discard stderr from formatting processes when outputting to a pager, CW> to avoid visual corruption from any error messages (closes: #372939). Who would have guessed man now does such discarding. No wonder I thought it was a man problem. Who knows how many other warnings one misses because of this. Unix's stderr is there for a reason! Is there a way for the user to turn stderr back on? If I don't like them I will use 2>/dev/null. How is one to know one is reading a damaged man page or not if you throw away errors? What if the user follows damaged instructions on a damaged man page and ends up damaging his system? This is starting to sound like a story from RISKS Digest. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
