all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: gerd.moellmann@t-online.de (Gerd Moellmann)
Cc: emacs-bidi@gnu.org, alex@emacswiki.org, rms@gnu.org,
	developer@arabeyes.org, emacs-devel@gnu.org
Subject: Re: merge emacs-bidi into the main tree
Date: 10 Aug 2003 12:42:37 +0200	[thread overview]
Message-ID: <86y8y1yesi.fsf@gerd.free-bsd.org> (raw)
In-Reply-To: <uptje10nk.fsf@elta.co.il>

Eli Zaretskii <eliz@elta.co.il> writes:

> However, it doesn't seem right to me to have an Emacs that cannot
> scroll fast enough just because I've set such a flag, assuming that
> Gerd's intuition is correct.

One way to see how working with disabled redisplay optimizations feels
might be to intentionally disable the optimizations in the source
code.

(Which is, BTW, where my intuition comes from, only that I didn't
disable any optimizations, but implement one after the other until the
result was "fast enough", for me anyway.  And, another BTW, redisplay
optimization was _the_ major time sink and _the_ primary source of
complexity, when rewriting redisplay, esp. under the ancillary
condition of being compatible with Emacs 19's redisplay.  I'm
mentioning that only in case that r2l redisplay optimization will
prove necessary.)

In any case, I think it might be worth the experiment.  Computers got
noticeable faster, maybe the picture is different now than it was in
the late '90s.

  reply	other threads:[~2003-08-10 10:42 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 [this message]
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
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=86y8y1yesi.fsf@gerd.free-bsd.org \
    --to=gerd.moellmann@t-online.de \
    --cc=alex@emacswiki.org \
    --cc=developer@arabeyes.org \
    --cc=emacs-bidi@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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 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.