From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.bugs Subject: bug#18372: Bug#755351: blink-cursor-mode should respect GTK+ setting by default Date: Wed, 29 Jun 2022 07:55:08 -0700 Message-ID: References: <20140719202311.12507.88471.reportbug@thin> <878um4fjzv.fsf@trouble.defaultvalue.org> <54041086.9070607@swipnet.se> <20140901182430.GA2901@thin> <83tx4rfaig.fsf@gnu.org> <67DC170C-4CD6-4F11-9C4A-955537B6CCD2@swipnet.se> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3135"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: "18372@debbugs.gnu.org" <18372@debbugs.gnu.org>, Josh Triplett , Po Lu , "rlb@defaultvalue.org" , Eli Zaretskii , "755351@bugs.debian.org" <755351@bugs.debian.org>, "755351-forwarded@bugs.debian.org" <755351-forwarded@bugs.debian.org> To: Jan =?UTF-8?Q?Dj=C3=A4rv?= Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Jun 29 16:58:19 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o6Z90-0000hl-UM for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 29 Jun 2022 16:58:18 +0200 Original-Received: from localhost ([::1]:37026 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o6Z8z-0007FG-Kc for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 29 Jun 2022 10:58:17 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47636) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o6Z6o-0004wg-JP for bug-gnu-emacs@gnu.org; Wed, 29 Jun 2022 10:56:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:37654) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1o6Z6o-0006gc-6l for bug-gnu-emacs@gnu.org; Wed, 29 Jun 2022 10:56:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1o6Z6n-0001HS-VL for bug-gnu-emacs@gnu.org; Wed, 29 Jun 2022 10:56:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Stefan Kangas Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 29 Jun 2022 14:56:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 18372 X-GNU-PR-Package: emacs Original-Received: via spool by 18372-submit@debbugs.gnu.org id=B18372.16565145164844 (code B ref 18372); Wed, 29 Jun 2022 14:56:01 +0000 Original-Received: (at 18372) by debbugs.gnu.org; 29 Jun 2022 14:55:16 +0000 Original-Received: from localhost ([127.0.0.1]:59781 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o6Z64-0001G3-6A for submit@debbugs.gnu.org; Wed, 29 Jun 2022 10:55:16 -0400 Original-Received: from mail-pg1-f174.google.com ([209.85.215.174]:33391) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o6Z62-0001FX-DI for 18372@debbugs.gnu.org; Wed, 29 Jun 2022 10:55:14 -0400 Original-Received: by mail-pg1-f174.google.com with SMTP id z14so15598419pgh.0 for <18372@debbugs.gnu.org>; Wed, 29 Jun 2022 07:55:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:in-reply-to:references:user-agent :mime-version:date:message-id:subject:to:cc :content-transfer-encoding; bh=TT2vk8MpUX8gMNTEh2OwluQQuSuKGj3HBVGOIsAKXco=; b=nG0Y34zEZ988HUeqnlKKiW292VTPVnkQzgKe5xtMYqsImt9n3sWPJz7/ujsBjzJf1T ecW93Rqwbjgx4ed7Ov6QFWf0oecP6kUo/WNE6KAArpNa6VbcjivotJgLyA/l8Vd4RIvl CRbMAVfATUm+UsaXiPIpXWco74kiIx3qg35c4u99269mFHrUMKflzGxhFqQW6QZlSEX6 uSJLetJHb41SEZK4necMy65Q62wJa64srK0FtkSKv65VL8VKolhdawz8XrBrPlLUgvW/ bg9zBLCEPnYODlBx3rkjNf0tHStPh4olLajofpE6CxLdk/ESjcNYtWdSMVKb+FZc4i53 ojng== X-Gm-Message-State: AJIora9kkSLay/YE4WkceGCsEAYGo1pTeaPvsRf5YHxw1WrmkJOGWdvP DQ4iGZDD1j+IEhTzJujMKaVk6auwE0n4i+fXMwY= X-Google-Smtp-Source: AGRyM1s7eoo5k5f4+60onOo7DCJGmmYnekz4ThVjQnFJdMhT1RuMU8dAD7vVVR8fFFxgraJvxQP7UHSF10TpRx4LEMg= X-Received: by 2002:a63:ed48:0:b0:40d:9866:6834 with SMTP id m8-20020a63ed48000000b0040d98666834mr3273194pgk.324.1656514508762; Wed, 29 Jun 2022 07:55:08 -0700 (PDT) Original-Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Wed, 29 Jun 2022 07:55:08 -0700 In-Reply-To: <67DC170C-4CD6-4F11-9C4A-955537B6CCD2@swipnet.se> ("Jan =?UTF-8?Q?Dj=C3=A4rv?="'s message of "Tue, 2 Sep 2014 07:05:58 +0200") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:235640 Archived-At: Jan Dj=C3=A4rv writes: > Hi. > > 1 sep 2014 kl. 20:42 skrev Eli Zaretskii : > >>> Date: Mon, 1 Sep 2014 11:24:31 -0700 >>> From: Josh Triplett >>> Cc: 755351@bugs.debian.org, Rob Browning , >>> 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. Als= o the > set of settings has not been very stable. There is no GUI in current Gnom= e to > change them, so they aren't really the place where a user can easily twea= k > 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?