Closed fcolledani-solari closed 1 year ago
Hi there!
Does the config path exist on your machine?
Please try with
mkdir -p $HOME/.config/termscp
Yes, this gif shows the step to reproduce the issue.
WSL2...
Does the file $HOME/.config/termscp/config.toml
exist?
Is the env variable $XDG_CONFIG_HOME
unset?
Yes, the contents of config.toml are in the image. The env var is not set
Please try running termscp with -D
option and send me the log file located at $HOME/.config/termscp.log
You will have no issues guessing the password. It is not the first you will think of, but the second one.
It's failing the parse of your ssh config. Probably contains some non standard keywords.
2023-02-27T13:35:49.233729543Z [TRACE] (1) remotefs_ssh::ssh::config: [/root/.cargo/registry/src/github.com-1ecc6299db9ec823/remotefs-ssh-0.1.3/src/ssh/config.rs:68] Parsing configuration at /home/.../.ssh/config
.
Try to remove the configuration path from your configuration.
Replied in private.
Fixed: the problem was that ssh_config_path was set by default to ~/.ssh/config
but without checking whether this file exists. So from 0.11.1 this value will be set only if the file exists.
Description
Hi Veeso! TermSCP installs on Windows Terminal, but it does not connect to anything. Ather filling the connection form, this is the response I get:
Look at the image and the destination URL, you will appreciate them
Changes
Support WSL2
Implementation
No idea, most likely some internal file descriptors are not supported by WSL.