unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 42452@debbugs.gnu.org, radon.neon@gmail.com
Subject: bug#42452: 27.0.91; hollow box cursor sometimes leaves artifacts
Date: Sun, 16 May 2021 16:25:11 +0300	[thread overview]
Message-ID: <837djyvmiw.fsf@gnu.org> (raw)
In-Reply-To: <87lf8eq0cd.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun,  16 May 2021 15:23:14 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: radon.neon@gmail.com,  42452@debbugs.gnu.org
> Date: Sun, 16 May 2021 15:23:14 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > The problem is only on X, so the variable should be X-specific.  It is
> > not unheard of to have such debugging-related variables be
> > system-specific.
> 
> That's true -- and if it was purely a work-around, then I'd see no
> problems with adding the variable.  But in this case, we're talking
> about allowing customising the line width of the hollow cursor, which
> sounds like something that people might find useful in general.

No, we are talking about code that no one really understands why it's
needed, and why only on some systems.  Which means we also don't
understand whether it could have some adverse effects on some systems.






      reply	other threads:[~2021-05-16 13:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21  1:36 bug#42452: 27.0.91; hollow box cursor sometimes leaves artifacts Aaron Jensen
2020-07-21  1:41 ` Aaron Jensen
2020-07-21  3:10   ` Aaron Jensen
2020-07-21 14:18 ` Eli Zaretskii
2021-03-28 22:21 ` Radon Rosborough
2021-03-29  5:06   ` Eli Zaretskii
2021-04-02 21:05     ` Radon Rosborough
2021-05-13  9:44     ` Lars Ingebrigtsen
2021-05-13 10:26       ` Eli Zaretskii
2021-05-16 13:23         ` Lars Ingebrigtsen
2021-05-16 13:25           ` Eli Zaretskii [this message]

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=837djyvmiw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=42452@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=radon.neon@gmail.com \
    /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).