Skip to content

bug: Save conversation does not support blank space in pathname #1962

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 task done
karenwky opened this issue May 25, 2025 · 2 comments
Open
1 task done

bug: Save conversation does not support blank space in pathname #1962

karenwky opened this issue May 25, 2025 · 2 comments

Comments

@karenwky
Copy link

Checks

Operating system

MacOS

Expected behaviour

  • /save support blank space in pathname
  • /save support quotation mark (" and ') for pathname
/save "/Users/home/Document 1"

will export conversation successfully.

Actual behaviour

Error message:

Failed to export to [only pathname before space]: No such file or directory (os error 2)

Steps to reproduce

No response

@Konippi
Copy link
Contributor

Konippi commented May 25, 2025

Inserting an \ before the space works fine, but is this not enough?
I feel like this is probably the standard way to indicate a file path.

@karenwky
Copy link
Author

Inserting a \ doesn’t work and adding extra \ char in file name, the pathname is still read only up to the space.
The current workflow is already inconvenient, I have to delete the quotation marks when copying pathname from finder, manually adding char is causing more work for a simple save.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants