From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 19721@debbugs.gnu.org
Subject: bug#19721: 25.0.50; Mode-line not redrawn with expose events
Date: Sun, 01 Feb 2015 14:40:40 +0900 [thread overview]
Message-ID: <wl61bm6vfr.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <83lhkjjhsp.fsf@gnu.org>
>>>>> On Sat, 31 Jan 2015 13:44:38 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> With this patch, the mode-lines are redrawn when they are exposed.
>> But I also observe that a mode-line part is not updated with the
>> last C-x o (see the 3rd mode-line in the screenshot) with the
>> previously mentioned procedure on the Mac port. Strangely, if I
>> try C-x o three times further, then the second mode-line part is
>> also not updated.
> Right. Which means it is not enough to avoid disabling the mode
> line, we must actually force its redrawing afterwards.
> How about the following patch instead of the previous one?
Now mode-lines get updated with C-x o again, but the original issue
still remains and I could reproduce it with the original procedure on
Cent OS 5.11.
If I apply both changes, mode-lines are redrawn when exposed, but some
of them are not updated with C-x o.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2015-02-01 5:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 10:51 bug#19721: 25.0.50; Mode-line not redrawn with expose events YAMAMOTO Mitsuharu
2015-01-31 10:31 ` YAMAMOTO Mitsuharu
2015-01-31 11:09 ` Eli Zaretskii
2015-01-31 10:53 ` Eli Zaretskii
2015-01-31 11:37 ` YAMAMOTO Mitsuharu
2015-01-31 11:44 ` Eli Zaretskii
2015-02-01 5:40 ` YAMAMOTO Mitsuharu [this message]
2015-02-01 8:51 ` martin rudalics
2015-02-01 15:44 ` Eli Zaretskii
2015-02-01 16:30 ` martin rudalics
2015-02-01 17:27 ` Eli Zaretskii
2015-02-01 18:09 ` martin rudalics
2015-02-01 18:37 ` Eli Zaretskii
2015-02-02 3:24 ` YAMAMOTO Mitsuharu
2015-02-01 15:33 ` Eli Zaretskii
2015-02-02 3:27 ` YAMAMOTO Mitsuharu
2015-02-02 16:16 ` 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
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=wl61bm6vfr.wl%mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=19721@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 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).