all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Keith David Bershatsky <esq@lawlist.com>
Cc: emacs-devel@gnu.org
Subject: Re: How to record the line number pixel width for each window.
Date: Fri, 06 Dec 2019 20:42:52 +0200	[thread overview]
Message-ID: <83zhg5fg7n.fsf@gnu.org> (raw)
In-Reply-To: <7B62F071-E6BB-4768-BEBA-8ABFB3727D3C@lawlist.com> (message from Keith David Bershatsky on Fri, 6 Dec 2019 09:07:10 -0800)

> Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
> From: Keith David Bershatsky <esq@lawlist.com>
> Date: Fri, 6 Dec 2019 09:07:10 -0800
> 
> Thank you, Eli, for reading and responding to this thread.  Once the redisplay cycle gets to the place where update_window is called, all simulations performed by moving IT have already concluded, and update_window is the launch-point for features 17684/22873.  I would be comfortable using an existing instance of screen simulation and perform the essence of line_number_display_width without launching a new session with start_display.  The goal is to be as efficient as possible when storing the values so that they are reliably accessible when update_window gets called.  My general feeling is that update_window is not the place to do screen simulations (moving IT) and running a _new_ instance of start_display for each window is not efficient.
> 
> Is there an existing instance of a running simulation for each window somewhere in xdisp.c where I could add the guts of line_number_display_width without launching a new start_display; and, if so, some pointers on where that might be located would be greatly appreciated?

I'm sorry, I don't understand the question.  What do you call
"simulation" in this context?



  reply	other threads:[~2019-12-06 18:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05 18:19 How to record the line number pixel width for each window Keith David Bershatsky
2019-12-06  8:10 ` Eli Zaretskii
2019-12-06 17:07   ` Keith David Bershatsky
2019-12-06 18:42     ` Eli Zaretskii [this message]
2019-12-06 19:29       ` Keith David Bershatsky
2019-12-07  8:27         ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2019-12-08  2:57 Keith David Bershatsky

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=83zhg5fg7n.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=esq@lawlist.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 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.