On Thursday 18 June 2009 10:20:25 rxantos wrote:
> asmedit, asmplan, asmproject, asmview and asmide leaves the console screen
> blue after its use. the problem corrects itself when a command with color
> is executed, but its anoying.
>
> asmmgr, asmfile correctly puts the screen back to its original colors.

Yes, terminal colors can be a problem and there are lots of options:

Some people set the color in their prompt string and put it in the
.bashrc file. There is a HOWTO on this somewhere.

Another approach is to build a small script that sets all the terminal
parmeters including color. This allows us to control line wrapping
and all the other features. We can then run the script whenever the
display is wrong.

Another approach is to use a file manager to run programs and let
it setup defaults after each program runs. I use this approach and
avoid most display setup problems.

The final approach is to rely on each program to restore the
defaults when it exits. The problem with this approach is that
each terminal has its own default color setting. It can be tedious
studying each terminal setup file to fix the color. On my system
a "xterm" gives a white-on-black screen and "konsole" gives a
black-on-white screen. It would be nice if each program could
read the current color and restore it, but I've not found a way to
do this. It appears the best we can do is restore the terminal
default.

So.. Asmtools should always restore the termnal
default as you suggest. Also, they need to clear the
screen and set other terminal defaults. Probably, the
best way to do all this is create a library function and
add it to the end of all programs.

It's on the todo list.

Thanks for the bug reprot.

all the best, jeff