unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jon Dufresne <jon.dufresne@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Need help debugging Emacs: emacsclient will not draw its contents sometimes
Date: Thu, 10 Sep 2015 11:20:20 -0700	[thread overview]
Message-ID: <CADhq2b5TLaFbSHZs1kceVesCo200-vXaKicUx6UzA2y+3e8S6Q@mail.gmail.com> (raw)
In-Reply-To: <83d1xq5m8f.fsf@gnu.org>

On Thu, Sep 10, 2015 at 8:26 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> This shows that Emacs examined the frames and windows, and decided
> that nothing requires to be redrawn.  Most redisplay cycles are like
> that, so this trace doesn't yet point to any problem.

For clarification on what I see, see the image: https://i.imgur.com/HWrwtUm.png

>
> If you type "M-x" into the (empty, AFAIU) client frame, does Emacs
> display the "M-x" prompt?

In the empty frame, no.

I sometimes also have an existing client frame that continues to work
normally. Typing M-x into this frame works normally.

>  Does it also redisplay some of the frame?

No.

> What happens if you type "M-x redraw-display RET"? does Emacs display
> anything?

Nothing. This is true if I type "M-x redraw-display RET" with the
drawn frame focused or the non-drawn frame focused. Would it help to
set a breakpoint before typing this command? If so where would you
expect something interesting?

Cheers,
Jon



  reply	other threads:[~2015-09-10 18:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08 13:00 Need help debugging Emacs: emacsclient will not draw its contents sometimes Jon Dufresne
2015-09-08 13:28 ` Tassilo Horn
2015-09-08 17:18 ` Eli Zaretskii
2015-09-08 18:58   ` Jon Dufresne
2015-09-08 19:16     ` Eli Zaretskii
2015-09-09 22:29       ` Jon Dufresne
2015-09-10 15:26         ` Eli Zaretskii
2015-09-10 18:20           ` Jon Dufresne [this message]
2015-09-10 18:46             ` Eli Zaretskii
2015-09-10 18:52               ` Jon Dufresne
2015-09-11  7:26                 ` Eli Zaretskii
2015-09-11 16:47                   ` Jon Dufresne
2015-09-14 10:09                     ` Eli Zaretskii
2015-09-23  0:51                       ` Jon Dufresne
2015-09-23  6:45                         ` Eli Zaretskii
2015-09-27 22:21                           ` Mike Kupfer
2015-09-28  6:39                             ` Eli Zaretskii
2016-02-16  1:07                             ` Mike Kupfer
2016-02-16 16:26                               ` Eli Zaretskii
2016-02-16 16:38                                 ` Kaushal Modi
2016-02-16 16:44                                   ` Eli Zaretskii
2016-02-16 17:06                                     ` Kaushal Modi
2016-02-17  2:05                                 ` Mike Kupfer
2016-02-17 20:02                                   ` Eli Zaretskii
2016-02-18  5:01                                     ` Mike Kupfer
2016-02-20 11:24                                       ` 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=CADhq2b5TLaFbSHZs1kceVesCo200-vXaKicUx6UzA2y+3e8S6Q@mail.gmail.com \
    --to=jon.dufresne@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).