- \n
- Multiprocess debugging<\/a><\/li>\n
- Live variables refresh<\/a><\/li>\n
- Native conditional breakpoints support<\/a><\/li>\n
- Exception breakpoints<\/a><\/li>\n<\/ul>\n<\/li>\n
- Navigation Bar<\/a><\/li>\n
- Ruby Parsing improvements<\/a><\/li>\n
- Future plans<\/a><\/li>\n<\/ul>\n
<\/i>Download RubyMine 2018.1 EAP<\/a><\/p>\n
Run Anything Action<\/strong><\/h2>\n
RubyMine has a great number of helpful tools for running rake tasks, various rails server configurations, and generators. All these actions require different shortcuts and different kinds of configuration.
\nA couple of months ago, a discussion in our slack channel<\/a> led to a feature request<\/a> for providing a unified way to run completely different stuff in RubyMine. We already have the universal and easy to use search everywhere<\/a>, and now we\u2019ve created a similar kind of action for running and debugging stuff (where possible). Meet Run Anything:<\/p>\n![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2018\/01\/ruby-run_anything_rake.gif\")
<\/p>\nThe action combines all our run configuration types and tries to match the input with known actions. For example, typing `rake` will render a list of available rake actions in the suggestion list. Typing `install` will suggest running bundle install and so on. If the command does not match any actions provided by RubyMine, you can still run it right from the popup:<\/p>\n
![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2018\/01\/ruby-run_anything_take2.gif\")
<\/p>\nIMPORTANT NOTE: <\/strong>due to a bug, on OS X systems RubyMine has to be run from the terminal in order to be able to run several \u201cunknown\u201d commands like rvm, brew, and others.<\/p>\n
As you know, RubyMine has a great built-in debugger, so you can seamlessly debug matched configurations right from the same popup. Hold the Shift button when selecting an existing configuration (or creating a new one) to debug the command:<\/p>\n
![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2018\/01\/ruby-debug_anything.gif\")
<\/p>\nAs of EAP1, it is not possible to debug commands unknown to RubyMine. However, we are already polishing this capability, so stay tuned for more juicy cases which are to be delivered next week!<\/p>\n
Inline Diagrams in Markdown<\/strong><\/h2>\n
It is now possible to render UML diagrams and DOT right in the markdown documents [RUBY-19041<\/a>].<\/p>\n
![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2018\/01\/ruby-markdown_diagram.gif\")
<\/p>\nPlease make sure you have Graphviz installed to use this feature. This page<\/a> describes the expected configuration on different OSs.<\/p>\n
Debugger Improvements<\/strong><\/h2>\n
Several important improvements and bugfixes come with this EAP build:<\/p>\n
Multiprocess debugging<\/strong><\/h3>\n
RubyMine now allows for proper debugging of multiprocess applications. By design, our debugger allows you to explore all the application processes, their threads, and variables during stepping. However, due to this bug<\/a>, RubyMine had only been gaining control over the process where a breakpoint was hit. Now that it is fixed, you have proper control over the whole application.<\/p>\n
Live variables refresh<\/strong><\/h3>\n
Now RubyMine updates the variables lists after using an action which changes them, e.g. evaluating expressions or running stuff in the debugger console.<\/p>\n
Native conditional breakpoints support<\/strong><\/h3>\n
The conditional breakpoints are now implemented right on the interpreter side which means less communicating between the debugged process and IDE, and, hence, an increased running speed.<\/p>\n
Exception breakpoints<\/strong><\/h3>\n
For a long time, RubyMine has been capable of setting up exception breakpoints<\/a> which suspend execution when a certain kind of Exception is raised. However, this feature has not really been discoverable. Now in the exceptions list<\/a> dialog you can enable catching every exception raised:<\/p>\n
![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2018\/01\/ruby-any_exception_correct.gif\")
<\/p>\nTo add some specific type of Exceptions to be considered, add a new one with a plus button:<\/p>\n
![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2018\/01\/ruby-particular_exception.gif\")
<\/p>\nNavigation Bar<\/strong><\/h2>\n
Another important feature which has been made more visible is Navigation bar<\/a>. Now it is enabled by default:<\/p>\n
![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2018\/01\/ruby-navbar.gif\")
<\/p>\nRuby Parsing Improvements<\/strong><\/h2>\n
We have unified parsing routines for arguments in method definitions and block calls. This has improved Code Insight features provided for block variables: for example, now a block passed as a parameter is properly resolved from the receiver block’s body, and the parameter inspections like “unused parameter” apply to them as well:<\/p>\n
![\"\"](\"https:\/\/blog.jetbrains.com\/wp-content\/uploads\/2018\/01\/ruby-blocks.gif\")
<\/p>\nFuture Plans<\/strong><\/h2>\n
- Live variables refresh<\/a><\/li>\n