unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Greg Klanderman <gak@klanderman.net>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>, emacs-devel@gnu.org
Subject: Re: gnus-server-to-method crash on virtual server name in gnus-secondary-select-methods
Date: Tue, 26 Jan 2021 11:51:15 +0100	[thread overview]
Message-ID: <878s8gug2k.fsf@gmail.com> (raw)
In-Reply-To: 8735yogb1z.fsf@lwm.klanderman.net

[-- Attachment #1: Type: text/plain, Size: 1554 bytes --]

>>>>> On Mon, 25 Jan 2021 12:51:04 -0500, Greg Klanderman <gak@klanderman.net> said:

    Greg> My biggest concern now with fully transitioning, other than a lot more
    Greg> time, is how slow it is over ssh forwarded X11.  As I said xemacs is
    Greg> perfectly snappy, but Emacs is taking sometimes 30-60+ sec just to
    Greg> create a new frame.

Does the attached patch improve frame creation?

    Greg> I turned off tooltips which seemed to be causing much of the latency
    Greg> issues, then it seemed that toolbars & menubars were the issue because
    Greg> after dragging another window over an Emacs frame, everything would
    Greg> redraw immediately but the menubars and toolbars, which could again
    Greg> take 30-60+ seconds with Emacs being essentially frozen to input.
    Greg> Switching gtk to lucid (Debian testing) did not make appreciable
    Greg> difference.

    Greg> I've now noticed that the problem only occurs when a frame of
    Greg> an Emacs is dragged over another frame of the same Emacs, so I suspect
    Greg> some problem with the event handling loop.  I will submit a bug
    Greg> report; this is perfectly reproducible with emacs -Q after ssh'ing
    Greg> from my work laptop (on home network) to my work desktop (in office
    Greg> 30mi away) and then back to my personal home desktop, even with
    Greg> tooltips/tool bars/menu bars/scroll bars off.

Which X server are you using? I donʼt see this at all (but admittedly
the two machines in question are a meter apart)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: check_x_display_less.patch --]
[-- Type: text/x-diff, Size: 593 bytes --]

diff --git a/src/xterm.c b/src/xterm.c
index 2e0407aff4..448e06eb8b 100644
--- a/src/xterm.c
+++ b/src/xterm.c
@@ -12709,8 +12709,6 @@ x_term_init (Lisp_Object display_name, char *xrm_option, char *resource_name)
       ++x_initialized;
     }
 
-  if (! x_display_ok (SSDATA (display_name)))
-    error ("Display %s can't be opened", SSDATA (display_name));
 
 #ifdef USE_GTK
   {
@@ -12838,6 +12836,7 @@ #define NUM_ARGV 10
   /* Detect failure.  */
   if (dpy == 0)
     {
+      error ("Display %s can't be opened", SSDATA (display_name));
       unblock_input ();
       return 0;
     }

  parent reply	other threads:[~2021-01-26 10:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07 18:14 gnus-server-to-method crash on virtual server name in gnus-secondary-select-methods Greg Klanderman
2021-01-08 18:28 ` Eric Abrahamsen
2021-01-18 18:07   ` Greg Klanderman
2021-01-21 23:50     ` Eric Abrahamsen
2021-01-25 17:51       ` Greg Klanderman
2021-01-25 18:41         ` Eric Abrahamsen
2021-01-26 19:11           ` Greg Klanderman
2021-01-26 10:51         ` Robert Pluim [this message]
2021-01-26 19:09           ` slow X11 frame creation and refresh after occlusion (was: gnus-server-to-method crash on virtual server name in gnus-secondary-select-methods) Greg Klanderman
2021-01-27  8:07             ` slow X11 frame creation and refresh after occlusion Robert Pluim
2021-01-30 19:32               ` Greg Klanderman
2021-02-01  8:56                 ` Robert Pluim
2021-02-03 21:52                   ` Greg Klanderman
2021-02-04  8:24                     ` Robert Pluim
2021-02-04 21:14                       ` Greg Klanderman
2021-02-05  9:53                         ` Robert Pluim
2021-02-05 17:12                           ` Greg Klanderman
2021-01-30 22:21               ` Greg Klanderman

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=878s8gug2k.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=eric@ericabrahamsen.net \
    --cc=gak@klanderman.net \
    /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).