Re: tramp (2.2.13.25.1); compilation-auto-jump-to-first-error slowness

[Dave Abrahams]

on Mon Jan 30 2017, Michael Albinus <michael.albinus-AT-gmx.de> wrote:

> Dave Abrahams <address@hidden> writes:
>
>> Hi Michael!
>
> Hi Dave,
>
>> emacs -Q
>> M-x load-library RET compile
>> M-x set-variable RET compilation-auto-jump-to-first-error RET t
>> C-x C-v <some remote host> RET
>> M-x compile RET cat <the attached file>
>>
>> You'll notice that emacs appears to hang for a long time.  Turning off
>> compilation-auto-jump-to-first-error makes it go away.
>
> The appended patch fixes this for me. Could you, pls, test?
>
> Best regards, Michael.
>
> diff --git a/lisp/tramp.el b/lisp/tramp.el
> index fc7fdd3..9ad510e 100644
> --- a/lisp/tramp.el
> +++ b/lisp/tramp.el
> @@ -3618,6 +3618,7 @@ connection buffer."
>    "Like `accept-process-output' for Tramp processes.
>  This is needed in order to hide `last-coding-system-used', which is set
>  for process communication also."
> +  (sit-for 0.01 'nodisp) ; If we are called inside a timer.
>    (with-current-buffer (process-buffer proc)
>      (let (buffer-read-only last-coding-system-used)
>        ;; Under Windows XP, accept-process-output doesn't return
>

Seems to work great!  It's a little odd that I see the remote shell
prompt and a little other garbage appear in the *compilation* window
before it is replaced by the expected contents, but that's just
cosmetic.

-- 
-Dave