David Pärsson

I'm still able to reproduce the problem in 1.0.3, and I don't see the fix with `shlex` for this in `editor.py` on master. The gist in https://github.com/fmoo/python-editor/issues/11#issuecomment-259981534 was never committed/merged....

@fmoo, is editors with (unescaped) spaces a thing that need to be supported? I don't think it should be, at least not on *nix. Even Bash's CTRL+x, CTRL+e does not...

Okay, let's make sure we don't misunderstand each other, because I see that #11 may be misinterpreted. When I opened #11 I did not mean to add support for binaries...

Apart from bash and git (above), a few Googles found this: - The [GNU Emacs Manual](http://ftp.gnu.org/old-gnu/Manuals/emacs-21.2/html_node/emacs_457.html) mentions `EDITOR="emacsclient --alternate-editor vi +%d %s"` - [Sublime Text for OS X](https://www.sublimetext.com/docs/3/osx_command_line.html) recommends `export...

I'm not sure what all current default arguments for all editors do, but I'm a big fan of sane defaults, so I think the augment approach seems like a reasonable...

@josh-gree, my **workaround** for this was to create a scripts that opens the editor with arguments. My `/usr/bin/editor` could contain something like: ``` #!/bin/sh code -w -n $1 ``` and...

Hi, and thanks for reporting. Have you been using this extension for a while? Has it been this way for as long as you've been using it or was this...

Are you willing to give it a try yourself? I'd appreciate a PR.

@filipnestak, I'm unable to re-trigger the builds the normal way, so I will rebase this branch on the latest `master` to trigger new builds.

@filipnestak, your changes are not following the `black` format conventions. Please update.