unofficial mirror of emacs-devel@gnu.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 prevent _inactive_ window update from overreaching.
Date: Wed, 28 Nov 2018 21:52:17 -0800	[thread overview]
Message-ID: <m27egw2zxq.wl%esq@lawlist.com> (raw)

Thank you, Alan, for the additional pointers regarding how this issue may ultimately be resolved.  I will continue to think about and work on this in the coming days.

Yes, all three features (multiple fake cursors, crosshairs, and visible fill column) operate on the same principal.  There are similar functions for each feature, with the only main difference being that multiple fake cursors look for a particular buffer position when dumping the glyph matrix and looping through each row, whereas crosshairs and visible fill column look for a particular window relative X coordinate.

At this time, there is nothing fancy about multiple fake cursors -- i.e., Emacs only looks for a buffer position and creates a fake cursor with the desired cursor type and cursor color.  Magnar's Lisp library is still the only mechanism I am aware of that does the magic.  Instead of placing a visible overlay where fake cursors would ordinarily be created using Magnar's library, there are a few modifications to his Lisp functions that are contained within crosshairs.el.  From the list of fake cursor overlays created by Magnar's library, Emacs gathers the list of buffer positions and then draws built-in fake cursors that are within the confines of the visible windows.

Keith

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

> Date: [11-28-2018 13:31:09] <28 Nov 2018 21:31:09 +0000>
> From: Alan Third <alan@idiocy.org>
> To: Keith David Bershatsky <esq@lawlist.com>
> Cc: emacs-devel@gnu.org
> Subject: Re: nsterm.m: How to prevent _inactive_ window update from overreaching.
> 
> * * *
> 
> FWIW I asked about how the crosshair is drawn (since that was what you
> were discussing originally) but you only talked about multiple
> cursors. Am I to assume then that the crosshair drawing is tightly
> integrated with the multiple cursors?
> --
> Alan Third



             reply	other threads:[~2018-11-29  5:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-29  5:52 Keith David Bershatsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-12-12  7:07 nsterm.m: How to prevent _inactive_ window update from overreaching Keith David Bershatsky
2018-11-27  4:58 Keith David Bershatsky
2018-11-28 21:31 ` Alan Third
2018-11-26  2:14 Keith David Bershatsky
2018-11-26 20:09 ` Alan Third
2018-11-25  2:20 Keith David Bershatsky
2018-11-22 20:13 Keith David Bershatsky
2018-11-22 19:07 Keith David Bershatsky
2018-11-22 22:57 ` 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

  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=m27egw2zxq.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 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).