From: Yuan MEI <yuan.mei.list@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Redisplay issue
Date: Sat, 28 Nov 2015 00:27:13 -0800 [thread overview]
Message-ID: <CANGGyWZSVT7V7N5aueVpXyO16ULDF6M_M6TtCn6E33hPQ1_1Xg@mail.gmail.com> (raw)
In-Reply-To: <83fuzqr1iz.fsf@gnu.org>
On Sat, Nov 28, 2015 at 12:06 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Fri, 27 Nov 2015 14:31:55 -0800
>> From: Yuan MEI <yuan.mei.list@gmail.com>
>>
>> Sometimes when I switch to another virtual desktop then come back
>> to emacs
>
> What is a "virtual desktop" in this case?
It is FVWM virtual desktop. I don't know how to put it better. To
further narrow down the issue: when the GUI frame is hidden behind
another window then exposed, sometimes it exhibits the same symptom.
This redisplay issue only happens in a recent version of emacs. I
don't recall encountering it for instance half a year ago.
>
>> the entire frame shows only the background color, no letter
>> or only part of the frame is visible. This does not happen all the
>> time though. I just happened to capture a screenshot (attached, I
>> hope the mailing server accepts it.)
>
> The screenshot shows a text-mode Emacs frame, AFAICT. Does this
> happen only with text-mode frames, or do you see that in GUI frames as
> well?
The screenshot is in fact a GUI frame. I just configured it to be
minimalistic. A `default' frame started with emacs -Q has the same
redisplay problem.
Yuan
next prev parent reply other threads:[~2015-11-28 8:27 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 22:31 Redisplay issue Yuan MEI
2015-11-28 8:06 ` Eli Zaretskii
2015-11-28 8:27 ` Yuan MEI [this message]
2015-11-28 9:44 ` Eli Zaretskii
2015-11-28 20:19 ` Yuan MEI
2015-11-28 20:49 ` Eli Zaretskii
2015-11-29 2:54 ` Yuan MEI
2015-11-29 15:42 ` Eli Zaretskii
2015-11-29 23:35 ` Yuan MEI
2015-11-30 16:16 ` Eli Zaretskii
2015-12-01 4:51 ` Yuan MEI
2015-12-01 16:01 ` Eli Zaretskii
2015-12-02 4:35 ` Yuan MEI
2015-12-02 13:57 ` Eli Zaretskii
2015-12-03 4:55 ` Yuan MEI
2015-12-03 7:47 ` Eli Zaretskii
2015-12-03 8:09 ` Yuan MEI
2015-12-03 10:23 ` Eli Zaretskii
2015-12-03 18:16 ` martin rudalics
2015-12-03 21:23 ` Yuan MEI
2015-12-04 8:08 ` martin rudalics
2015-12-04 8:30 ` Yuan MEI
2015-12-04 8:48 ` martin rudalics
2015-12-04 8:54 ` Yuan MEI
2015-12-04 8:56 ` martin rudalics
2015-12-04 9:00 ` Yuan MEI
2015-12-04 9:05 ` martin rudalics
2015-12-04 9:47 ` Eli Zaretskii
2015-12-04 10:21 ` martin rudalics
2015-12-04 11:01 ` Eli Zaretskii
2015-12-04 11:12 ` Eli Zaretskii
2015-12-05 0:25 ` YAMAMOTO Mitsuharu
2015-12-05 9:17 ` Eli Zaretskii
2015-12-06 0:49 ` Yuan MEI
2015-12-07 3:33 ` YAMAMOTO Mitsuharu
2015-12-07 17:19 ` Eli Zaretskii
2015-12-08 4:03 ` YAMAMOTO Mitsuharu
2015-12-11 8:48 ` Eli Zaretskii
2015-11-28 21:44 ` joakim
2015-11-29 0:14 ` Yuan MEI
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=CANGGyWZSVT7V7N5aueVpXyO16ULDF6M_M6TtCn6E33hPQ1_1Xg@mail.gmail.com \
--to=yuan.mei.list@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).