From: Claus <claus.klingberg@gmail.com>
To: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
Cc: Juanma Barranquero <lekktu@gmail.com>,
Jason Rumney <jasonr@gnu.org>, Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Assertion failes in w32uniscribe.c
Date: Fri, 4 Apr 2008 19:50:20 +0200 [thread overview]
Message-ID: <fb5c9a920804041050l3145f2b9jc0009c55fb8a7cfc@mail.gmail.com> (raw)
In-Reply-To: <47F65F16.70904@gmail.com>
> I am still using --disable-font-backend because without it there has been
> some very annoying screen blinking. Has anyone else seen this?
Confirmed. Lot's of blinking, especially when the screen is split (C-x
2). It looks like for each keystroke both buffers are completely
redisplayed (or parsed... or re-fontified... hard to tell the
difference).
Whatever it is, it causes lag / slowdown during typing.
Thus, I see myself using C-x 1 all the time to enhance performance a bit.
GNU Emacs 23.0.60.1 (i386-mingw-nt6.0.6000) of 2008-03-23 on WindowsVista
Claus
On Fri, Apr 4, 2008 at 7:02 PM, Lennart Borgman (gmail)
<lennart.borgman@gmail.com> wrote:
>
> Juanma Barranquero wrote:
>
> > OK, it is working now. Thanks.
> >
> > It is still slow, though. From "emacs -Q -f view-hello-file" to
> > actually see etc/HELLO, about 8-10 seconds, or three times slower than
> > the same operation using --disable-font-backend.
> >
>
> I am still using --disable-font-backend because without it there has been
> some very annoying screen blinking. Has anyone else seen this?
>
> Another strange things I have seen the last days is that sometimes the
> welcome screen is shown without any colors and without the image. Next time
> I try it works as it should. Does not that look like a missing
> initialization somewhere?
>
> But please notice that this is with my slightly patched version (v 23,
> 2008-04-03).
>
>
>
--
Mit freundlichem Gruß,
Claus Klingberg
next prev parent reply other threads:[~2008-04-04 17:50 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 [this message]
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
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=fb5c9a920804041050l3145f2b9jc0009c55fb8a7cfc@mail.gmail.com \
--to=claus.klingberg@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=lekktu@gmail.com \
--cc=lennart.borgman@gmail.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 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).