Closed rahji closed 8 years ago
Hi Rob
I'm not really (or even slightly) a vim guy, so I can't offer much wisdom on that one. But if you do figure it out then feel free to submit a pull request.
On Tue, Dec 11, 2012 at 3:07 PM, rahji notifications@github.com wrote:
Trying the \o mapping with extempore.vim gives me this error:
File "", line 1 open()^M ^ SyntaxError: unexpected EOF while parsing
All of the other commands give similar errors. After removing the "" from the end of each line that starts with "command!" all of the commands work properly.
— Reply to this email directly or view it on GitHubhttps://github.com/digego/extempore/issues/75.
Making the change that I mentioned definitely seems to have fixed it. I'm curious as to why no one else has had this problem, though, and I'm also not an expert on vim or python. I've emailed the author of this file to see if he thinks my workaround is the fix.
@rahji, would you submit a pull request please? Looking at the source I'm not quite clear on what your change is.
When I originally wrote the plugin, it was a relatively quick hack to get started with vim and extempore. A smarter solution for the future might involve utilizing some of the existing SLIME plugins for vim.
I submitted a pul request.
anyone know where this is at?
Looks like this was merged in 3925908
.
Trying the \o mapping with extempore.vim gives me this error:
File "", line 1
open()^M
^
SyntaxError: unexpected EOF while parsing
All of the other commands give similar errors. After removing the "" from the end of each line that starts with "command!" all of the commands work properly.