You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm writing Julia using the Julia-vim plugin. When I also have Vim-Sexp loaded, any parenthesis or bracket (([{) inserted in a Julia (*.jl) file is autoindented by one space - a space is inserted before the parenthesis right after it's typed. Commenting Vim-Sexp out makes the issue go away.
I understand the description is light on details and the problem might as well be in the Julia-Vim plugin rather than Vim-Sexp. However, I think this issue might be helpful to anyone who runs into the same problem. Maybe someone will actually be able to figure it out!
The text was updated successfully, but these errors were encountered:
helps with the issue. Thus, the default value of let g:sexp_filetypes = 'clojure,scheme,lisp,timl' must be somehow confusing Julia with one of the scheme/lisp/timl filetypes. Not sure how this is happening though...
Unfortunately Julia's extension .jl conflicts with librep Lisp's, so Vim sets filetype "lisp" which makes vim-sexp correctly add several insert mode mappings.
Overriding the wrong filetype for .jl with an autocommand in .vimrc or ~/.vim/ftdetect etc. does not seem work. let g:sexp_filetypes = 'clojure,scheme,timl'
might be the best preliminary solution for now if you don't write Lisp code.
I'm writing Julia using the Julia-vim plugin. When I also have Vim-Sexp loaded, any parenthesis or bracket (
([{
) inserted in a Julia (*.jl
) file is autoindented by one space - a space is inserted before the parenthesis right after it's typed. Commenting Vim-Sexp out makes the issue go away.I understand the description is light on details and the problem might as well be in the Julia-Vim plugin rather than Vim-Sexp. However, I think this issue might be helpful to anyone who runs into the same problem. Maybe someone will actually be able to figure it out!
The text was updated successfully, but these errors were encountered: