From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "755351@bugs.debian.org" <755351@bugs.debian.org>,
"rlb@defaultvalue.org" <rlb@defaultvalue.org>,
Josh Triplett <josh@joshtriplett.org>,
"18372@debbugs.gnu.org" <18372@debbugs.gnu.org>,
"755351-forwarded@bugs.debian.org"
<755351-forwarded@bugs.debian.org>
Subject: bug#18372: Bug#755351: blink-cursor-mode should respect GTK+ setting by default
Date: Tue, 2 Sep 2014 07:05:58 +0200 [thread overview]
Message-ID: <67DC170C-4CD6-4F11-9C4A-955537B6CCD2@swipnet.se> (raw)
In-Reply-To: <83tx4rfaig.fsf@gnu.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.
next prev parent reply other threads:[~2014-09-02 5:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=67DC170C-4CD6-4F11-9C4A-955537B6CCD2@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=18372@debbugs.gnu.org \
--cc=755351-forwarded@bugs.debian.org \
--cc=755351@bugs.debian.org \
--cc=eliz@gnu.org \
--cc=josh@joshtriplett.org \
--cc=rlb@defaultvalue.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).