I'm trying to mount my remote server using curlftpfs but I get a stupid error because the password is too long in the command

even with the window maximized, now I know this can be solved with \ or / but I rarely ever did that myself in 10 years of linux usage, I'm not a newbie, but whenever those showed up in tasks I had to do, I would be copypasting them from a website.

I know it's because the password is too long for the window because I get thrown the last characters of the password in the error following entering the command :

I hid the characters even if its a randomly generated 64 characters password, you never know

How can I correct this exactly?

I suspect it's not length, but presence of ";" (or another Bash metacharacter) causing it to be interpreted as a new command.

Either way, the solution is to wrap the password in single quotes to ensure all characters are treated as literals.

Rather than on command line, username and password for curlftpfs could be specified in ~/.netrc:
The file must be readable only by owner, or it won't be accepted.

thanks! I forgot I can do this, I do it often when using dnuos -L 'folder name of album' when looking at bitrates

I wonder if it will think the single quotes are part of the password now though, I'll check back soon and tell you when I get back home and do it.

It wont, because it doesn't see them - everything you type into the shell is interpreted by the shell and split into individual components ("words") before identifying which of those words are commands and which are arguments and eventually executing the relevant programs with arguments. The single quotes instruct the shell not to perform that splitting within them, so their enclosed text is treated as a single unit, but the quotes are essentially consumed during this step; they do not get passed through to the command.

See https://www.gnu.org/software/bash/manual/html_node/Shell-Operation.html

Another way to avoid word splitting is to put the password in a config file, as in Shruggy's post, which is a better option (though if you can use certificates and disable password logins that's even better).

Turns out it's true, curlftpfs worked, but the mnt/ftp/ folder is not recognized as a folder in Caja, I'll try to get in there through terminal but if it doesn't work with the gui, then all reasons I wanted to try curlftpfs for are nullified and I might just as well connect through Caja like with Nautilus. It's apparently faster to use curlftpfs than ssh/sftp hence why I'm going this route. I will consider Shruggy's post once I get this working right from my vps's own instructions wiki though.