Chinese water torture or blinking cursor at qt5 apps

[cord]

One of the most famous methods of torture is Chinese water torture. In this torture a tied person is placed under a bucket filled with water with a tiny hole in the bottom. Water is slowly dripped on to a person's forehead, eventually driving the victim insane.
Software development is not an easy task, and often after a painful process of writing a program developers feel they should share their pains with users, so they put a part of own sufferings onto the shoulders of users in a method similar to the Chinese water torture - blinking cursors.
Fortunately, programmers are not insensitive torturers, and sometimes they provide an option in their programs to turn blinking cursors off. Often these options are not documented, and are not easily accessible, but many users can't stand the blinking cursor for a long time, because blinking cursors are very distracting.
http://www.jurta.org/en/prog/noblink

For the qt5 apps in KDE there's useful utility qt5noblink. It compiles and works clearly simple.

[cboldt]

Try /etc/env.d

[cord]

[cboldt]

/etc/env.d/00Local doesn't exist if you don't make it, and even IF and AFTER you make it, entries in there do NOTHING without following the steps I specified in my previous.

The program `env-update` reads ALL of the files in the directory /etc/env.d, and collates those entries into /etc/profile.env. I assure you, that process does in fact work.

Now, I have no clue as to whether or not having LD_PRELOAD in your bash/shell environment affects KDE the way you want it to, but if you make an LD_PRELOAD entry into ANY file in /etc/env.d, run `env-update`, and login to a fresh shell, you will find that the assignment of LD_PRELOAD you put into a file in /etc/env.d does in fact make it to your shell environment. You can prove it to yourself with `env | grep LD_PRELOAD`

If a single user want to make an entry in his or her environment, the details depends on the shell being used. Most people running Gentoo use bash for their shell. Setting an environment variable under bash is typically done in either ~/.bash_profile or ~/.bashrc

[cord]

Oh, thanks for detailed answer. Now it works (after full reboot; 'env-update' was not enough).
However, using ~/.bashrc is more attractive.

[cboldt]

Good to know it works. You are correct, `env-update` is not enough, no more than just editing .bashrc is enough. The "proposed revised" environment has to be "entered" to the system, from the file. Rather than rebooting, if you run into this sort of thing again, logging your user out and back in again will cause the new environment to be in effect. Same goes for environment settings in .bashrc

That's not the only way to get the new environment in place, but something beyond editing the file or files that define the "proposed environment" is necessary.

[cord]

Yeah, some tips.
For /etc/env.d/* you can simply set

[Hu]

If you are confident that you will always want this, it might be easier to carry a local user patch to Qt5 to implement the equivalent change. The linked project is very simple. Assuming it produces the result you want, you could get equivalent results without need of LD_PRELOAD by patching QApplication::cursorFlashTime() and QStyleHints::cursorFlashTime() const to return 0 instead of whatever the Qt developers made them do normally. If you need help with this approach, post back and someone can give you more detailed assistance.

[cord]

All right. I'll be glad to see if someone do that patch.