unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#18372: Bug#755351: blink-cursor-mode should respect GTK+ setting by default
       [not found] <20140719202311.12507.88471.reportbug@thin>
@ 2014-08-31 21:05 ` Rob Browning
  2014-09-01  0:55   ` Stefan Monnier
  0 siblings, 1 reply; 13+ messages in thread
From: Rob Browning @ 2014-08-31 21:05 UTC (permalink / raw)
  To: 18372; +Cc: Josh Triplett, 755351, 755351-forwarded

[If possible, please preserve the -forwarded address in any replies.]

This was reported to bugs.debian.org, and looked like something that
would be best considered upstream.

Josh Triplett <josh@joshtriplett.org> writes:

> In the GTK+ version of Emacs, the default setting for
> blink-cursor-mode should respect the desktop setting of
> org.gnome.desktop.interface.cursor-blink .  An explicit setting of
> blink-cursor-mode in .emacs could still override it, but the default
> setting should not.
>
> - Josh Triplett

More information here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755351

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4





^ permalink raw reply	[flat|nested] 13+ messages in thread

* bug#18372: Bug#755351: blink-cursor-mode should respect GTK+ setting by default
  2014-08-31 21:05 ` bug#18372: Bug#755351: blink-cursor-mode should respect GTK+ setting by default Rob Browning
@ 2014-09-01  0:55   ` Stefan Monnier
  2014-09-01  6:21     ` Jan D.
  0 siblings, 1 reply; 13+ messages in thread
From: Stefan Monnier @ 2014-09-01  0:55 UTC (permalink / raw)
  To: Rob Browning; +Cc: 755351, Josh Triplett, 18372, 755351-forwarded

>> In the GTK+ version of Emacs, the default setting for
>> blink-cursor-mode should respect the desktop setting of
>> org.gnome.desktop.interface.cursor-blink .  An explicit setting of
>> blink-cursor-mode in .emacs could still override it, but the default
>> setting should not.

That would make a lot of sense, indeed.


        Stefan





^ permalink raw reply	[flat|nested] 13+ messages in thread

* bug#18372: Bug#755351: blink-cursor-mode should respect GTK+ setting by default
  2014-09-01  0:55   ` Stefan Monnier
@ 2014-09-01  6:21     ` Jan D.
  2014-09-01 18:24       ` Josh Triplett
  2014-09-01 22:21       ` Stefan Monnier
  0 siblings, 2 replies; 13+ messages in thread
From: Jan D. @ 2014-09-01  6:21 UTC (permalink / raw)
  To: Stefan Monnier, Rob Browning
  Cc: 755351-forwarded, Josh Triplett, 18372, 755351

Stefan Monnier skrev 2014-09-01 02:55:
>>> In the GTK+ version of Emacs, the default setting for
>>> blink-cursor-mode should respect the desktop setting of
>>> org.gnome.desktop.interface.cursor-blink .  An explicit setting of
>>> blink-cursor-mode in .emacs could still override it, but the default
>>> setting should not.
>
> That would make a lot of sense, indeed.
>

How do you distinguish between the default and

% emacs
M-x blink-cursor-mode
M-x blink-cursor-mode

?

The latter is an explicit setting to on.
Or are we just talking about customizing blink-cursor-mode?

	Jan D.







^ permalink raw reply	[flat|nested] 13+ messages in thread

* bug#18372: Bug#755351: blink-cursor-mode should respect GTK+ setting by default
  2014-09-01  6:21     ` Jan D.
@ 2014-09-01 18:24       ` Josh Triplett
  2014-09-01 18:42         ` Eli Zaretskii
  2014-09-01 22:21       ` Stefan Monnier
  1 sibling, 1 reply; 13+ messages in thread
From: Josh Triplett @ 2014-09-01 18:24 UTC (permalink / raw)
  To: Jan D.; +Cc: 755351, Rob Browning, 18372, 755351-forwarded

On Mon, Sep 01, 2014 at 08:21:58AM +0200, Jan D. wrote:
> Stefan Monnier skrev 2014-09-01 02:55:
> >>>In the GTK+ version of Emacs, the default setting for
> >>>blink-cursor-mode should respect the desktop setting of
> >>>org.gnome.desktop.interface.cursor-blink .  An explicit setting of
> >>>blink-cursor-mode in .emacs could still override it, but the default
> >>>setting should not.
> >
> >That would make a lot of sense, indeed.
> >
> 
> How do you distinguish between the default and
> 
> % emacs
> M-x blink-cursor-mode
> M-x blink-cursor-mode
> 
> ?

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.

- Josh Triplett





^ permalink raw reply	[flat|nested] 13+ messages in thread

* bug#18372: Bug#755351: blink-cursor-mode should respect GTK+ setting by default
  2014-09-01 18:24       ` Josh Triplett
