From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Daniel Colascione <dancol@dancol.org>
Cc: 11484@debbugs.gnu.org
Subject: bug#11484: 23.4; Scrolling leaves traces of old text behind
Date: Mon, 22 Oct 2012 09:19:27 -0400 [thread overview]
Message-ID: <jwvzk3ebqs3.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <5084D588.4080303@dancol.org> (Daniel Colascione's message of "Sun, 21 Oct 2012 22:11:36 -0700")
>> That isn't a very good solution now that I think about it, as it would
>> require
> A redraw of the whole line just to draw the cursor.
> Are displays still slow enough that we have to care about graphics
> optimization at this level?
Sadly, in my experience, yes: with an E350 fusion processor running X11
and using server-side fonts, the drawing operations are sufficiently
slow that I can see that the frame is drawn top-to-bottom, so yes a full
redraw is very much visible.
IIUC the Xorg guys justify this by saying that these operations "never
happen" nowadays and that speeding them up would have to be at the
detriment of the more common operations.
If someone knows how to get misc-fixed-semicondensed-13 using xft
(i.e. client-side fonts), I'm all ears.
Stefan
PS: BTW, I'm not sure if redrawing one more char on each side would
help, because depending on how the redraw is done, it might just push
the problem one char further.
next prev parent reply other threads:[~2012-10-22 13:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 22:02 bug#11484: 23.4; Scrolling leaves traces of old text behind Frank Marcoline
2012-10-21 19:07 ` Jan Djärv
2012-10-21 19:56 ` Eli Zaretskii
2012-10-22 5:07 ` Jan Djärv
2012-10-22 5:11 ` Daniel Colascione
2012-10-22 13:19 ` Stefan Monnier [this message]
2012-10-22 15:06 ` Kenichi Handa
2012-10-23 1:22 ` Stefan Monnier
2012-10-23 4:50 ` Kenichi Handa
2012-10-23 12:59 ` Stefan Monnier
2012-10-22 17:27 ` Achim Gratz
2012-10-22 17:33 ` Eli Zaretskii
2012-10-22 17:29 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvzk3ebqs3.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=11484@debbugs.gnu.org \
--cc=dancol@dancol.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.