From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Jason Rumney" <jasonr@gnu.org>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Assertion failes in w32uniscribe.c
Date: Mon, 7 Apr 2008 13:22:32 +0200 [thread overview]
Message-ID: <f7ccd24b0804070422g309eb3b3ra612e7cc35c164f3@mail.gmail.com> (raw)
In-Reply-To: <47F9FF6F.3020900@gnu.org>
On Mon, Apr 7, 2008 at 1:03 PM, Jason Rumney <jasonr@gnu.org> wrote:
> I don't see a significant difference
Well, THAT is surprising. They are not comparable at all for me. In my
setup, with the variable settings I reported, the old backend keeps up
with key repeat and I can scroll one line at a time as long as I want
(that's so in two different computers, with different XP versions,
different CPUs, etc.); and the redisplay during the scroll is smooth.
The new backend either scrolls visibly slow or, often, it just
recenters.
> certainly nothing to justify language like "unusable" and "unbearable" that has been used on this thread.
For my use and scrolling habits, the new backend is unusable and
unbearable. That's a fact: I wouldn't be able to use the CVS Emacs
right now, were not for --disable-font-backend. But that is not a
complain, I'm *reporting* one case of quite noticeable slowness in one
particular use case (scrolling one line at a time) that is perhaps
less usual that the "use C-v/M-v a lot and let next-line/previous-line
ocassionally recenter" behavior that many people prefers.
That said, if you take offense to my choice of words, I apologize and
will try to be more careful from now on. I wasn't trying to slight the
work you've done with the new backend, which is great.
Juanma
prev parent reply other threads:[~2008-04-07 11:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 14:41 Assertion failes in w32uniscribe.c Juanma Barranquero
2008-04-03 15:06 ` Jason Rumney
2008-04-03 17:22 ` Juanma Barranquero
2008-04-04 8:14 ` Jason Rumney
2008-04-04 9:17 ` Juanma Barranquero
2008-04-04 9:42 ` Jason Rumney
2008-04-04 9:35 ` Juanma Barranquero
2008-04-04 10:29 ` Jason Rumney
2008-04-04 11:40 ` Juanma Barranquero
2008-04-04 11:44 ` Juanma Barranquero
2008-04-04 12:54 ` Juanma Barranquero
2008-04-04 17:02 ` Lennart Borgman (gmail)
2008-04-04 17:50 ` Claus
2008-04-04 20:34 ` Jason Rumney
2008-04-04 22:53 ` Lennart Borgman (gmail)
2008-04-04 19:32 ` Óscar Fuentes
2008-04-06 1:14 ` Jason Rumney
2008-04-06 1:47 ` Juanma Barranquero
2008-04-06 13:42 ` Jason Rumney
2008-04-06 15:36 ` Óscar Fuentes
2008-04-07 10:37 ` Juanma Barranquero
2008-04-07 11:03 ` Jason Rumney
2008-04-07 11:22 ` Juanma Barranquero [this message]
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=f7ccd24b0804070422g309eb3b3ra612e7cc35c164f3@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jasonr@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).