On May 3 2007 18:40, Trent Piepho wrote: > >How about these examples: > >menuconfig FOO >if FOO >config A > depends on FOO >endif >config B >if FOO >config C > depends on FOO >endif
This does not work as expected in ncurses-menuconfig either. It does not even need a "menuconfig" object for that, something as simple as config A config B config C depends on A prints it A B C rather than A \_ C B which is why some of my menuconfig patches _move_ C to not come after B. >How does it show the first one, keeping the config entries in the correct >order and put them into the menu at the same time? > >And which of what should the second be show? > >foo >\-bar > \-baz > >or > >foo >|-bar >\-baz > >There is no question with menus, as the menu tree is clearly lexically >defined by the matching menu / endmenu pairs. But menuconfig doesn't work >that way, and it seems like it would make more sense if it did. > Jan -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
