-
-
Notifications
You must be signed in to change notification settings - Fork 184
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
[Bug] The alternative editor does not work in Windows 11. #1082
Comments
Hi, I just looked into this issue, and was able to reproduce on win10 as well (so looks like this is not related specifically to win11). Based on the project's docs it seems the command was just defined incorrectly. Try the following in your <?xml version="1.0" encoding="UTF-8"?>
<commands>
<command alias="edit" value="cmd /c start "" C:\\Program\ Files\\Sublime\ Text\\subl.exe $f"/>
</commands> Here is a breakdown of the command:
We might need to add this clarification to the documentation - @ahadas please LMK what you think... |
Thank you for the explanation, the modified notation works great, changing the documentation would be helpful. |
Is there an existing issue for this?
Description
It looks like the configuration for the alternative editor in Windows 11 is not working properly. An error message appears when I try to edit a text:
The content of the
commands.xml
file:Excaping spaces using backslashes didn't work for me either.
Steps to reproduce
F4
key.ERROR
type entries.Expected behavior
Opening the new window of the editor
sublimetext
. The Notepad++ editor showed the same behaviour.Actual behavior
An error message appears when I try to edit a text.
Screenshots?
Error window (screenshot above)
muCommander version
Version information
muCommander
Version: 1.3.0
Build date: 2023/07/08
Build number: 057ec38
Java version
Java
Runtime version: 20.0.1
VM name: OpenJDK 64-Bit Server VM
VM version: 20.0.1+9
VM vendor: Eclipse Adoptium
Operating System type and version
OS
Name: Windows 11
Version: 10.0
Architecture: amd64
Relevant log output
No response
The text was updated successfully, but these errors were encountered: