bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#53283: 28.0.91; TRAMP SSHFS method not known by default


From: Philipp Stephani
Subject: bug#53283: 28.0.91; TRAMP SSHFS method not known by default
Date: Sat, 15 Jan 2022 19:17:46 +0100

Am Sa., 15. Jan. 2022 um 18:59 Uhr schrieb Michael Albinus
<michael.albinus@gmx.de>:
>
> Philipp Stephani <p.stephani2@gmail.com> writes:
>
> Hi Philipp,
>
> > $ emacs -Q -batch -eval '(print (directory-files "/sshfs:localhost:/sys/"))'
> > , Method ‘sshfs’ is not known.
>
> > But it would be great if this could just work out of the box.
>
> It works for me:
>
> --8<---------------cut here---------------start------------->8---
> $ emacs -Q -batch -eval '(print (directory-files "/sshfs:localhost:/sys/"))'
>
> ("." ".." "block" "bus" "class" "dev" "devices" "firmware" "fs" "hypervisor" 
> "kernel" "module" "power")
> --8<---------------cut here---------------end--------------->8---
>
> What happens, if you try the following:
>
> --8<---------------cut here---------------start------------->8---
> $ emacs -Q -batch -l tramp -eval '(print (mapcar (quote car) tramp-methods))'
>
> ("adb" "ftp" "sftp" "nextcloud" "mtp" "gdrive" "davs" "dav" "afp" "rclone" 
> "fcp" "psftp" "pscp" "plinkx" "plink" "krlogin" "ksu" "doas" "sudo" "sg" "su" 
> "nc" "telnet" "sshx" "ssh" "remsh" "rsh" "rsync" "scpx" "scp" "remcp" "rcp" 
> "smb" "sshfs" "sudoedit")
> --8<---------------cut here---------------end--------------->8---
>
> In my case, you see the supported Tramp methods, including "sshfs".

$ src/emacs -Q -batch -l tramp -eval '(print (mapcar (quote car)
tramp-methods))'
("adb" "ftp" "sftp" "nextcloud" "mtp" "gdrive" "davs" "dav" "afp"
"rclone" "fcp" "psftp" "pscp" "plinkx" "plink" "krlogin" "ksu" "doas"
"sudo" "sg" "su" "nc" "telnet" "sshx" "ssh" "remsh" "rsh" "rsync"
"scpx" "scp" "remcp" "rcp" "smb" "sudoedit")

It does work on the master branch (the bug report is for Emacs 28), so
looks like it has been fixed in the meantime? Maybe it would be
possible to backport the fix onto the release branch.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]