-
Notifications
You must be signed in to change notification settings - Fork 44
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
[Feature Request] Officially support "/" as path separator #827
Comments
In july 2014 (regarding rev 1713) we had a short discussion about this. I thought basically the same thing as you, that we could use whichever path separator / or \ because wx will handle it correctly anyway but Martin was of another opinion. The help since old specifies \ as canonical separator and basic reason was complying to the HW1 standard. I won't complain about removing the warning about which path separator is used, though. PS. In DOS one would use / to specify parameters or switches to a program, never the paths, but this is very much irrelevant now. |
I propose to introduce a separate settings checkbox |
… ODF for HW1-compatibility' is set GrandOrgue#827
… ODF for HW1-compatibility' is set GrandOrgue#827
Discussed in #821
Originally posted by vpoguru October 31, 2021
The path separator "/" already works in all 3 operating systems, but GrandOrgue gives a warning (at least if "Perform strict ODF" is checked).
Linux and macOS terminals work with "/" anyway, and Windows supports this separator as well. If I remember correctly, the "/" separator could even be used (unofficially) in DOS times.
The text was updated successfully, but these errors were encountered: