Open avar opened 14 years ago
The value of $EDITOR is really down to the edit server. Although the principle focus is the elisp one which runs in emacs other edit servers are usable.
The python client however needs a few tweaks. One to honour ${EDITOR} and another to handle multiple requests.
I suppose passing ${EDITOR} from the extension is possible. I guess fetching a list of editors or confirming the server cared would also be useful?
Yeah I think that the server could be "smarter" and allow negotiation like that. But it might be confusing having the settings in multiple places. Ideally we could make some type of standard for Chrome edit servers.
Has there been any progress on this? The lack of It's All Text (or anything equivalent for using Vim) for Chrome has me close to switching back to Firefox.
I have not read the docs for the non-.el edit-servers so it's possible one of them might work but the descriptions don't sound promising.
There's really nothing emacs specific about this extension aside from the edit-server.el. To support other editors it would be nice to present the user with a configuration option to change the path to the editor. This would then be passed to the edit server who'd call that instead of the hardcoded "emacsclient" program.