This forum has been archived. All content is frozen. Please use KDE Discuss instead.

cursor blinking rate

Tags: None
(comma "," separated)
jlittle
Registered Member
Posts
4
Karma
0
OS

cursor blinking rate  Topic is solved

Sun Apr 15, 2012 11:22 am
I avoided konsole for years because the cursor didn't blink, and then when it could it was too slow. Nowhere in the konsole screen or docs gave any indication that it could be controlled.

But it can ;D

konsole respects the Qt cursorFlashTime setting! Install qtconfig and it's on the Interface tab. Or edit the config file, on my Kubuntu Oneiric it's in ~/.config/Trolltech.conf, in the [qt] section.
User avatar
Jekyll
KDE Developer
Posts
34
Karma
0
OS

Re: cursor blinking rate

Mon Apr 16, 2012 2:42 am
Thanks for sharing tip.

Yes, Konsole internally looks up QApplication::cursorFlashTime() to determine the cursor splashing interval.

One question out of curiosity: what is the value you have set since you find the default speed too slow? Another related question is why you prefer cursor blinking on than off. AFAIK, many users don't like cursor blinking at all because it is a huge distraction for them. That is good reason why cursor blinking is disabled by default.
jlittle
Registered Member
Posts
4
Karma
0
OS

Re: cursor blinking rate

Mon Apr 16, 2012 10:47 am
Jekyll wrote: One question out of curiosity: what is the value you have set since you find the default speed too slow?

I like 200 ms on, 150 ms off, usually; it depends how fast I am working, if really cranking I might make that 150 ms on 100 off. Before discovering the Qt setting I was using a blink programme in the background 200 ms on, 150 off, but that was not a "smart" blink. I initially formed my preference experimenting in gvim many years ago.
So now for konsole I have cursorFlashTime set to 350 ms.
Another related question is why you prefer cursor blinking on than off.

You find the cursor easily, and are quickly alerted if through a typo the cursor has gone somewhere you're not expecting. In the old days using "dumb" terminals I'd find myself doing a trill on a pair of arrow keys, to locate the cursor if it didn't blink, or blinked too slowly.
I suppose these days terminal emulators run shells and pagers almost all of the time, and finding the cursor is easy because it's always on the last line. But I do use shell commands that are quite long, and build them gradually to avoid errors, and so use line editing movement commands that can put the cursor where the blink helps to find it.
AFAIK, many users don't like cursor blinking at all because it is a huge distraction for them. That is good reason why cursor blinking is disabled by default.

I suspect that a large subset of those users do not realize the boon the blink can be, because the default is so slow.


Bookmarks



Who is online

Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell