Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error detected while processing /Users/me/.janus/elm-vim/ftplugin/elm.vim (using Janus) #136

Open
AdamT opened this issue Oct 9, 2017 · 5 comments

Comments

@AdamT
Copy link

AdamT commented Oct 9, 2017

Hi there 👋 ,

When I write an Elm file I get this error:

Error detected while processing /Users/me/.janus/elm-vim/ftplugin/elm.vim:
line   44:
E174: Command already exists: add ! to replace it
line   45:
E174: Command already exists: add ! to replace it
line   46:
E174: Command already exists: add ! to replace it
line   47:
E174: Command already exists: add ! to replace it
line   48:
E174: Command already exists: add ! to replace it
line   49:
E174: Command already exists: add ! to replace it
line   50:
E174: Command already exists: add ! to replace it 

Do I have to fix it locally or is it within elm-vim?

Thank you

Update:
So I modified it locally with

" Commands
command! -buffer -nargs=? -complete=file ElmMake call elm#Make(<f-args>)
command! -buffer ElmMakeMain call elm#Make("Main.elm")
command! -buffer -nargs=? -complete=file ElmTest call elm#Test(<f-args>)
command! -buffer ElmRepl call elm#Repl()
command! -buffer ElmErrorDetail call elm#ErrorDetail()
command! -buffer ElmShowDocs call elm#ShowDocs()
command! -buffer ElmBrowseDocs call elm#BrowseDocs()
command! -buffer ElmFormat call elm#Format()

But that just doesn't sound right 😄

Janus instructs us to place/clone all plugins in to ~/.janus/ but is installing it like this conflicting with your recommended mode of installation?

@EverybodyKurts
Copy link

I started getting this same error as well. I'll give a status update if I can fix it.

@EverybodyKurts
Copy link

I believe this issue is related to issue #123

@mdxprograms
Copy link
Contributor

@KurtRMueller @AdamT if it is related to #123 then my current fork has the fix if you want to use it.

@AdamT
Copy link
Author

AdamT commented Dec 3, 2017

@mdxprograms your commit looks like it'll work 😄 (mdxprograms@4a712f0) Any thoughts on PR-ing it back into here?

@mdxprograms
Copy link
Contributor

mdxprograms commented Dec 3, 2017

@AdamT I might have already sent one in, but here is a new PR for this fix: #144

This was referenced Dec 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants