If I have a folder named ad hoc stuff, using the Cursor shell (cursor "ad hoc stuff") to try to open it does not work properly. It simply creates new files named ad, hoc, and stuff, respectively, in the currently active editor.
VSCode’s code command handles this case properly.
Steps to Reproduce
Create a folder with spaces in the name
Try to open it with the cursor shell command
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
If you try to open a file with Cursor CLI that has a space in the name, and it’s properly quoted or escaped, Cursor cannot open it.
# This opens "my" and "file.txt" as two separate files, since you're passing two filenames.
cursor my file.txt
# This should open one file called `my file.txt`, because the filename is quoted. But, it incorrectly opens two!
cursor "my file.txt"
# The space is escaped here, so it should still open a file called `my file.txt`.
cursor my\ file.txt
Steps to Reproduce
cursor “my file.txt”
or
cursor my\ file.txt
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Any news on fixing this?
This is kind of a major thing that is blocking some critical things.
Both the ““ and direct escaping on path is really base level stuff as we have people working on modern OSs that allow not just spaces but special characters in the paths.
If git supports these then having and IDE that does not is a big deal.
The fact that this works on Windows makes this even worse, as we have teams that need to work on both.