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

Previous Next

Full log

Message #29 received at 18372 <at> debbugs.gnu.org (full text, mbox):

From: Jan Djärv <jan.h.d <at> swipnet.se>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: "755351-forwarded <at> bugs.debian.org" <755351-forwarded <at> bugs.debian.org>,
 "18372 <at> debbugs.gnu.org" <18372 <at> debbugs.gnu.org>,
 Josh Triplett <josh <at> joshtriplett.org>,
 "755351 <at> bugs.debian.org" <755351 <at> bugs.debian.org>,
 "rlb <at> defaultvalue.org" <rlb <at> defaultvalue.org>
Subject: Re: bug#18372: Bug#755351: blink-cursor-mode should respect GTK+
 setting	by default
Date: Tue, 2 Sep 2014 06:57:26 +0200

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.
> 
> (I know nothing about GTK, so apologies if these are silly questions.)

Previous Next

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