Thank you for the PR.
However, the current implementation is intentional.
Please let me have time to consider it.

I have not looked at the code, but as a user would love to see --new go away - it breaks the assumed CLI behavior of myself and many programs calling cot.

Considering that CotEditor aims to provide a macOS-native experience, I guess that this behavior was originally intended to align with how open -a TextEdit <filename> works, where a new file is not automatically created. It makes sense that the default behavior doesn’t create new files without an explicit flag like --new.

That said, I think it is much more convenient when a new file is automatically created. What do you think about introducing an environment variable to control this behavior? For example, if COT_CREATE_NEW_FILES=true is set, CotEditor could create new files even without the --new flag.

Considering that CotEditor aims to provide a macOS-native experience, I guess that this behavior was originally intended to align with how open -a TextEdit <filename> works, where a new file is not automatically created. It makes sense that the default behavior doesn’t create new files without an explicit flag like --new.

That said, I think it is much more convenient when a new file is automatically created. What do you think about introducing an environment variable to control this behavior? For example, if COT_CREATE_NEW_FILES=true is set, CotEditor could create new files even without the --new flag.

I think thats a complication that users of a simpler editor like cot would prefer not to need to deal with. Cot should follow the general trend of other editors - particularly in the command line interface so that it can be used as ones general purpose editor. As it is, due to --new, I have to keep sublime around for EDITOR uses...

@matteocarnelos It took me some time to decide, but I still conclude that, at least at this point, the requested specification change is not suitable for CotEditor.

As @stonechoe also pointed out, CotEditor aims to be a GUI application provides a native macOS experience, and the CUI exists just to support the operation of CotEditor.app.

Additionally, and this is a system limitation, the macOS sandboxing restrictions are becoming stricter every year. Currently, there are already limited ways to pass file paths from the command line to GUI applications for editing, so I also don't want to make this the standard approach.

In any case, I appreciate your suggestion.
If circumstances change in the future, the behavior of the cot command may also change.

@1024jp I see. Thanks anyway for the consideration.

I will still keep the fork up in case anyone wants to try the proposed behavior by manually patching the cot command as mentioned in the description:

mv /Applications/CotEditor.app/Contents/SharedSupport/bin/cot /Applications/CotEditor.app/Contents/SharedSupport/bin/cot.bak
curl https://raw.githubusercontent.com/matteocarnelos/CotEditor/refs/heads/update-cot-cli/CotEditor/Resources/cot -o /Applications/CotEditor.app/Contents/SharedSupport/bin/cot
chmod +x /Applications/CotEditor.app/Contents/SharedSupport/bin/cot