Home/RubyMine/RubyMine 2016.2.3 Bug-Fix Update

RubyMine 2016.2.3 Bug-Fix Update

Posted on September 5, 2016 by Tatiana Vasilyeva

Hello everyone,

Please welcome the next minor update: RubyMine 2016.2.3. To update, download the new version from our website or, if you’re running RubyMine 2016.2.2, install the patch by clicking Check for Updates.

This update brings more accurate Ruby and HAML code error highlighting together with various fixes for better integration with version control systems. Thanks to our colleagues from the WebStorm team it also improves JavaScript support. You can find a full list of all addressed issues in the release notes.

—
Your RubyMine Team

#2016.2

Comments below can no longer be edited.

5 Responses to RubyMine 2016.2.3 Bug-Fix Update

Ilias says:
September 5, 2016
The bug with trailing spaces is still there. It has been reported in the RubyMine forums guys, but you don’t seem to care much. This is very counterproductive and it messes up teams collaboration.
- Tatiana Vasilyeva says:
  September 5, 2016
  Could you please point me to the corresponding topic on the forum? Or to the issue in our bug tracker? Is this issue the right one?
  - Ilias says:
    September 5, 2016
    Hi Tatiana,
    
    Sure https://intellij-support.jetbrains.com/hc/en-us/community/posts/207665709-The-RubyMine-version-2016-2-1-not-work-Strip-trailing-spaces-on-Save
    
    The issue you are linking (and the duplicated mentioned under the subject) seem related, although not exactly accurate. All spaces are ignored if the line does not contain any character (so only spaces).
    
    Apparently, the issue appeared on version 2016.2.1 and continued through 2016.2.3.
    - Anna Kutarba says:
      September 7, 2016
      Ilias, please check ‘Virtual Space->Allow placement of caret after end of line’ option in the ‘Settings | Editor| General’, set value ‘All’ in the ‘Strip trailing spaces on Save’ and check again. If it still doesn’t work please let us know.
  - Ilias says:
    September 6, 2016
    Is this going to be included in the next bug-fix release?