Michael Albinus <[email protected]> writes:
Hi Tassilo & Philip,
>> And Michael, looking at the code I have the feeling that
>> tramp-gvfs-dbus-event-vector should be buffer-local but it's set
>> globally and then causes the issue...
>
> Somehow. tramp-gvfs tries to catch *any* D-Bus error it sees, even if it
> isn't responsible for. And from the error itself it cannot determine
> whether it is meant for tramp-gvfs, the struct
>
> (dbus-event :session 3 48 "org.freedesktop.DBus" ":1.220203" nil nil
> "org.freedesktop.DBus.Error.ServiceUnknown" dbus-call-method-handler (:string
> "The name is not activatable"))
>
> tells us that it is an error ("3") with the serial "48" (not relevant,
> D-Bus internal counter) from service "org.freedesktop.DBus" (the general
> purpose D-Bus service) sent to service ":1.220203" (that's us,
> Emacs). So there is no chance to filter tramp-gvfs events out.
>
> A buffer-local tramp-gvfs-dbus-event-vector doesn't help; the D-Bus
> event is received asynchronously, and it can happen any time Emacs reads
> incoming events. No guarantee that the respective buffer is current.
>
> The appended patch changes tramp-gvfs-dbus-event-vector being let-bound
> while tramp-gvfs is in action. There is the possible threat that a
> related D-Bus event arrives too late, due to time-outs or so, but let's
> see how it works.
>
> Could you pls check the patch?
No further comments, so I've pushed this to the emacs-28 branch. In a
couple of days I'll close it, unless there are problems reported by you.
>> Bye,
>> Tassilo
Best regards, Michael.
_______________________________________________
bug-auctex mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-auctex
