all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@elta.co.il>
Cc: gerd.moellmann@t-online.de, emacs-devel@gnu.org,
	emacs-bidi@gnu.org, developer@arabeyes.org, alex@emacswiki.org
Subject: Re: Re: merge emacs-bidi into the main tree
Date: Tue, 12 Aug 2003 10:48:58 +0200	[thread overview]
Message-ID: <3791-Tue12Aug2003104858+0300-eliz@elta.co.il> (raw)
In-Reply-To: <200308120718.QAA24158@etlken.m17n.org> (message from Kenichi Handa on Tue, 12 Aug 2003 16:18:12 +0900 (JST))

> Date: Tue, 12 Aug 2003 16:18:12 +0900 (JST)
> From: Kenichi Handa <handa@m17n.org>
> 
> Then, it seems that what you've done is not that different
> from the current emacs-bidi.  In most cases, we anyway move
> the iterator all over "abcdABCDefg".  Your code caches only
> some crucial information, so get_next_display_element will
> need some work at C B A e f g.  My code caches all
> information given by get_next_display_element, so
> get_next_display_element will work fast at C B A e f g.

Right.  IIRC, Gerd did not like the caching of glyph matrix elements.
I think he felt that producing the information stored in the glyph is
expensive, and so doing that unnecessarily would hamper performance.
The information my code caches is only relevant to the bidi properties
of the characters, which need to be computed anyway to decide what is
the next character in the visual order.

  reply	other threads:[~2003-08-12  8:48 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87lluax3ch.fsf@emacswiki.org>
     [not found] ` <7458-Sun03Aug2003224354+0300-eliz@elta.co.il>
     [not found]   ` <87smoi9p64.fsf@emacswiki.org>
     [not found]     ` <u1xw26isb.fsf@elta.co.il>
2003-08-04 14:54       ` merge emacs-bidi into the main tree Alex Schroeder
2003-08-07  6:05         ` Richard Stallman
2003-08-07 14:29           ` Eli Zaretskii
2003-08-08  9:05             ` Oliver Scholz
2003-08-08 11:47               ` Kenichi Handa
2003-08-08 15:57               ` Eli Zaretskii
2003-08-08 11:23             ` Gerd Moellmann
2003-08-08 16:02               ` Eli Zaretskii
2003-08-08 16:13                 ` Gerd Moellmann
2003-08-09 14:21                   ` Richard Stallman
2003-08-09 14:58                     ` Gerd Moellmann
2003-08-10  6:34                     ` Eli Zaretskii
2003-08-10 10:42                       ` Gerd Moellmann
2003-08-10 16:56                         ` Eli Zaretskii
2003-08-10 16:33                           ` Gerd Moellmann
2003-08-10 16:45                             ` Stefan Monnier
2003-08-11 12:53                       ` Richard Stallman
2003-08-12  1:49                         ` Kenichi Handa
2003-08-12  6:59                           ` Eli Zaretskii
2003-08-12  7:18                             ` Kenichi Handa
2003-08-12  8:48                               ` Eli Zaretskii [this message]
2003-08-13 17:13                           ` Richard Stallman
2003-08-09 14:21               ` Richard Stallman
2003-08-09 15:04                 ` Gerd Moellmann
2003-08-10  6:36                 ` Eli Zaretskii
2003-08-08 11:44             ` Kenichi Handa
2003-08-08 16:04               ` Eli Zaretskii
2003-08-08 17:48               ` Alex Schroeder
2003-08-08 18:58           ` Chahine M. HAMILA
2003-08-09 18:43           ` Nadim Shaikli
2003-08-11 12:54             ` Richard Stallman
2003-08-11 16:32               ` Nadim Shaikli
2003-08-12 23:22                 ` Richard Stallman
2003-08-13  0:33                   ` Kenichi Handa
2003-08-14  3:08                     ` Richard Stallman
2003-08-15  5:51                       ` Kenichi Handa
2003-08-15 11:51                         ` Alex Schroeder
2003-08-15 15:38                           ` Nadim Shaikli
2003-08-17  0:36                         ` Richard Stallman
2003-08-18  0:24                           ` Kenichi Handa
2003-08-13  3:44                   ` Nadim Shaikli

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=3791-Tue12Aug2003104858+0300-eliz@elta.co.il \
    --to=eliz@elta.co.il \
    --cc=alex@emacswiki.org \
    --cc=developer@arabeyes.org \
    --cc=emacs-bidi@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=gerd.moellmann@t-online.de \
    /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.