[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: What could be causing "# Interrupt received in operation"?
From: |
Michael Albinus |
Subject: |
Re: What could be causing "# Interrupt received in operation"? |
Date: |
Tue, 12 Mar 2019 16:26:54 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
Alex Bennée <address@hidden> writes:
> Hi,
Hi Alex,
> I had a working tramp setup with my box but at some point it broke,
> possibly with an update to emacs-26.1. Sometimes it starts working again
> but I haven't been able to detect a pattern, currently it is hard
> broken. I keep seeing a lot of these messages as it attempts to connect:
With partial information I have no chance to analyze. Please rerun your
test, preferred starting with "emacs -Q". Set tramp-verbose to 10,
prior connecting.
When it fails, pls send the whole Tramp debug buffer as attachment. As
it could contain non-ASCII characters, this would preserve the
information.
Don't worry if it is long.
> Alex Bennée
best regards, Michael.
- What could be causing "# Interrupt received in operation"?, Alex Bennée, 2019/03/12
- Re: What could be causing "# Interrupt received in operation"?,
Michael Albinus <=
- Re: What could be causing "# Interrupt received in operation"?, Alex Bennée, 2019/03/12
- Re: What could be causing "# Interrupt received in operation"?, Michael Albinus, 2019/03/12
- Re: What could be causing "# Interrupt received in operation"?, Robert Pluim, 2019/03/13
- Re: What could be causing "# Interrupt received in operation"?, Alex Bennée, 2019/03/13
- Re: What could be causing "# Interrupt received in operation"?, Michael Albinus, 2019/03/13
- Re: What could be causing "# Interrupt received in operation"?, Robert Pluim, 2019/03/13