Issue #19718 has been updated by nobu (Nobuyoshi Nakada). I thought the issue about `-u` is simply a matter of priorities; just the chance of `-0x` cannot be denied, but `-0u` should have never been used. But now I remembered `-U` has been implemented since 1.9. My patch allows `-0U` as well as `-0u`, and would need to change. Probably a punctuation (like as `:`) may be possible. ---------------------------------------- Feature #19718: Extend `-0` option https://bugs.ruby-lang.org/issues/19718#change-103440 * Author: nobu (Nobuyoshi Nakada) * Status: Open * Priority: Normal ---------------------------------------- Recently I learned that Perl's `-0` option is extended to accept a hexadecimal Unicode codepoint. However it uses `-0x`, and since `-x` is used for shebang and cd, it would cause a backward incompatibility if we will incorporate it as it is. So I propose that `-0uCODEPOINT` instead. This can be extended to comma- or colon-separated codepoint list. Also, another idea is `-0:sepaerator` which specifies the separator as-is. Considering many of modern shells provide escaped string form (e.g., `$'\uHHHH'), this may be a more modern answer, except for NUL cannot be represented. https://github.com/ruby/ruby/pull/7914 -- https://bugs.ruby-lang.org/