GNU bug report logs - #18372
Bug#755351: blink-cursor-mode should respect GTK+ setting by default

Previous Next

Package: emacs;

Reported by: Rob Browning <rlb <at> defaultvalue.org>

Date: Sun, 31 Aug 2014 21:06:02 UTC

Severity: wishlist

Tags: wontfix

Done: Stefan Kangas <stefan <at> marxist.se>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Stefan Kangas <stefan <at> marxist.se>
To: Jan Djärv <jan.h.d <at> swipnet.se>
Cc: "18372 <at> debbugs.gnu.org" <18372 <at> debbugs.gnu.org>, Josh Triplett <josh <at> joshtriplett.org>, Po Lu <luangruo <at> yahoo.com>, "rlb <at> defaultvalue.org" <rlb <at> defaultvalue.org>, Eli Zaretskii <eliz <at> gnu.org>, "755351 <at> bugs.debian.org" <755351 <at> bugs.debian.org>, "755351-forwarded <at> bugs.debian.org" <755351-forwarded <at> bugs.debian.org>
Subject: bug#18372: Bug#755351: blink-cursor-mode should respect GTK+ setting by default
Date: Wed, 29 Jun 2022 07:55:08 -0700

Jan Djärv <jan.h.d <at> swipnet.se> writes:

> Hi.
>
> 1 sep 2014 kl. 20:42 skrev Eli Zaretskii <eliz <at> gnu.org>:
>
>>> Date: Mon, 1 Sep 2014 11:24:31 -0700
>>> From: Josh Triplett <josh <at> joshtriplett.org>
>>> Cc: 755351 <at> bugs.debian.org, Rob Browning <rlb <at> defaultvalue.org>,
>>>    18372 <at> debbugs.gnu.org, 755351-forwarded <at> bugs.debian.org
>>>
>>> For the simplest possible implementation, determine the desktop setting
>>> for whether the cursor should blink, and set blink-cursor-mode to that
>>> at startup; any explicit setting would then override that.
>>
>> Why should we only take blink-cursor-mode from there, and ignore all
>> the rest?  E.g., cursor-blink-time and cursor-blink-timeout.  And then
>> there are other settings, like cursor-size, clock-format, etc.  It
>> makes very little sense to take only one setting.
>
> Those that we look at had a GUI in Gnome at one point to change them. Also the
> set of settings has not been very stable. There is no GUI in current Gnome to
> change them, so they aren't really the place where a user can easily tweak
> settings.
>
> So in 99% (figure from air) of the cases these settings are never
> changed. It is not worth it to track a setting that with high
> probability will be removed or change name/place within two years.

So if we don't want to chase these settings, does it make sense to keep
this bug open?  Maybe Po Lu has any comments?
This bug report was last modified 3 years and 40 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.