SCP'ing Config To Remote Fails

[ihersom]

It appears that I am unable to copy my nvim config to the remote host, and I cannot figure out why this is happening. I have tried completely deleting my whole setup including cache and reinstalling.

[amitds1997]

Sorry about this. This might have been caused by the latest release. Can you downgrade to ~v0.2.9~ v0.3.9 and let me know. I think that should make it work. For me to handle this edge case, could you provide the output your SSH version info (ssh -V).

Edit: Version -> v0.3.9 not v0.2.9

[Diogo364]

I am having the same problem here. I tried manually change the configuration path my plugin config.lua file as shown in the documentation (see code below), but did not work.

return {
    "amitds1997/remote-nvim.nvim",
    version = "*",                 -- Pin to GitHub releases
    dependencies = {
        "nvim-lua/plenary.nvim",   -- For standard functions
        "MunifTanjim/nui.nvim",    -- To build the plugin UI
        "nvim-telescope/telescope.nvim", -- For picking b/w different remote methods
    },
    config = function()
        require("remote-nvim").setup({
            -- Remote configuration
            remote = {
                app_name = "nvim", -- This directly maps to the value NVIM_APPNAME. If you use any other paths for configuration, also make sure to set this.
                -- List of directories that should be copied over
                copy_dirs = {
                    -- What to copy to remote's Neovim config directory
                    config = {
                        base = "~/.dotfiles/.config/nvim/",
                        dirs = "*", -- Directories that should be copied over. "*" means all directories. To specify a subset, use a list like {"lazy", "mason"} where "lazy", "mason" are subdirectories}
                    }
                }
            }
        })
    end
}

Downgrading to v0.2.7 has worked, since v0.2.9 is not available in the release tags. Any idea of the cause of the issue?

[amitds1997]

Yeah, I do know the cause. Basically, when copying all dirs we use the syntax <base-path>/. to indicate the directory path <base-path> (in the latest release). This seems to not work on some systems. So, we see the error: no such filename . It somehow interprets . as a filename and not the denotion for current directory.

So, having the SSH client and system information would help me debug this.

[amitds1997]

Downgrading to v0.2.7 has worked, since v0.2.9 is not available in the release tags. Any idea of the cause of the issue?

Sorry, the version would be v0.3.9 (previous to the latest release)

[Diogo364]

Here are a few informations regarding the SSH and my system:

• OpenSSH_8.9p1 Ubuntu-3ubuntu0.7, OpenSSL 3.0.2 15 Mar 2022
• Ubuntu 22.04.4 LTS
• zsh 5.8.1 (x86_64-ubuntu-linux-gnu)

[ihersom]

Here is my ssh version:

OpenSSH_8.0p1, OpenSSL 1.1.1k FIPS 25 Mar 2021

NAME="Rocky Linux" VERSION="8.10 (Green Obsidian)"