From: Thierry Volpiatto <thievol@posteo.net>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 48067@debbugs.gnu.org
Subject: bug#48067: 28.0.50; Tramp error: cannot determine gio monitor
Date: Thu, 29 Apr 2021 08:42:57 +0000 [thread overview]
Message-ID: <87tunp5vfp.fsf@posteo.net> (raw)
In-Reply-To: <87tunpzf09.fsf@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]
Michael Albinus <michael.albinus@gmx.de> writes:
> Thierry Volpiatto <thievol@posteo.net> writes:
>
>> Update2:
>> More exactly the error occur when setting 'string':
>>
>> diff --git a/lisp/net/tramp-sh.el b/lisp/net/tramp-sh.el
>> index 4a3072ee346..8885bd55846 100644
>> --- a/lisp/net/tramp-sh.el
>> +++ b/lisp/net/tramp-sh.el
>> @@ -3748,7 +3748,8 @@ Supported arguments for GIO_USE_FILE_MONITOR environment variable:
>> (intern
>> (format "G%sFileMonitor" (capitalize (match-string 1 string)))))
>> (t (throw 'doesnt-work nil))))
>> - (setq string (substring string (match-end 0))))
>> + ;(setq string (substring string (match-end 0)))
>> + )
>>
>> ;; Delete empty lines.
>> (setq string (tramp-compat-string-replace "\n\n" "\n" string)
>>
>> With this commented line events occur as expected.
>
> So the problem is the match-end call. Here's a patch which might fix
> this.
No, it doesn't fix it, as long as string is set with
(setq string (substring string (match-end 0))) it doesn't work,
*rm-watch is never called.
> In case it doesn't work, pls give me ssh access to your machine.
Ok will prepare it.
> I would send you my public ssh key for access.
No thanks, PAM login will be enabled.
--
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 686 bytes --]
next prev parent reply other threads:[~2021-04-29 8:42 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
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 [this message]
[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=87tunp5vfp.fsf@posteo.net \
--to=thievol@posteo.net \
--cc=48067@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/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).