Your suggestion in comment #8 looks like something that is worth to
forward to the Xfce bug tracker (Xfce Core -> Xfce4-settings).
https://bugzilla.xfce.org/
The new key could be added to the xsettings.xml, and maybe even be
exposed in the keyboard settings dialog too.
--
You received this bug
I really don't have much experience reporting bugs with large open
projects. I tried asking in what I thought was the correct venue but
didn't get a response. As long as people who were in my situation can
discover the solution via finding this report or the answer I posted to
the related question
Steve, did you contact the Xfce developers?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798481
Title:
org.gnome.desktop.interface.cursor-blink-timeout not honored
To manage notifications about
Or perhaps such an addition wouldn't be appropriate because it only
applies to GTK applications and the xfce team would only want to include
such a control if it were universal? In any case, I'll try to bring this
to the attention of the xfce maintainers (and add answers to
askubuntu.com, etc).
It seems the symptom is specific to xfce, where the values in xfconf
seem to control the relevant behavior. The cursor blinking timeout for
GTK applications can be controlled by adding a new integer key
"/Gtk/CursorBlinkTimeout" to the "xsettings" channel.
--
You received this bug notification
I grepped for 463 against everything in my home directory and this was at the
top of the list:
.config/xfce4/xfconf/xfce-perchannel-xml/xsettings.xml:
(Apparently I'm also not very familiar with the xfce ecosystem.)
It seems there is some mechanism by which changes to properties in dconf
Thanks for the investigation!
In the mean time I've tried xfce, icewm and windowmaker –
/org/gnome/desktop/interface/cursor-blink* weren't used by VTE in any of
them, some hardcoded defaults were used. I guess some dconf or gsettings
daemon needs to be running to have the required binding in
** Also affects: xfconf (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798481
Title:
org.gnome.desktop.interface.cursor-blink-timeout not
The blink time does seem to be a bit less than a half second. If I count
the seconds out loud it blinks twice each second with a little time to
spare.
"dconf dump /" doesn't yield any instances of 463, but does show 1205
for cursor-blink-time (so it's in harmony with the dconf-editor GUI),
and
> cursor-blink-time: 1200
> cursor-blink-timeout: 1
> time=463 timeout=10
Oops, time should also match and it doesn't.
Can you confirm that blinking is pretty fast for you, that is, the
duration of an entire cycle (on + off phases) is a bit less than half a
second (463 ms, rather than 1.2
#2 Thanks for the comment. I'm accustomed to blinking following focus. The
values I have in dconf are:
cursor-blink: true
cursor-blink-time: 1200
cursor-blink-timeout: 1
I built vte 0.54.1 and ran the test app with debugging messages on as
you described. There is a line referring to "Cursor
VTE does have code in place to support these variables and they work for
me. No need for reboot, not even to restart gnome-terminal, it should
pick up the change immediately.
It stops blinking the cursor when the focus is lost, and restarts
blinking it when the terminal is focused again. Are you
Those are VTE based terminal emulators, so I suggest that you forward
this issue to the GNOME developers.
https://gitlab.gnome.org/GNOME/vte/issues
** Also affects: vte2.91 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
13 matches
Mail list logo
