From: Eli Zaretskii <eliz@gnu.org>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: 20410-done@debbugs.gnu.org
Subject: bug#20410: 24.5.50; cursor not updated after yank of non-ASCII string from the clipboard
Date: Mon, 27 Apr 2015 18:17:39 +0300 [thread overview]
Message-ID: <83oam9wqgc.fsf@gnu.org> (raw)
In-Reply-To: <wlwq0ytfk5.wl%mituharu@math.s.chiba-u.ac.jp>
> Date: Mon, 27 Apr 2015 12:28:58 +0900
> From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
> Cc: 20410@debbugs.gnu.org
>
> >>>>> On Sun, 26 Apr 2015 18:04:56 +0300, Eli Zaretskii <eliz@gnu.org> said:
>
> >> 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.
>
> > Hmm... you are right, we could be more selective. Does the
> > alternative patch below work for you?
>
> Yes, this works fine. Thanks a lot.
>
> The previous one (for src/dispnew.c) caused redraw on another window
> on the same frame when I scrolled one window using set-window-vscroll,
> which may call adjust_frame_glyphs. But the current one (for
> src/xdisp.c) doesn't have such a problem.
Thanks, pushed as commit d89687b.
prev parent reply other threads:[~2015-04-27 15:17 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
2015-04-26 15:04 ` Eli Zaretskii
2015-04-27 3:28 ` YAMAMOTO Mitsuharu
2015-04-27 15:17 ` Eli Zaretskii [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83oam9wqgc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20410-done@debbugs.gnu.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
/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.