Hi y’all.
Are there any plans to bundle a more recent Ruby version in the app?
Ruby 2.5.1 is the latest. Ruby 1.8.7 ships with the app.
The Ruby Core team has long ago stopped supporting 1.8.x. They currently only support (security fixes, etc) Ruby 2.3 - 2.5 (and 2.6 preview).
Thanks Shane
On Jul 5, 2018, at 7:52 PM, Shane Becker veganstraightedge@gmail.com wrote:
Hi y’all.
Are there any plans to bundle a more recent Ruby version in the app?
Ruby 2.5.1 is the latest. Ruby 1.8.7 ships with the app.
The Ruby Core team has long ago stopped supporting 1.8.x. They currently only support (security fixes, etc) Ruby 2.3 - 2.5 (and 2.6 preview).
We include 1.8.7 only due to the fact that many bundle commands and libraries that are still in active use were written with and aren’t compatible with 2.x. For newer bundle items and as we update older ones we are converting to using 2.x. For these cases we use the version supplied with the OS (currently 2.3.3). None of this is really meant for ruby development, for that case you can set the TM_RUBY variable to whatever version you want to use and it will be used for running your own scripts, etc. (And for simple cases it will be default use the OS supplied version if TM_RUBY is not set.)
I think another way of looking at this (correct me if I’m wrong) is that the internal 1.8.7 is used only for internal scripts, so it makes no difference to you, the end user; it is, as it were, just a part of TextMate’s internal functionality.
m.
On Jul 6, 2018, at 5:06 PM, Michael Sheets mummer@whitefalls.org wrote:
On Jul 5, 2018, at 7:52 PM, Shane Becker veganstraightedge@gmail.com wrote:
Hi y’all.
Are there any plans to bundle a more recent Ruby version in the app?
Ruby 2.5.1 is the latest. Ruby 1.8.7 ships with the app.
The Ruby Core team has long ago stopped supporting 1.8.x. They currently only support (security fixes, etc) Ruby 2.3 - 2.5 (and 2.6 preview).
We include 1.8.7 only due to the fact that many bundle commands and libraries that are still in active use were written with and aren’t compatible with 2.x. For newer bundle items and as we update older ones we are converting to using 2.x. For these cases we use the version supplied with the OS (currently 2.3.3). None of this is really meant for ruby development, for that case you can set the TM_RUBY variable to whatever version you want to use and it will be used for running your own scripts, etc. (And for simple cases it will be default use the OS supplied version if TM_RUBY is not set.)
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
-- matt neuburg, phd = http://www.apeth.net/matt/ pantes anthropoi tou eidenai oregontai phusei Programming iOS 11! http://shop.oreilly.com/product/0636920107408.do iOS 11 Fundamentals! http://shop.oreilly.com/product/0636920107415.do RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
I think another way of looking at this (correct me if I’m wrong) is that the internal 1.8.7 is used only for internal scripts, so it makes no difference to you, the end user; it is, as it were, just a part of TextMate’s internal functionality.
Thanks for clarifying.
Would it be of any benefit to the project if someone took on the task of converting internal scripts to being compatible with 2.x?
Sb
On 6 Jul 2018, at 9:11, Shane Becker wrote:
Would it be of any benefit to the project if someone took on the task of converting internal scripts to being compatible with 2.x?
The main benefit would be updating the internal shared libraries (found in bundle-support) to be compatible with 2.x as then new commands would be able to use these libraries without needing to be written in ruby 1.x and we could then also convert old commands to use 2.x one-by-one.
From the user’s point of view, the only nuisance with having internal scripts written in ruby 1.x is that the first time they call upon such functionality, TextMate will need to download the ruby 1.x interpreter.
The main benefit would be updating the internal shared libraries (found in bundle-support) to be compatible with 2.x as then new commands would be able to use these libraries without needing to be written in ruby 1.x and we could then also convert old commands to use 2.x one-by-one.
I’m new here. Would you mind linking me to one of those in the gh repo for me to take a look at?
Thanks Sb
On 16 Jul 2018, at 10:05, Shane Becker wrote:
The main benefit would be updating the internal shared libraries (found in bundle-support) to be compatible with 2.x as then new commands would be able to use these libraries without needing to be written in ruby 1.x and we could then also convert old commands to use 2.x one-by-one.
I’m new here. Would you mind linking me to one of those in the gh repo for me to take a look at?
Most of the shared code used by bundles can be found here: https://github.com/textmate/bundle-support.tmbundle/tree/master/Support/shar...
It’s a bit of a mess :)