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

Indentation with = does not honor indent_keywords #26

Open
kiselgra opened this Issue Nov 9, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@kiselgra
Copy link

kiselgra commented Nov 9, 2017

Hi,

when I enter code manually the auto-indent works fine. Following the example from the docs:

(multiple-value-bind
    a
    b
  c
  d
  e)

However, when I want to indent a block of code that has gone out-of-sync the results neither honor g:vlime_indent_keywords, nor g:vlime_default_indent_keywords. As an example, when I select the form given above and press = the result is

(multiple-value-bind
  a
  b
  c
  d
  e)

I tested it on a fresh .vim config with only Vundle in it. Am I missing something?

@kiselgra

This comment has been minimized.

Copy link
Author

kiselgra commented Nov 12, 2017

Weirdly, you have to set nolisp for (the correctly working) indentexpr to work.

If lisp (the vim option) is set, then it overrules indentexpr.

Since an indentexpr is set by vlime (and working!) it would be great to add nolisp to the default configuration, I guess.

@l04m33

This comment has been minimized.

Copy link
Owner

l04m33 commented Nov 15, 2017

Thanks for the investigation! The lisp option overrides indentexpr, in a weird way. I noticed this behavior some time ago, but the indentation code still needs some tweaking (see #24). It may be necessary to provide a custom = mapping to boost the performance, in this case set nolisp won't be needed, so I didn't touch the default set lisp behavior at all.

I can set nolisp as the default for now, but need to first make sure this doesn't break anything...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment