From: shevegen@... Date: 2018-10-29T12:08:59+00:00 Subject: [ruby-core:89618] [Ruby trunk Feature#15261] Expose rl_variable_value as Readline.variable_value Issue #15261 has been updated by shevegen (Robert A. Heiler). I would recommend to you, if you would like to, to add your request to the next developer meeting at: https://bugs.ruby-lang.org/issues/15229 It is such a small change that it may be quickly approved before the upcoming x-mas release of ruby and the developer meeting is where it may be easier to discuss functionality if necessary; or direct approval too. (I assume that the closer we are to the x-mas release, the more likely it may be for new features for ruby to be postponed into next year; for small changes such as this one here, perhaps this can be easily done before the x-mas release, though.) I would also recommend to add or expand on the small use case describing what could be done in pry; just something short. May be useful for irb as well in the long run. (I myself use Readline a lot, so I am always happy that others make use of readline as well, from ruby. I often use Readline because it is very convenient for commandline applications written in ruby to access a history or use the up-arrow for history, so I understand use cases pertaining to it. Readline makes user input so much more convenient compared to traditional $stdin.gets) ---------------------------------------- Feature #15261: Expose rl_variable_value as Readline.variable_value https://bugs.ruby-lang.org/issues/15261#change-74656 * Author: graywolf (Gray Wolf) * Status: Open * Priority: Normal * Assignee: * Target version: ---------------------------------------- I would like to propose exponsing rl_variable_value as Readline.variable_value, it would be useful in pry. Pull request: https://github.com/ruby/ruby/pull/1995 -- https://bugs.ruby-lang.org/ Unsubscribe: