From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 20410@debbugs.gnu.org
Subject: bug#20410: 24.5.50; cursor not updated after yank of non-ASCII string from the clipboard
Date: Sun, 26 Apr 2015 19:02:05 +0900 [thread overview]
Message-ID: <wlpp6r9pia.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <83mw1wxuax.fsf@gnu.org>
>>>>> On Sat, 25 Apr 2015 15:32:22 +0300, Eli Zaretskii <eliz@gnu.org> said:
> Adjusting frame glyphs makes all glyph rows disabled, so various
> redisplay optimizations should be disabled. In particular, new cursor
> position was correctly computed, but because it was on a disabled
> glyph row, display_and_set_cursor would not obey that new position,
> and exposing a window would not redraw the disabled glyph rows.
> Does the patch below fix the problems you see? (It might look a bit
> drastic, but then loading new fonts is not supposed to be a frequent
> operation, I think.)
Yes, it solves the problems as far as I tested. But because
adjust_frame_glyphs are called from many places other than font
changes, I wonder if it might disable some cases where some
optimizations were applied successfully otherwise (sorry, I don't have
any ideas about concrete examples). Some calls to adjust_frame_glyphs
are already accompanied by SET_FRAME_GARBAGED, but not always.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2015-04-26 10:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 9:59 bug#20410: 24.5.50; cursor not updated after yank of non-ASCII string from the clipboard YAMAMOTO Mitsuharu
2015-04-23 10:42 ` Eli Zaretskii
2015-04-24 4:09 ` YAMAMOTO Mitsuharu
2015-04-24 6:58 ` Eli Zaretskii
2015-04-25 9:49 ` YAMAMOTO Mitsuharu
2015-04-25 10:09 ` Eli Zaretskii
2015-04-25 12:32 ` Eli Zaretskii
2015-04-26 10:02 ` YAMAMOTO Mitsuharu [this message]
2015-04-26 15:04 ` Eli Zaretskii
2015-04-27 3:28 ` YAMAMOTO Mitsuharu
2015-04-27 15:17 ` 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=wlpp6r9pia.wl%mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=20410@debbugs.gnu.org \
--cc=eliz@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.