Project

General

Profile

Actions

Bug #3391

closed

Use single exclamation mark instead of double exclamation mark for IRB

Added by diegoviola (Diego Viola) almost 14 years ago. Updated almost 13 years ago.

Status:
Closed
Target version:
ruby -v:
Ruby 1.9.2-trunk
Backport:
[ruby-core:30589]

Description

=begin
Hello,

I'm adding this patch which changes the "!!" double exclamation marks in lib/irb.rb to use single exclamation marks "!", I think using single exclamation marks are more formal for outputs and Ruby itself.

The patch in question was patched from: http://github.com/ruby/ruby -- Please let me know if you want me to patch from SVN trunk instead.

Thanks and Best Regards,

Diego
=end


Files

exclamation_mark_irb_fix.diff (983 Bytes) exclamation_mark_irb_fix.diff diegoviola (Diego Viola), 06/05/2010 08:33 AM
Actions #1

Updated by nobu (Nobuyoshi Nakada) almost 14 years ago

  • Category set to lib
  • Status changed from Open to Assigned
  • Assignee set to keiju (Keiju Ishitsuka)
  • Priority changed from Normal to 3
  • Target version set to 2.0.0

=begin

=end

Actions #2

Updated by diegoviola (Diego Viola) almost 14 years ago

=begin
When can I expect to see this merged?

Thanks,

Diego
=end

Actions #3

Updated by matz (Yukihiro Matsumoto) almost 14 years ago

=begin
Hi,

In message "Re: [ruby-core:30589] [Bug #3391] Use single exclamation mark instead of double exclamation mark for IRB"
on Sat, 5 Jun 2010 08:33:07 +0900, Diego Viola writes:

|I'm adding this patch which changes the "!!" double exclamation marks in lib/irb.rb to use single exclamation marks "!", I think using single exclamation marks are more formal for outputs and Ruby itself.
|
|The patch in question was patched from: http://github.com/ruby/ruby -- Please let me know if you want me to patch from SVN trunk instead.

Although your claim is reasonable, we don't want to introduce any
incompatibility right now. So we will merge the patch on trunk, for
sometime in the future.

						matz.

=end

Actions #4

Updated by matz (Yukihiro Matsumoto) almost 14 years ago

  • Status changed from Assigned to Closed
  • % Done changed from 0 to 100

=begin
This issue was solved with changeset r28363.
Diego, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.

=end

Actions #5

Updated by diegoviola (Diego Viola) almost 14 years ago

=begin
Thanks Matz, Ruby FTW.
=end

Actions #6

Updated by diegoviola (Diego Viola) almost 14 years ago

=begin
Why isn't this change included in Ruby 1.9.2 RC1?
=end

Actions #7

Updated by runpaint (Run Paint Run Run) almost 14 years ago

=begin

Why isn't this change included in Ruby 1.9.2 RC1?

It was committed after the code freeze. See http://redmine.ruby-lang.org/wiki/ruby-19/ReleasePlan . :-)
=end

Actions #8

Updated by diegoviola (Diego Viola) almost 14 years ago

=begin
I see. Is there any chance it will be merged in future versions?

Thanks,

Diego
=end

Actions #9

Updated by runpaint (Run Paint Run Run) almost 14 years ago

=begin
Certain. :-) It's been merged into trunk now, so the next release branched from trunk will have your patch applied. In addition, people who run bleeding-edge Ruby, i.e. build from trunk themselves, already have your patch. :-)
=end

Actions #10

Updated by diegoviola (Diego Viola) almost 14 years ago

=begin
Thanks
=end

Actions

Also available in: Atom PDF

Like0
Like0Like0Like0Like0Like0Like0Like0Like0Like0Like0