| 2012-07-28 13:42:48 |
Martin Weis |
description |
bluefish has a bad habit of outputting debug messages not only to stderr, but also on stdout.
1) reproduce: start bluefish from commandline (see example below)
1) expected behaviour: being able to use that commandline further.
2) what happens: bluefish output makes commandline barely usable
Each character typed into the gui text area will trigger one debug message.
This is annoying and might be just due to compiler options not properly set.
For now I added this alias to ~/.bashrc:
alias bluefish="bluefish &>/dev/null"
This appears already since some releases of ubuntu, at least on precise it is apparent.
Thank you for looking into it,
Martin
Example:
# on commandline, run:
echo "<?php ?>" > /tmp/bluefish_bug.php
\bluefish /tmp/bluefish_bug.php 2>/tmp/log.stderr 1>/tmp/log.stdout
# type something in gui
# output on commandline as found in /tmp/log.std* (on 11.04/natty here):
::::::::::::::
/tmp/log.stdout
::::::::::::::
htmlbar_build_menu, finished
cleanup_scanner, num_marks=0, fblock_refcount=0,fcontext_refcount=0,fstack_refcount=0
cleanup_scanner, num_marks=0, fblock_refcount=0,fcontext_refcount=0,fstack_refcount=0
group disabled, class=php_short_open_tag, notclass=(null), skip to end of group, my depth=3
cleanup_scanner, num_marks=0, fblock_refcount=0,fcontext_refcount=0,fstack_refcount=0
Language statistics for PHP from /usr/share/bluefish/bflang//php.bflang2
table 45133 (11283,25 Kbytes)
contexts 140 (6,56 Kbytes)
matches 7467 (525,02 Kbytes)
cleanup_scanner, num_marks=0, fblock_refcount=0,fcontext_refcount=0,fstack_refcount=0
scanning run 1 (0 ms): 0, 0, 0, 0; loops=12,chars=9,blocks 1/1 (1) contexts 1/1 (1) scancache 2 refcs 1(0Kb),1(0Kb),2(0Kb) marks 0
scanning run 2 (0 ms): 0, 0, 0, 0; loops=13,chars=11,blocks 0/0 (0) contexts 0/0 (0) scancache 2 refcs 1(0Kb),1(0Kb),2(0Kb) marks 0
[...snip...]
::::::::::::::
/tmp/log.stderr
::::::::::::::
(process:6243): GLib-WARNING **: /build/buildd/glib2.0-2.28.6/./glib/goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 0
(process:6243): GLib-WARNING **: /build/buildd/glib2.0-2.28.6/./glib/goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 0
(process:6243): GLib-WARNING **: /build/buildd/glib2.0-2.28.6/./glib/goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 6 |
bluefish has a bad habit of outputting debug messages not only to stderr, but also on stdout.
1) reproduce: start bluefish from commandline (see example below)
1) expected behaviour: being able to use that commandline further.
2) what happens: bluefish output makes commandline barely usable
Each character typed into the gui text area will trigger one debug message.
This is annoying and might be just due to compiler options not properly set.
For now I added this alias to ~/.bashrc:
alias bluefish="bluefish &>/dev/null"
This appears already since some releases of ubuntu, at least on precise it is apparent.
Thank you for looking into it,
Martin
Example:
# on commandline, run:
echo "<?php ?>" > /tmp/bluefish_bug.php
\bluefish /tmp/bluefish_bug.php 2>/tmp/log.stderr 1>/tmp/log.stdout
# type something in gui
# output on commandline as found in /tmp/log.std* (on 11.04/natty here):
::::::::::::::
/tmp/log.stdout
::::::::::::::
htmlbar_build_menu, finished
cleanup_scanner, num_marks=0, fblock_refcount=0,fcontext_refcount=0,fstack_refcount=0
cleanup_scanner, num_marks=0, fblock_refcount=0,fcontext_refcount=0,fstack_refcount=0
group disabled, class=php_short_open_tag, notclass=(null), skip to end of group, my depth=3
cleanup_scanner, num_marks=0, fblock_refcount=0,fcontext_refcount=0,fstack_refcount=0
Language statistics for PHP from /usr/share/bluefish/bflang//php.bflang2
table 45133 (11283,25 Kbytes)
contexts 140 (6,56 Kbytes)
matches 7467 (525,02 Kbytes)
cleanup_scanner, num_marks=0, fblock_refcount=0,fcontext_refcount=0,fstack_refcount=0
scanning run 1 (0 ms): 0, 0, 0, 0; loops=12,chars=9,blocks 1/1 (1) contexts 1/1 (1) scancache 2 refcs 1(0Kb),1(0Kb),2(0Kb) marks 0
scanning run 2 (0 ms): 0, 0, 0, 0; loops=13,chars=11,blocks 0/0 (0) contexts 0/0 (0) scancache 2 refcs 1(0Kb),1(0Kb),2(0Kb) marks 0
[...snip...]
::::::::::::::
/tmp/log.stderr
::::::::::::::
(process:6243): GLib-WARNING **: /build/buildd/glib2.0-2.28.6/./glib/goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 0
(process:6243): GLib-WARNING **: /build/buildd/glib2.0-2.28.6/./glib/goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 0
(process:6243): GLib-WARNING **: /build/buildd/glib2.0-2.28.6/./glib/goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 6
---
Architecture: i386
DistroRelease: Ubuntu 11.04
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
NonfreeKernelModules: wl
Package: bluefish 2.0.2-1
PackageArchitecture: i386
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
LANG=en_US.UTF-8
LC_MESSAGES=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.38-15.64-generic 2.6.38.8
Tags: natty
Uname: Linux 2.6.38-15-generic i686
UpgradeStatus: Upgraded to natty on 2011-05-10 (444 days ago)
UserGroups: |
|
