Branching off of another thread:
I thought I had 3.63 restabilized, but I guess I was mistaken. I've gotten a particular connection all set up again as it was, but periodically strange things happen. The screen font goes from 11 point to 7 point, it loses track of the font I have designated on the screen (still there in options), it reverts to ANSI instead of connection colors, it goes from 80x25 fixed to 80x24 fixed. I thought this was coming from a shell script issuing a tput is2, which is defined as is2=\\E[?3l\\E[?7h\\E>\\E[?1l\\E[?4l\\E)0, but now it seems to happen every time a new prompt is displayed.
PS1='\\[\\033[1;7;34m\\]\\u\\[\\033[1;7;34m\\]@\\h:\\[\\033[1;7;34m\\]\\w\\[\\033[0m\\] '
Also from the prior thread:
Further experimentation reveals that
PS1='\\[\\033[1;7;34m\\]\\u' is sufficient to produce the effect.
I am also getting this every time I do an "ls -l" and there is a file whose permissions cause bash to color the file name.
Thomas,
I've been thinking about this and it sounds like you've got the auto-ansi setting set to 'yes'. Look at Options->Properties->Global to check. When set to yes, the color mode will switch automatically to 'ANSI' when ANSI color data is received. Absolute then gets a little overly agressive in setting some other things (font, screen size). This is not new in 3.63, but it sounds like switching the auto-ansi to 'no' will help.
Future versions of Absolute will likely be less agressive about automatically setting these additional things, but when set to yes, the 'auto-ansi' feature will still switch to ansi mode when ansi color data is received.
Brian
Bang on! That was it.
Glad to hear it!
Brian
It would be nice, however, to do something about that "aggression"!
It's already done. In the next version, 'auto-ansi' will ONLY change the color setting. I always have to try to remember to strike a balance between building in 'smarts' into the application (to do things for users who don't know what they're doing) and allowing users to have full control.
Inevitably, trying to make the application smart will get in the way of those who don't want it to be done that way. That is why the auto-ansi option is configurable.
Equally inevitable will be the complaints that are yet to come from users who want the auto-ansi put back the way it was!!!
Oh well... We'll see...
Brian
I find it difficult to see that overriding/forgetting the font; changing the font size, and changing the number of lines in the window is a virtue, simply because one has encountered one of the most common color codings in use.