|
From: | Dmitry Gutov |
Subject: | bug#32496: 27.0.50; Strange indentation when ruby-align-chained-calls is t |
Date: | Wed, 22 Aug 2018 15:50:05 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.0 |
On 8/22/18 2:36 PM, Artur Malabarba wrote:
1. (setq ruby-align-chained-calls t) 2. (setq ruby-use-smie t) 3. Open a file in ruby-mode, insert the following and indent it ---------- some_variable.where.not(x: nil) .where(y: 2) ---------- Expected behaviour: Nothing would happen, the code is already properly indented. What actually happens: The code gets indented as follows ---------- some_variable.where.not(x: nil) .where(y: 2) ---------- Note that this is conflicts with the indentation enforced by rubocop.
I'd like to point out that this is exactly the behavior Bozhidar asked for, back when this variable was introduced. See:
http://lists.gnu.org/archive/html/emacs-devel/2014-01/msg01802.html and in particular the Example 1 in the referenced comment: https://github.com/rubocop-hq/ruby-style-guide/pull/176#issuecomment-18664622So we even have a test (ruby-align-chained-calls) that check that the alignment is do to the last dot, and not to the first one.
[Prev in Thread] | Current Thread | [Next in Thread] |