unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Thierry Volpiatto <thievol@posteo.net>
Cc: 48067@debbugs.gnu.org
Subject: bug#48067: 28.0.50; Tramp error: cannot determine gio monitor
Date: Wed, 28 Apr 2021 09:38:27 +0200	[thread overview]
Message-ID: <87eeeudfkc.fsf@gmx.de> (raw)
In-Reply-To: <87h7jrj664.fsf@posteo.net> (Thierry Volpiatto's message of "Wed,  28 Apr 2021 05:59:29 +0000")

[-- Attachment #1: Type: text/plain, Size: 396 bytes --]

Thierry Volpiatto <thievol@posteo.net> writes:

>> Hi Michael,

Hi Thierry,

> More exactly, it seems gio command is correctly extracted in
> `tramp-sh-handle-file-notify-add-watch` with
> (tramp-get-remote-gio-monitor v) but later in the process filter
> (tramp-connection-property-p proc "gio-file-monitor") returns nil.

Does the appended patch fixes this?

> Thanks.

Best regards, Michael.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 1755 bytes --]

*** /tmp/ediffdHBFUW	2021-04-28 09:36:25.118483724 +0200
--- /home/albinus/src/tramp/lisp/tramp-sh.el	2021-04-28 09:36:03.920592244 +0200
***************
*** 3731,3737 ****
        ;; Determine monitor name.
        (unless (tramp-connection-property-p proc "gio-file-monitor")
          (cond
!          ;; We have seen this on cygwin gio and on emba.  Let's make some assumptions.
           ((string-match
             "Can't find module 'help' specified in GIO_USE_FILE_MONITOR" string)
            (cond
--- 3731,3738 ----
        ;; Determine monitor name.
        (unless (tramp-connection-property-p proc "gio-file-monitor")
          (cond
!          ;; We have seen this on cygwin gio and on emba.  Let's make
!          ;; some assumptions.
           ((string-match
             "Can't find module 'help' specified in GIO_USE_FILE_MONITOR" string)
            (cond
***************
*** 3741,3747 ****
             ((eq system-type 'cygwin)
              (tramp-set-connection-property
               proc "gio-file-monitor" 'GPollFileMonitor))
!            (t (tramp-error proc 'file-error "Cannot determine gio monitor"))))
           ;; TODO: What happens, if several monitor names are reported?
           ((string-match "\
  Supported arguments for GIO_USE_FILE_MONITOR environment variable:
--- 3742,3749 ----
             ((eq system-type 'cygwin)
              (tramp-set-connection-property
               proc "gio-file-monitor" 'GPollFileMonitor))
!            (t (tramp-set-connection-property
!                proc "gio-file-monitor" tramp-cache-undefined))))
           ;; TODO: What happens, if several monitor names are reported?
           ((string-match "\
  Supported arguments for GIO_USE_FILE_MONITOR environment variable:

  reply	other threads:[~2021-04-28  7:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27 16:58 bug#48067: 28.0.50; Tramp error: cannot determine gio monitor Thierry Volpiatto
2021-04-27 19:19 ` Michael Albinus
2021-04-27 21:38   ` Thierry Volpiatto
2021-04-28  5:59     ` Thierry Volpiatto
2021-04-28  7:38       ` Michael Albinus [this message]
2021-04-28 10:56         ` Thierry Volpiatto
2021-04-28 11:16           ` Michael Albinus
     [not found]             ` <87czuefu94.fsf@posteo.net>
2021-04-28 13:57               ` Michael Albinus
     [not found]                 ` <87zgxi1nci.fsf@posteo.net>
     [not found]                   ` <87zgxixx8j.fsf@posteo.net>
2021-04-28 16:25                     ` Michael Albinus
     [not found]                       ` <87tunqxrii.fsf@posteo.net>
2021-04-28 17:39                         ` Michael Albinus
2021-04-28 18:28                           ` Thierry Volpiatto
2021-04-28 18:47                           ` Thierry Volpiatto
2021-04-28 18:56                             ` Michael Albinus
2021-04-29  5:33                               ` Thierry Volpiatto
2021-04-29  7:17                                 ` Michael Albinus
2021-04-29  7:48                                   ` Thierry Volpiatto
2021-04-29  6:09                               ` Thierry Volpiatto
2021-04-29  6:46                                 ` Thierry Volpiatto
2021-04-29  8:11                                   ` Michael Albinus
2021-04-29  8:42                                     ` Thierry Volpiatto
     [not found]                                     ` <87r1it5u0q.fsf@posteo.net>
     [not found]                                       ` <87pmydz9my.fsf@gmx.de>
2021-04-29 10:55                                         ` Michael Albinus
2021-04-29 11:26                                           ` Thierry Volpiatto
2021-04-29 11:30                                             ` Thierry Volpiatto
2021-04-29 13:09                                               ` Michael Albinus
2021-04-29 13:07                                             ` Michael Albinus
2021-04-29 13:20                                               ` Thierry Volpiatto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87eeeudfkc.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=48067@debbugs.gnu.org \
    --cc=thievol@posteo.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).