From: Keith David Bershatsky <esq@lawlist.com>
To: Alan Third <alan@idiocy.org>,Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Cursors: Is superimposing the same glyph a feature?
Date: Sat, 16 Feb 2019 08:28:49 -0800 [thread overview]
Message-ID: <m2ef87hf3y.wl%esq@lawlist.com> (raw)
Thank you both.
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
> Date: [02-16-2019 03:00:21] <16 Feb 2019 11:00:21 +0000>
> From: Alan Third <alan@idiocy.org>
> To: Keith David Bershatsky <esq@lawlist.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
> Subject: Re: Cursors: Is superimposing the same glyph a feature?
>
> * * *
>
> I can see it too. I'd never noticed. I doubt very much it's
> intentional.
>
> It looks like the NS port does the wrong thing here. At the moment it
> redraws the glyph on top of the cursor as long as CURSOR_TYPE !=
> NO_CURSOR, but looking at an X build, it looks as though HBAR_CURSOR,
> for example, should cover the glyph.
>
> So I reckon we should only redraw the glyph if the cursor is filled box or
> hollow box.
>
> Patch attached.
> --
> Alan Third
>
> [* 0001-Prevent-redrawing-the-glyph-on-top-of-bar-cursors.patch]
next reply other threads:[~2019-02-16 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 16:28 Keith David Bershatsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-08 3:33 Cursors: Is superimposing the same glyph a feature? Keith David Bershatsky
2019-03-09 9:22 ` Alan Third
2019-02-16 7:34 Keith David Bershatsky
2019-02-16 10:05 ` Eli Zaretskii
2019-02-16 11:00 ` Alan Third
2019-02-15 16:27 Keith David Bershatsky
2019-02-15 18:31 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2ef87hf3y.wl%esq@lawlist.com \
--to=esq@lawlist.com \
--cc=alan@idiocy.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.