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
{{ message }}
Repository navigation
Incorrect indentation for block params with parenthesis #344
I can't seem to reproduce the issue on the current master branch. Could you check if you've got the latest version from github? If you do, it might be something setting-related, or related to the Vim version. Could you post the output from vim --version, and any vim-ruby settings that you've set?
Hmm, well, I tried installing this distribution. It was harder than it should be, since the authors seem to be building it exclusively for MacOS (relying on the presence of brew), but I digress. I still can't seem to reproduce the issue with this distribution.
Could you double-check that vim-ruby is at the latest version? I know you've run a PluginUpdate, but could you cd into ~/.vim/bundle/vim-ruby and run git show HEAD? For me, the latest commit is 074200ffa39b19baf9d9750d399d53d97f21ee07.
Can't reproduce either. This is definitely a bug I've encountered in the past, so I'm inclined to think this is a case of the stock files included with Vim loading rather than the latest.
Here's my --startuptime... dirty laundry notwithstanding, I think it confirms it's loading in the right order. (~/.vim/ftplugin/ruby.vim is just setlocal ts=2 sts=2 sw=2 et)
Likewise:
indentexpr=GetRubyIndent(v:lnum)
Last set from ~/.common/.vim/bundle/vim-ruby/indent/ruby.vim
indentkeys=0{,0},0),0],!^F,o,O,e,:,.,=end,=else,=elsif,=when,=ensure,=rescue,==begin,==end,=private,=protected,=public
Last set from ~/.common/.vim/bundle/vim-ruby/indent/ruby.vim
Activity
AndrewRadev commentedon May 2, 2017
I can't seem to reproduce the issue on the current master branch. Could you check if you've got the latest version from github? If you do, it might be something setting-related, or related to the Vim version. Could you post the output from
vim --version, and any vim-ruby settings that you've set?klieth commentedon Aug 31, 2017
I am also seeing this issue, on OS X 10.12.6 using both vim and neovim:
I just ran a
:PluginUpdate, so I should have the latest from Github.AndrewRadev commentedon Sep 1, 2017
@klieth Could you also post your .vimrc? The particular settings you have might give me a clue.
klieth commentedon Sep 1, 2017
@AndrewRadev I'm using a mostly vanilla install of maximum-awesome: https://github.com/square/maximum-awesome/blob/master/vimrc and https://github.com/square/maximum-awesome/blob/master/vimrc.local
The only addition I've made is to add
set nohlsearch.AndrewRadev commentedon Sep 2, 2017
Hmm, well, I tried installing this distribution. It was harder than it should be, since the authors seem to be building it exclusively for MacOS (relying on the presence of
brew), but I digress. I still can't seem to reproduce the issue with this distribution.Could you double-check that
vim-rubyis at the latest version? I know you've run aPluginUpdate, but could youcdinto~/.vim/bundle/vim-rubyand rungit show HEAD? For me, the latest commit is074200ffa39b19baf9d9750d399d53d97f21ee07.matthewd commentedon Jul 3, 2018
FWIW, I just came here to report this same issue:
My HEAD is 1e4c6fd.
tpope commentedon Jul 6, 2018
Can't reproduce either. This is definitely a bug I've encountered in the past, so I'm inclined to think this is a case of the stock files included with Vim loading rather than the latest.
matthewd commentedon Jul 6, 2018
Hrmm 😕
Here's my
--startuptime... dirty laundry notwithstanding, I think it confirms it's loading in the right order. (~/.vim/ftplugin/ruby.vimis justsetlocal ts=2 sts=2 sw=2 et)Likewise:
(
~/.vimis a symlink to~/.common/.vim)tpope commentedon Jul 6, 2018
I concede your install looks correct.
matthewd commentedon Jul 7, 2018
Thanks for confirming; from that, I dug in in hopes of finding some sort of cross-plugin interaction.
... but I didn't find one. I think (based on
--startuptimeand-V) this eliminates all local context:But that still leaves me looking at:
(to be extra sure I also killed
$VIMRUNTIME/*/ruby.vim, though they should all no-op because vim-ruby's versions were loaded first)I also tried pointing at a fresh clone (now at 6959e10), just to eliminate any weirdness in my existing checkout; no luck there either.