From: Thien-Thi Nguyen <ttn@glug.org>
Cc: emacs-devel@gnu.org
Subject: Re: display question: should ^N and \NNN widths be fixed?
Date: 27 May 2002 02:44:14 -0400 [thread overview]
Message-ID: <jkptziozsx.fsf@glug.org> (raw)
In-Reply-To: Richard Stallman's message of "Sat, 25 May 2002 22:28:53 -0600 (MDT)"
Richard Stallman <rms@gnu.org> writes:
- consult font text-property <-- potential race condition?
This code is all serial; it can't have race conditions. Why did you
think there was one? Perhaps that is a misunderstanding that is worth
identifying so we can clear it up now.
i know emacs separates the display into its own thread. the emacs display is
customizable w/ elisp that may eventually lead back to calling current-column.
not knowing the details for text-property access from C, i imagine some lock
that must be manipulated in precise order. this is because i haven't read
that part of emacs, foolishly trusting my instincts to cover for my ignorance.
in any case, when retooling caching schemes, there is always a possibility of
offloading the task to another thread. (sometimes i like to think of things
w/ parallel operation in mind, even if not needed immediately -- headed for
that emacs uproc, you know. ;-)
thi
next prev parent reply other threads:[~2002-05-27 6:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-23 21:16 display question: should ^N and \NNN widths be fixed? Thien-Thi Nguyen
2002-05-24 21:14 ` Richard Stallman
2002-05-24 23:20 ` Thien-Thi Nguyen
2002-05-24 23:34 ` Thien-Thi Nguyen
2002-05-25 1:44 ` Miles Bader
2002-05-25 2:39 ` Thien-Thi Nguyen
2002-05-25 2:57 ` Miles Bader
2002-05-26 5:03 ` Eli Zaretskii
2002-05-26 5:11 ` Thien-Thi Nguyen
2002-05-25 3:05 ` Miles Bader
2002-05-25 22:53 ` Thien-Thi Nguyen
2002-05-25 3:05 ` Miles Bader
2002-05-26 4:28 ` Richard Stallman
2002-05-27 6:44 ` Thien-Thi Nguyen [this message]
2002-05-28 5:15 ` Richard Stallman
2002-05-26 5:09 ` Eli Zaretskii
2002-05-27 6:48 ` Thien-Thi Nguyen
2002-05-27 7:33 ` Eli Zaretskii
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=jkptziozsx.fsf@glug.org \
--to=ttn@glug.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).