From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
hermann sorgel <hermannsorgel@gmail.com>,
72230@debbugs.gnu.org
Subject: bug#72230: 29.4; Cursor Disappears with Hebrew Text
Date: Mon, 22 Jul 2024 10:05:05 +0800 [thread overview]
Message-ID: <87sew2xju6.fsf@yahoo.com> (raw)
In-Reply-To: <CADwFkmnZ_AgRFES+aeQ7GvQ8HGwStJqRrhzKKKYzYT88PSWa7w@mail.gmail.com> (Stefan Kangas's message of "Sun, 21 Jul 2024 11:05:57 -0700")
Stefan Kangas <stefankangas@gmail.com> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> So maybe the problem is elsewhere. One thing is almost certain: it's
>> a problem specific to the macOS build of Emacs. People who can debug
>> on that platform are encouraged to suggest insights and changes.
>
> This seems to have something to with the clipping path, and is fixed
> here by the below patch. I don't think it's suitable for installing
> though.
>
> Po Lu, since you added the below NSRectClip call, do you have any
> thoughts here?
Yes, this will cause the overhangs of a cursor glyph to overwrite its
surroundings. There is certain to be some other factor that has not
been accounted for, while mindlessly removing clipping operations is not
the solution.
> diff --git a/src/nsterm.m b/src/nsterm.m
> index 794630de1c1..54b15bc851d 100644
> --- a/src/nsterm.m
> +++ b/src/nsterm.m
> @@ -3102,7 +3102,7 @@ Note that CURSOR_WIDTH is meaningful only for
> (h)bar cursors.
> #ifdef NS_IMPL_GNUSTEP
> GSRectClipList (ctx, &r, 1);
> #else
> - NSRectClip (r);
> + // NSRectClip (r);
> #endif
>
> [FRAME_CURSOR_COLOR (f) set];
> @@ -3135,7 +3135,7 @@ Note that CURSOR_WIDTH is meaningful only for
> (h)bar cursors.
> on the right of its glyph, rather than on the left. */
> cursor_glyph = get_phys_cursor_glyph (w);
> if ((cursor_glyph->resolved_level & 1) != 0)
> - s.origin.x += cursor_glyph->pixel_width - s.size.width;
> + s.origin.x += cursor_glyph->pixel_width - cursor_width;
I don't recollect what `s' is supposed to represent.
next prev parent reply other threads:[~2024-07-22 2:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-21 14:20 bug#72230: 29.4; Cursor Disappears with Hebrew Text hermann sorgel
2024-07-21 15:46 ` Eli Zaretskii
2024-07-21 16:01 ` Eli Zaretskii
2024-07-21 17:15 ` hermann sorgel
2024-07-21 17:31 ` hermann sorgel
2024-07-21 17:37 ` Eli Zaretskii
2024-07-21 18:05 ` Stefan Kangas
2024-07-21 18:42 ` Gerd Möllmann
2024-07-21 18:45 ` Gerd Möllmann
2024-07-21 19:26 ` Stefan Kangas
2024-07-21 21:35 ` hermann sorgel
2024-07-22 2:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-07-22 6:47 ` Gerd Möllmann
2024-07-23 6:17 ` Gerd Möllmann
2024-07-23 7:14 ` Stefan Kangas
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=87sew2xju6.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=72230@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=hermannsorgel@gmail.com \
--cc=luangruo@yahoo.com \
--cc=stefankangas@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).