[debbugs-tracker] bug#29817: closed (26.0.50; Saving files on remotes very slow if shell buffer is open)

[GNU bug Tracking System]

Your message dated Sun, 29 Sep 2019 01:32:44 +0200
with message-id <CADwFkmnr8uRt=4Xgzo5hg2kKon4_WDGSjX-DD=address@hidden>
and subject line Re: bug#29817: 26.0.50; Saving files on remotes very slow if 
shell buffer is open
has caused the debbugs.gnu.org bug report #29817,
regarding 26.0.50; Saving files on remotes very slow if shell buffer is open
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
29817: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=29817
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 26.0.50; Saving files on remotes very slow if shell buffer is open
>
>
>
>
> Date: 
>
> Fri, 22 Dec 2017 21:38:34 +0100
>
>
>
>
> Hi,
>
> I am observing a rather weird interaction between tramp and comint. Saving and
> editing files on remotes is pretty snappy till I open a shell buffer. Once a
> shell is open it can take good 10s to save a buffer. Editing and navigation are
> also impaired.
>
> Steps to reproduce:
>
>   1) emacs -Q
>   2) /ssh:remote-host:tmp.txt
>   3) save tmp.txt (snappy)
>   4) M-x shell
>   5) back to tmp.txt and save (terribly slow)
>
> Can anyone reproduce this?
>
>   Vitalie
>
> In GNU Emacs 26.0.50 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.18.9) of 
> 2017-12-22 built on galago
> Repository revision: 5d45ba1a05bccc53d52422e867f378a0adeb8970
> Windowing system distributor 'The X.Org Foundation', version 11.0.11804000
> System Description:     Ubuntu 16.04.2 LTS
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#29817: 26.0.50; Saving files on remotes very slow if shell buffer is open
>
>
>
>
> Date: 
>
> Sun, 29 Sep 2019 01:32:44 +0200
>
>
>
>
> Vitalie Spinu <address@hidden> writes:
>
> >>> On Fri, Dec 22 2017 15:44, Glenn Morris wrote:
> >
> >> This is a 6-month old development version, so the first thing to ask is:
> >> can you yourself reproduce this with the current emacs-26 branch?
> >
> > Damn. I actually pulled and recompiled before sending ... but it wasn't on
> > master :-/
> >
> > It's fixed in master. Thanks!
>
> Great, I'm therefore closing this bug.
>
> Best regards,
> Stefan Kangas
>
>
> --- End Message ---