Vim Sessions with Escape Characters Not Restored?

[nabsiddiqui]

I seem to be able to cd into a directory and edit a file in vim and have it restored. When I just type the full path name of the with vim it fails to restore. This is worse when there are escape characters, such as spaces in the name.

[JohnStarich]

I also have this problem when restoring vim. If the file argument has a space in it, it fails to open vim.

[bruno-]

Care to provide tmux-resurrect last file that fails?

Did you guys try restoring full vim sessions? https://github.com/tmux-plugins/tmux-resurrect/blob/master/docs/restoring_vim_and_neovim_sessions.md That should get around file naming problems as the command that will be called is vim -S. And then vim will take care of opening files with escape chars.

[JohnStarich]

Here's my last file. Basically it opened vim in such a way that it thought it was opening two files, neither of which exist.
last.txt
My use case for opening a file like this is that I run a utility to open iCloud Drive documents on my Mac. The iCloud Drive folder path contains "Mobile Documents" with the space.

The vim command I had run was actually vim ~/Library/Mobile\ Documents/iCloud\~com\~chintanghate\~Falcon/Documents/Notebooks/Personal/TODO.md
Note the backslash-escaped space between "Mobile" and "Documents", which is not present in the restore file or the re-run command after the restore.

Regarding vim sessions, my workflow has typically not needed a full session restore. I have toyed around with them before, but they didn't quite suit me at the time.
Rather than only affecting vim, however, this seems to be a more general problem.