Package: conkeror Version: 0.9~git080629-1 Severity: important The launcher script /usr/bin/conkeror executes Conkeror in a subshell, capturing the program's output in a variable. Since Conkeror sends all output to the console, this prevents the user from being able to view download status changes, stack traces, debug messages, and other important messages.
Conkeror is designed to be customizable by entering JavaScript code into an RC file, typically ~/.conkerorrc, just as Emacs is desinged to be customizable by entering elisp code into ~/.emacs. Errors in the user's RC file are reported only on the console. Without console output, the user has no way of knowing where in her RC file errors occur. The user can't even print debug messages from her RC file because the output of dump() and dumpln() is eaten by the launcher script. This severly inhibits Conkeror's intended purpose as a customizable and extensible web browsing environment. Moreover, when problems occur in Conkeror, hints as to their causes such, as error/debug/assertion messages and stack traces, are printed only to the console. Conkeror is young software under heavy development and is expected to have a fair number of bugs. When bugs are encountered, all useful clues as to their causes are eaten by the launcher script, preventing users from filing bug reports with useful information. Please modify /usr/bin/conkeror to not eat Conkeror's output.
