retitle 589683 Kate needs a "quiet" option
stop
Hi,
Fair enough... I'm so use to verbose KDE apps that I automatically put
them in the background and redirect output when I start one from a
command line--of course everyone else should do the same. :D
I tried a couple other "visual" editors, xjed and xemacs, neither of
them sent any output to the X-term. So, indeed, this is a problem with
Kate which makes it rather less than suitable as a system's VISUAL
editor.
Note: although I use a local build of KDE3 (KDE4 eats up too many
resources on this older box), and the Kate that comes with KDE4 is
somewhat less verbose than the one from KDE3, it still spews out a lot
of generally useless messages and doesn't appear to have a "quiet"
option.
- Bruce
On July 19, 2010 11:25:19 pm Sandro Tosi wrote:
> reassign 589683 kate
> thanks
>
> Hello Bruce,
> this seems to me a bug (even if at wishlist severity) in kate: if you
> want them to stop print those lengthy messages, ask them :) I can't
> redirect all output from text editor to dev/null or so: there might
> be cases when having their output on screen is useful, without going
> to look in another place (or in no place at all, as in /d/null), but
> I understand the startup of kate is really verbose.
>
> I'm assigning this bug to the kate package.
>
> Regards,
> Sandro
>
> On Tue, Jul 20, 2010 at 00:42, Bruce Sass wrote:
> > Package: reportbug
> > Version: 4.12.4
> > Severity: wishlist
> >
> >
> > It would be really nice if reportbug sent the information messages
> > generated by Kate (KDE text editor) to /dev/null or a log file
> > instead of the screen when not in debug/verbose mode.
> >
> > Here is a transcript of a session so you can see just how ugly the
> > current behaviour is:
> >
> > bs...@onegee:~$ reportbug chkrootkit
> > *** Welcome to reportbug. Use ? for help at prompts. ***
> > Detected character set: us-ascii
> > Please change your locale if this is incorrect.
> >
> > Using 'Bruce Sass ' as your from address.
> > Getting status for chkrootkit...
> > Verifying package integrity...
> > Checking for newer versions at packages.debian.org,
> > incoming.debian.org and http://ftp-master.debian.org/new.html Will
> > send report to Debian (per lsb_release).
> > Querying Debian BTS for reports on chkrootkit (source)...
> > 9 bug reports found:
> >
> > Outstanding bugs -- Important bugs; Patch Available (1 bug)
> > 1) #580491 chkrootkit: 1)with nfs mounted the silent don't work
> > 2)can't exclude legacy sniffer (dhcpd, snort, ntop e
> >
> > Outstanding bugs -- Normal bugs; Unclassified (7 bugs)
> > 2) #535942 chkrootkit: fix for chkproc race
> > 3) #548582 chkrootkit: Chkrootkit isn't quiet with -q and
> > excluded suspicious files 4) #564147 chkrootkit: false positive:
> > scalper rootkit and ser2net debian package both listen on port 2001
> > by defaul 5) #566687 chkrootkit: False positive for SMTPs
> > (Courier, Postfix) 6) #576470 chkrootkit: false positives for
> > libsmlnj-smlnj 7) #586897 Meaningless error message when option -e
> > is used without argument 8) #588121 chkrootkit: false positive
> > bitlbee, /usr/bin/find 'head' terminated signal 13
> >
> > Forwarded bugs -- Normal bugs (1 bug)
> > 9) #488558 False positive for vdr
> > (1-9/9) Is the bug you found listed above [y|N|b|m|r|q|s|f|?]?
> > Maintainer for chkrootkit is 'Giuseppe Iuculano
> > '. Looking up dependencies of chkrootkit...
> > Getting changed configuration files...
> > *** The following debconf settings were detected:
> > * chkrootkit/run_daily: true
> > * chkrootkit/run_daily_opts: -q -n
> > * chkrootkit/diff_mode: false
> > Include these settings in your report [Y|n|q|?]?
> >
> > Please briefly describe your problem (max. 100 characters allowed;
> > you can elaborate in a moment). This will be the bug email subject,
> > so write a concise summary of what is wrong with the package, for
> > example, "fails to send email" or "does not start with -q option
> > specified" (type Ctrl+c to exit).
> >
> >> $egrep used unset
> >
> > Rewriting subject to 'chkrootkit: $egrep used unset'
> >
> > Enter any additional addresses this report should be sent to; press
> > ENTER after each address. Press ENTER on a blank line to continue.
> >
> >
> > How would you rate the severity of this problem or report?
> >
> > 1 critical makes unrelated software on the system (or the
> > whole system) break, or causes serious data loss, or introduces a
> > security hole on systems where you install the package. 2 grave
> > makes the package in question unusable by most or all users,
> > or causes data loss, or introduces a security hole allowing access
> > to the accounts of users who use the package. 3 serious is
> > a severe violation of Debian policy (that is, the problem is a
> > violation of a 'must' or 'required' directive); may or may not
> > affect the usability of the package. Note that non-severe policy
> > violations may be 'normal,' 'minor,' or '
