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: Thu, 13 May 2021 13:26:35 +0300 [thread overview]
Message-ID: <83im3n0w10.fsf@gnu.org> (raw)
In-Reply-To: <8735urrmrs.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 13 May 2021 11:44:23 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Radon Rosborough <radon.neon@gmail.com>, 42452@debbugs.gnu.org
> Date: Thu, 13 May 2021 11:44:23 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Since this happens for unknown reasons, most probably some misfeature
> > of the X server, the change to use an explicit line thickness is a
> > debugging device. As such, it shouldn't be the default; instead,
> > let's have a Lisp variable that gives the thickness, by default zero,
> > and let users affected by this issue set the variable to whatever
> > value that fixes the problem.
>
> The patch fixes an issue under some X implementations, and doesn't seem
> to have any negative effects (that I can see), so I've applied Rodon's
> patch.
>
> Allowing users to control the width of the lines sounds like a nice
> feature, but I don't think anybody's requested it, so I'm not sure
> holding up fixing this bug warrants waiting for that to be implemented.
>
> It's easy enough to implement in xterm.c, but (for instance) the Windows
> implementation uses FrameRect, which doesn't allow specifying the line
> thickness? I'd rather not have a feature divergence here.
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.
next prev parent reply other threads:[~2021-05-13 10:26 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 [this message]
2021-05-16 13:23 ` Lars Ingebrigtsen
2021-05-16 13:25 ` Eli Zaretskii
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=83im3n0w10.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).