I'm trying to open a remote file (over sftp) while launching Komodo Edit from command line. I'd expect this to work:
$ /Applications/Komodo\ Edit.app/Contents/MacOS/komodo sftp://server/file
Unfortunately, this fails - Komodo thinks this is a local file, doesn't find it, and proposes to create such a file.
Bug or feature?
It is a bug, which I see you've already logged a report on it here:
http://bugs.activestate.com/show_bug.cgi?id=82925
Thanks,
Todd
Thanks. Hopefully, the bug will be easy to fix :)
To ask somehow related question - are there any flags to launch separate instance of Komodo, instead of opening a new tab at already existing instance? What I'm exactly looking for, is to emulate behavior of unix editors, like vim or emacs - that are suitable for hooking into various places that expect editor process to stay active as long as user edits the file (ie. editor for mutt, or any place where VISUAL is called in order to edit a file (ie. commit description)).
Right now, if Komodo Edit is already running, and you say:
$ /Applications/Komodo\ Edit.app/Contents/MacOS/komodo /dir/file
in a terminal, new tab will be opened for the file, and newly launched komodo process will exit.
Ideally, this would behave like this:
* Komodo Edit is already running
* $ /Applications/Komodo\ Edit.app/Contents/MacOS/komodo /dir/file
* new tab opens for file in already running instance
* new komodo process stays up
* user edits the file
* upon closing the tab/file, new komodo process launched at second step exits
Should I open a separate bug for that?
Komodo does not have any external editor support as yet, though there is a bug on this here:
http://bugs.activestate.com/show_bug.cgi?id=79755
The biggest hurdle for this is that Komodo is forking/detaching from the starting process...
Cheers,
Todd