@ 2014-09-01 18:42         ` Eli Zaretskii
  2014-09-01 22:21           ` Stefan Monnier
                             ` (3 more replies)
  0 siblings, 4 replies; 13+ messages in thread
From: Eli Zaretskii @ 2014-09-01 18:42 UTC (permalink / raw)
  To: Josh Triplett; +Cc: 755351-forwarded, rlb, 18372, 755351

> Date: Mon, 1 Sep 2014 11:24:31 -0700
> From: Josh Triplett <josh@joshtriplett.org>
> Cc: 755351@bugs.debian.org, Rob Browning <rlb@defaultvalue.org>,
> 	18372@debbugs.gnu.org, 755351-forwarded@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.)





^ permalink raw reply	[flat|nested] 13+ messages in thread

* bug#18372: Bug#755351: blink-cursor-mode should respect GTK+ setting by default
  2014-09-01 18:42         ` Eli Zaretskii
@ 2014-09-01 22:21           ` Stefan Monnier
  2014-09-01 22:47           ` Josh Triplett
                             ` (2 subsequent siblings)
  3 siblings, 0 replies; 13+ messages in thread
From: Stefan Monnier @ 2014-09-01 22:21 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: 755351-forwarded, rlb, 18372, 755351, Josh Triplett

> Why should we only take blink-cursor-mode from there, and ignore all
> the rest?

Nobody asked to ignore 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.

Currently we only take a few things such as foreground and
background color.  I agree that we should take "anything that's
applicable".


        Stefan





^ permalink raw reply	[flat|nested] 13+ messages in thread

* bug#18372: Bug#755351: blink-cursor-mode should respect GTK+ setting by default
  2014-09-01  6:21     ` Jan D.
  2014-09-01 18:24       ` Josh Triplett
@ 2014-09-01 22:21       ` Stefan Monnier
  1 sibling, 0 replies; 13+ messages in thread
From: Stefan Monnier @ 2014-09-01 22:21 UTC (permalink / raw)
  To: Jan D.; +Cc: Josh Triplett, Rob Browning, 755351, 18372, 755351-forwarded

>>>> In the GTK+ version of Emacs, the default setting for
>>>> blink-cursor-mode should respect the desktop setting of
>>>> org.gnome.desktop.interface.cursor-blink .  An explicit setting of
>>>> blink-cursor-mode in .emacs could still override it, but the default
>>>> setting should not.
>> That would make a lot of sense, indeed.

> How do you distinguish between the default and

> % emacs
> M-x blink-cursor-mode
> M-x blink-cursor-mode

> ?

> The latter is an explicit setting to on.

No, AFAICT it's just asking to toggle it twice.


        Stefan





^ permalink raw reply	[flat|nested] 13+ messages in thread

* bug#18372: Bug#755351: blink-cursor-mode should respect GTK+ setting by default
  2014-09-01 18:42         ` Eli Zaretskii
  2014-09-01 22:21           ` Stefan Monnier
@ 2014-09-01 22:47           ` Josh Triplett
  2014-09-02  4:57           ` Jan Djärv
  2014-09-02  5:05           ` Jan Djärv
  3 siblings, 0 replies; 13+ messages in thread
From: Josh Triplett @ 2014-09-01 22:47 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: 755351-forwarded, rlb, 18372, 755351

On Mon, Sep 01, 2014 at 09:42:15PM +0300, Eli Zaretskii wrote:
> > Date: Mon, 1 Sep 2014 11:24:31 -0700
> > From: Josh Triplett <josh@joshtriplett.org>
> > Cc: 755351@bugs.debian.org, Rob Browning <rlb@defaultvalue.org>,
> > 	18372@debbugs.gnu.org, 755351-forwarded@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.)

By all means, please do so.  blink-cursor-mode was just the particular
one that motivated my report.

- Josh Triplett





^ permalink raw reply	[flat|nested] 13+ messages in thread

* bug#18372: Bug#755351: blink-cursor-mode should respect GTK+ setting by default
  2014-09-01 18:42         ` Eli Zaretskii
  2014-09-01 22:21           ` Stefan Monnier
  2014-09-01 22:47           ` Josh Triplett
@ 2014-09-02  4:57           ` Jan Djärv
  2014-09-02  5:05           ` Jan Djärv
  3 siblings, 0 replies; 13+ messages in thread
From: Jan Djärv @ 2014-09-02  4:57 UTC (permalink / raw)
  To: Eli Zaretskii
  Cc: 755351@bugs.debian.org, rlb@defaultvalue.org, Josh Triplett,
	18372@debbugs.gnu.org, 755351-forwarded@bugs.debian.org

Hi. 

1 sep 2014 kl. 20:42 skrev Eli Zaretskii <eliz@gnu.org>:

>> Date: Mon, 1 Sep 2014 11:24:31 -0700
>> From: Josh Triplett <josh@joshtriplett.org>
>> Cc: 755351@bugs.debian.org, Rob Browning <rlb@defaultvalue.org>,
>>    18372@debbugs.gnu.org, 755351-forwarded@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.)





