Process: Determining the origin of a command loop.

[Keith David Bershatsky <esq@lawlist.com>]

One of the items on my todo list for developing feature requests #22873 (multiple fake cursors) and #17684 (crosshairs and visible fill column) is the suppression of redrawing the cursor(s) in certain windows due to output from an ongoing process in one of many visible window.

Let us assume that a user has an _inactive_ window that has ongoing activity; e.g., an *Eshell* buffer is compiling an application and output necessitates that its window be updated.  The user is viewing source code in another window, which may or may not be a different frame all together.  The frame with the *Eshell* buffer may even be hidden behind the active frame.  As output arrives to the *Eshell* buffer, redisplay is updating the cursor in that window and also the active window.

I am unaware of any reason why the cursor in the active window needs updating in this situation.

Q:  How can I determine the origin of the command loop in this situation so that I can suppress the cursor from being updated in the active window?

BACKGROUND:  In general (with some exceptions), multiple fake cursors, crosshairs and the visible fill column are redrawn whenever the real cursor gets updated.

Thanks,

Keith