asked 2014-01-12 23:08:46 +0300
Terminal screen flashes brightly if the backspace key is pressed when the bash command line is empty, i.e. if there's nothing to delete. This may be disturbing especially if the phone is used in darkness.
Interestingly enough, this does not seem to happen in the same session again if the About menu is displayed once.
Fingerterm version is 1.0.3, SailfishOS is 1.0.2.5.
answered 2018-08-11 13:05:52 +0300
@t4k1t - if this did work, it doesn't work any more. Strange that a settings.ini file makes no difference when edited, I have no idea why.
So, I have come up with another solution. Using Terminal, navigate to;
/usr/share/fingertern/Main.qml
Look for line 90, it looks like this;
color: bellTimer.running ? "#ffffff" : bgcolor
Change the hex colour letters of 'ffffff' to 6 x zero; '000000', so it looks like this;
color: bellTimer.running ? "#000000" : bgcolor
or simply,
color: bgcolor
also, as suggested by Mohjive, a subtle shade to keep visual bell visible but in a dimmer shade,
color: bellTimer.running ? "#303030" : bgcolor
Save your changes and open FingerTerm again to test, the 'visual bell' should no longer flash.
Somewhat related; more on FingerTerm stuff by me, here;
https://together.jolla.com/question/102504/allow-setting-background-colour-of-fingerterm/
answered 2014-01-14 18:32:48 +0300
That is the visual bell. If it annoys you that much you can open up /home/nemo/.config/FingerTerm/settings.ini and set visualBell=false.
You're right the settings are overwritten on every start. This very much looks like a bug to me - According to fingerterm's doc it should only be created on first run.
t4k1t ( 2014-01-15 20:37:52 +0300 )editExperiencing same flashing behavior in Sailfish 2.2 . Tried setting both visualBell=false and bellAlert=falsebut no change of behavior. Tried looking in https://git.merproject.org/mer-core/fingerterm but couldn't find any clues.
Asked: 2014-01-12 23:08:46 +0300
Seen: 901 times
Last updated: Aug 12 '18
I'd assume that that is the visible bell. It should be there by default, but an idea is that the user should be able to disable it. That it goes away after the About dialog seems to me is the real bug.
Mohjive ( 2014-01-13 00:14:44 +0300 )edit