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
should merging of #183 necessary? #202
Comments
Agree. |
Is making
|
On a somewhat tangential note, the current "fix" doesn't seem to even address pep8 block requirements:
Emphasis mine. The current implementation yields: # some_block = {
# 'a': 1,
# 'b': 2} in which pep8/pycodestyle tool correctly identifies "unexpected indentation", rather than: # some_block = {
# 'a': 1,
# 'b': 2} |
I think you can meet Pep8 requirements with:
Put it inside .vim/after/ftplugin/python.vim to avoid changing the setting for other filetypes. |
Right, according to pep8, we need
#<space>
instead of#
. But this kind of behavior can be implemented bylet g:NERDSpaceDelims = 1
. Actually, isn't it necessary to add a space between the comment delimiter of any language to make it clean? The requirement of pep8 should not make python a special case. Or at least the committer should take into account ofg:NERDSpaceDelims
. Someone argues that #183 makes it simpler for python commenting from the start. But before the merging I just need to confignow I have to config
besides two hours wasted on locating the reason why
<Leader>cc
only cause comments in python two spaces instead of one.The text was updated successfully, but these errors were encountered: