-
Notifications
You must be signed in to change notification settings - Fork 69
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
indenting long lists fails because of maxoff #63
Comments
Personaly I removed it completely on my machine (the stopline arg from searchpairs to be precise). Maybe I am not used to dealing with really long files, but I am not experiencing any lags without maxoff at all. So I think maybe to make it optional, or make it turning on only in long files, like YouCompleteMe does... |
How about double the default value every time someone files a bug complaining about this? Undo the last doubling if somebody complains about indentation being noticeably slow. Should converge to a reasonable default value after a few iterations. (I'm reading this issue because I also have list literals in my unit tests that are longer than 50 lines. In this particular project they're shorter than 100 lines. I've now set |
Defaults have been adjusted by now. |
In case anyone else runs into this (since it's not yet mentioned here), the current workaround from #91 is configured at: vim-python-pep8-indent/indent/python.vim Lines 58 to 60 in 60ba5e1
Looks like maintainers want to keep it private and keep the freedom to change it in the future In the meantime, I've set my own to: let s:paren_pairs = {'()': 9999, '[]': 9999, '{}': 9999} |
Hi!
I found out that current version of find_opening_paren looks for only as long as 50 lines backwards for opening parenthesis. This is set explicitly by maxoff variable and prevents any list longer than 50 lines from being indented correctly. Is it a bug, or is it somehow a feature?
The text was updated successfully, but these errors were encountered: