Re: What could be causing "# Interrupt received in operation"?

[Alex Bennée]

Robert Pluim <address@hidden> writes:

>>>>>> On Tue, 12 Mar 2019 17:04:15 +0000, Alex Bennée <address@hidden> said:
>     Alex> Which had a logic fault that it was failing to check
>     Alex> local-mu4e before adding to the load-path. You would think
>     Alex> having a nil in your load-path would cause more complaints
>     Alex> overall but no just obscure hard to track down failures in
>     Alex> tramp :-/
>
> In `load-path', nil → `default-directory', which by its very nature is
> dependent on which buffer you happen to be in, however itʼs allowed.

I did try and track down where in tramp this might have broken things
but I had no joy. I think it is somewhere in:

  tramp-maybe-open-connection

But I guess the condition-case stops be setting up break on error.
Unless there is a way to override that?

>
> Robert


--
Alex Bennée