all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Keith David Bershatsky <esq@lawlist.com>
To: Alan Third <alan@idiocy.org>
Cc: emacs-devel@gnu.org
Subject: Re: nsterm.m: How to play nice with Mojave revisions -- #17684 (crosshairs) and #22873 (multiple fake cursors) ...
Date: Sun, 14 Oct 2018 17:05:48 -0700	[thread overview]
Message-ID: <m2va64ysyr.wl%esq@lawlist.com> (raw)

Thank you, Alan.  Your observations led me to the location where I had suppressed display_and_set_cursor within update_window_cursor.  +-mode and mc-test both work now (after removing the aforementioned restrictions).

Your help is greatly appreciated!

Keith

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

> Date: [10-14-2018 11:03:38] <14 Oct 2018 19:03:38 +0100>
> From: Alan Third <alan@idiocy.org>
> To: Keith David Bershatsky <esq@lawlist.com>
> Cc: emacs-devel@gnu.org
> Subject: Re: nsterm.m: How to play nice with Mojave revisions -- #17684 (crosshairs) and #22873 (multiple fake cursors) ...
> 
> OK, I don't know what's going on, but I *can* tell that as soon as
> +-mode is enabled ns_draw_window_cursor is never called from within
> drawRect, which implies it's not being called by expose_frame. I don't
> know why not, but that's the bit that does the actual drawing.
> 
> At a guess you have to add another call somewhere in xdisp.c to draw
> the cursor(s) when expose_frame is happening.
> --
> Alan Third



             reply	other threads:[~2018-10-15  0:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15  0:05 Keith David Bershatsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-10-13  2:17 nsterm.m: How to play nice with Mojave revisions -- #17684 (crosshairs) and #22873 (multiple fake cursors) Keith David Bershatsky
2018-10-14 18:03 ` Alan Third
2018-10-12  1:53 Keith David Bershatsky
2018-10-12  8:54 ` Alan Third

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=m2va64ysyr.wl%esq@lawlist.com \
    --to=esq@lawlist.com \
    --cc=alan@idiocy.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.