[#9722] Kernel#system broken inside Dir.chdir(&block) if system command doesn't have shell characters — <noreply@...>

Bugs item #7278, was opened at 2006-12-14 13:59

8 messages 2006/12/14

[#9749] System V IPC in standard library? — Steven Jenkins <steven.jenkins@...>

Back in August, I needed a semaphore to serialize access to an external

14 messages 2006/12/19

[#9753] CVS freeze — SASADA Koichi <ko1@...>

Hi,

20 messages 2006/12/20
[#9755] Re: [ruby-dev:30039] CVS freeze — SASADA Koichi <ko1@...> 2006/12/20

Hi,

[#9757] Re: [ruby-dev:30040] Re: CVS freeze — SASADA Koichi <ko1@...> 2006/12/20

Hi,

Re: using OptionParser.on_tail leads to missed AmbiguousOption

From: "Nobuyoshi Nakada" <nobu@...>
Date: 2006-12-11 03:35:28 UTC
List: ruby-core #9698
Hi,

At Mon, 11 Dec 2006 04:35:55 +0900,
Jim Meyering wrote in [ruby-core:09696]:
> From a quick look at ruby1.9's optparse.rb, it seems options registered
> via on_tail (and maybe on_head, too?) are not searched when determining
> whether to throw an AmbiguousOption.  This is ruby1.9 from Debian/unstable.
>
> For example, given this code, handling both --version and --verbose,
> I would expect the use of a "--v" argument to evoke an AmbiguousOption:
(snip)
> Yet I get this:
>
>    $ ruby1.9 optparse --v
>    verbose

Intended behavior.

`on' (or def_option) and `on_tail' (or def_tail_option) exist in order
to define options in different precedences.

-- 
Nobu Nakada

In This Thread

Prev Next