^ permalink raw reply	[flat|nested] 13+ messages in thread

* bug#18372: Bug#755351: blink-cursor-mode should respect GTK+ setting by default
  2014-09-01 18:42         ` Eli Zaretskii
                             ` (2 preceding siblings ...)
  2014-09-02  4:57           ` Jan Djärv
@ 2014-09-02  5:05           ` Jan Djärv
  2022-06-29 14:55             ` Stefan Kangas
  3 siblings, 1 reply; 13+ messages in thread
From: Jan Djärv @ 2014-09-02  5:05 UTC (permalink / raw)
  To: Eli Zaretskii
  Cc: 755351@bugs.debian.org, rlb@defaultvalue.org, Josh Triplett,
	18372@debbugs.gnu.org, 755351-forwarded@bugs.debian.org

Hi.

1 sep 2014 kl. 20:42 skrev Eli Zaretskii <eliz@gnu.org>:

>> Date: Mon, 1 Sep 2014 11:24:31 -0700
>> From: Josh Triplett <josh@joshtriplett.org>
>> Cc: 755351@bugs.debian.org, Rob Browning <rlb@defaultvalue.org>,
>>    18372@debbugs.gnu.org, 755351-forwarded@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. 

      Jan D. 




^ permalink raw reply	[flat|nested] 13+ messages in thread

* bug#18372: Bug#755351: blink-cursor-mode should respect GTK+ setting by default
  2014-09-02  5:05           ` Jan Djärv
@ 2022-06-29 14:55             ` Stefan Kangas
  2022-06-30  1:09               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
  0 siblings, 1 reply; 13+ messages in thread
From: Stefan Kangas @ 2022-06-29 14:55 UTC (permalink / raw)
  To: Jan Djärv
  Cc: 18372@debbugs.gnu.org, Josh Triplett, Po Lu, rlb@defaultvalue.org,
	Eli Zaretskii, 755351@bugs.debian.org,
	755351-forwarded@bugs.debian.org

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

> Hi.
>
> 1 sep 2014 kl. 20:42 skrev Eli Zaretskii <eliz@gnu.org>:
>
>>> Date: Mon, 1 Sep 2014 11:24:31 -0700
>>> From: Josh Triplett <josh@joshtriplett.org>
>>> Cc: 755351@bugs.debian.org, Rob Browning <rlb@defaultvalue.org>,
>>>    18372@debbugs.gnu.org, 755351-forwarded@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?





^ permalink raw reply	[flat|nested] 13+ messages in thread

* bug#18372: Bug#755351: blink-cursor-mode should respect GTK+ setting by default
  2022-06-29 14:55             ` Stefan Kangas
@ 2022-06-30  1:09               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
  2022-07-05 11:51                 ` Stefan Kangas
  0 siblings, 1 reply; 13+ messages in thread
From: Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2022-06-30  1:09 UTC (permalink / raw)
  To: Stefan Kangas
  Cc: Josh Triplett, 18372@debbugs.gnu.org, rlb@defaultvalue.org,
	Eli Zaretskii, Jan Djärv, 755351@bugs.debian.org,
	755351-forwarded@bugs.debian.org

Stefan Kangas <stefan@marxist.se> writes:

>> 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?

No, I think it should be closed.





^ permalink raw reply	[flat|nested] 13+ messages in thread

* bug#18372: Bug#755351: blink-cursor-mode should respect GTK+ setting by default
  2022-06-30  1:09               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
@ 2022-07-05 11:51                 ` Stefan Kangas
  0 siblings, 0 replies; 13+ messages in thread
From: Stefan Kangas @ 2022-07-05 11:51 UTC (permalink / raw)
  To: Po Lu; +Cc: Eli Zaretskii, Josh Triplett, 18372, rlb@defaultvalue.org

tags 18372 + wontfix
close 18372
thanks

Po Lu <luangruo@yahoo.com> writes:

> > 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?
>
> No, I think it should be closed.

OK, done.





^ permalink raw reply	[flat|nested] 13+ messages in thread

end of thread, other threads:[~2022-07-05 11:51 UTC | newest]

Thread overview: 13+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20140719202311.12507.88471.reportbug@thin>
2014-08-31 21:05 ` bug#18372: Bug#755351: blink-cursor-mode should respect GTK+ setting by default Rob Browning
2014-09-01  0:55   ` Stefan Monnier
2014-09-01  6:21     ` Jan D.
2014-09-01 18:24       ` Josh Triplett
2014-09-01 18:42         ` Eli Zaretskii
2014-09-01 22:21           ` Stefan Monnier
2014-09-01 22:47           ` Josh Triplett
2014-09-02  4:57           ` Jan Djärv
2014-09-02  5:05           ` Jan Djärv
2022-06-29 14:55             ` Stefan Kangas
2022-06-30  1:09               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-05 11:51                 ` Stefan Kangas
2014-09-01 22:21       ` Stefan Monnier

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).