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: Eli Zaretskii <eliz@gnu.org>, larsi@gnus.org, 55832@debbugs.gnu.org
Subject: bug#55832: 28.1; Emacs crashes when using tramp from helm in emacs-29
Date: Tue, 14 Jun 2022 13:39:16 +0200	[thread overview]
Message-ID: <87bkuvxymz.fsf@gmx.de> (raw)
In-Reply-To: <87mteh20qo.fsf@posteo.net> (Thierry Volpiatto's message of "Sun,  12 Jun 2022 18:16:23 +0000")

Thierry Volpiatto <thievol@posteo.net> writes:

Hi Thierry,

> I have a function wrote long time ago to delete tramp connections which
> is not working (or most of the time not working) because it uses
> tramp-list-connections which is itself broken (unexpectedly it worked
> only once today don't know why).
>
> The test (tramp-connection-property-p key "process-buffer") is wrong IMO
> according to the data fetched from tramp-cache-data,

I don't understand this. tramp-connection-property-p just tests whether
a connection property is defined. It does not check the value of this property.

> here a function based
> on tramp-list-connections to illustrate the data fetched here from a
> sudo connection:
>
>     (defun tv/list-tramp-connections ()
>       (cl-loop with tramp-verbose = 0
>                for key being the hash-keys in tramp-cache-data
>                using (hash-value val)
>                when (and (tramp-file-name-p key)
>     		     (null (tramp-file-name-localname key))
>                          ;; (tramp-connection-property-p key "process-buffer"))
>                          )
>                collect (list key (cl-loop for k being the hash-keys in val
>                                           using (hash-value v)
>                                           collect (list k v))))

Sorry, but I'm not fluent with the cl-loop syntax.

> The function for a sudo connection returns:
>
> (((tramp-file-name "sudo"
>                    #("root" 0 4
>                      (tramp-default t))
>                    nil
>                    #("IPad-S340" 0 9
>                      (tramp-default t))
>                    nil nil nil)
>   (("process-buffer" nil)
>    ("null-device" "/dev/null")
>    ("uid-string" "UNKNOWN")
>    ("gid-string" "UNKNOWN")
>    ("uid-integer" -1)
>    ("gid-integer" -1)
>    ("first-password-request" nil)
>    ("uname" "Linux 5.15.0-33-generic")
>    ("locale" "LC_ALL=en_US.utf8")
>    ("test" "test")
>    ("remote-path"
>     ("/bin" "/usr/bin" "/sbin" "/usr/sbin" "/usr/local/bin" "/usr/local/sbin"))
>    ("pipe-buf" 4096)
>    ("remote-shell" "/bin/sh")
>    ("~root" "/root")
>    ("file-exists" "test -e")
>    ("stat" "env QUOTING_STYLE=locale \\stat")
>    ("case-insensitive" nil)
>    ("readlink" "\\readlink"))))
>
> As you can see "process-buffer" is listed in the cdr but not the car of
> result so tramp-list-connections always returns nil because
> (tramp-connection-property-p key "process-buffer") always returns nil.
>
> Seems the cdr is the same as what found in ~/.emacs.d/tramp.

Sorry, I cannot follow what you try to explain. Could you please show me
an example, both the value of tramp-cache-data, and the result
tramp-list-connections is returning?

> Maybe it can help you to understand what's going wrong.

At least it is unrelated to the problem of this bug report.

> Thanks.

Best regards, Michael.





  reply	other threads:[~2022-06-14 11:39 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 15:16 bug#55832: 28.1; Emacs crashes when using tramp from helm in emacs-29 Thierry Volpiatto
2022-06-07 16:08 ` Eli Zaretskii
2022-06-07 17:02   ` Thierry Volpiatto
2022-06-07 17:18     ` Eli Zaretskii
2022-06-07 18:33       ` Thierry Volpiatto
2022-06-07 18:53         ` Eli Zaretskii
2022-06-07 19:20   ` Thierry Volpiatto
2022-06-08 13:01     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-08 16:30     ` Eli Zaretskii
2022-06-08 18:17       ` Lars Ingebrigtsen
2022-06-08 18:25         ` Eli Zaretskii
2022-06-09 10:34           ` Lars Ingebrigtsen
2022-06-09 10:42           ` Thierry Volpiatto
2022-06-09 13:05             ` Eli Zaretskii
2022-06-09 15:18               ` Thierry Volpiatto
2022-06-09 15:29                 ` Lars Ingebrigtsen
2022-06-09 16:36                 ` Eli Zaretskii
2022-06-09 16:51                   ` Thierry Volpiatto
2022-06-09 17:48                     ` Eli Zaretskii
2022-06-09 18:28                       ` Thierry Volpiatto
2022-06-09 18:55                         ` Eli Zaretskii
2022-06-10  7:53                           ` Michael Albinus
2022-06-10 10:00                             ` Thierry Volpiatto
2022-06-10 12:20                               ` Michael Albinus
2022-06-11  6:14                                 ` Thierry Volpiatto
2022-06-11 19:27                                   ` Michael Albinus
2022-06-11 19:46                                     ` Thierry Volpiatto
2022-06-11 20:07                                       ` Michael Albinus
2022-06-11 20:12                                         ` Thierry Volpiatto
2022-06-12 18:16                                         ` Thierry Volpiatto
2022-06-14 11:39                                           ` Michael Albinus [this message]
2022-06-14 11:49                                             ` Thierry Volpiatto
2022-06-09 15:37               ` Thierry Volpiatto
2022-06-14 11:05 ` Michael Albinus
2022-06-14 11:36   ` Thierry Volpiatto
2022-06-14 11:44     ` Michael Albinus
2022-06-14 17:42 ` Michael Albinus
2022-06-16 17:27 ` Michael Albinus
2022-06-16 18:11   ` Thierry Volpiatto
2022-06-17 16:54     ` Michael Albinus
2022-06-17 17:10       ` Thierry Volpiatto
2022-06-19 14:25         ` Michael Albinus
2022-06-19 16:21           ` Thierry Volpiatto
2022-06-19 17:51             ` Michael Albinus
2022-06-21  8:24             ` Michael Albinus
2022-06-21  9:35               ` 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=87bkuvxymz.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=55832@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.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).