You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Besides that it would be useful to associate the file extensions from ecode, why don't you set ecode as default editor for those extensions? I do that once and forget about it.
Is ecode a single-instance application? Or will it launch a new instance for each file sent to it via Windows Explorer?
I don't want to associate file extensions with ecode. For example, I want to view this html file on ecode but don't want it to be the default application to open html files. I can still add ecode to the Open With list, but now another problem arises. Imagine you selected 10 html files and used right click, Open With -> ecode, and 10 instances of ecode are launching. Things will quickly become a mess. If ecode is a single-instance application, it will be much easier. I will open an instance of ecode before opening these 10 html files. They will be opened in this existing instance of ecode.
I have never tested to know if it's single-instance or not.
There is no integration with the file manager on both Windows and Linux/BSD. I need to view various files scattered throughout the file system. The open as folder model of ecode doesn't suit this. Currently, I have to drag these files into ecode from the file manager to open them. I'm really tired with this.
p/s: I want to ensure that just one instance of ecode is running.
Discussed in #134
Right click context menu for files and folders.
The text was updated successfully, but these errors were encountered: