Vadim Bendebury (вб) napsal(a): > Hi Michal, thank you for your comments. Please see my further questions below: > > 2009/12/11 Michal Marek <mmarek@xxxxxxx>: >> Vadim Bendebury napsal(a): >>> Help text for certain config options is very extensive (the text includes all >>> config options which the option in question depends on). Long lines are not >>> wrapped, making it impossible to see the list. >>> >>> This patch adds a function to wrap long lines to fit the screen width and >>> makes sure the function is invoked after help text is prepared. >> Hi Vadim, >> >> I think that wrapping long lines in menuconfig is a good idea, but I >> have a few problems with your patch. >> > > this was just an attempt to get the discussion going :-) > >>> diff --git a/scripts/kconfig/expr.c b/scripts/kconfig/expr.c >>> index edd3f39..2aa49e8 100644 >>> --- a/scripts/kconfig/expr.c >>> +++ b/scripts/kconfig/expr.c >>> @@ -1083,6 +1083,8 @@ void expr_print(struct expr *e, void (*fn)(void *, struct symbol *, const char * >>> } >>> if (expr_compare_type(prevtoken, e->type) > 0) >>> fn(data, NULL, ")"); >>> + >>> + str_screen_wrap(data, "||"); >>> } >> expr_print() is not the right place to do it. data is a opaque pointer, >> you can't assume that it's a pointer to struct gstr. qconf passes some >> class pointer here, there is code to dump symbol info to a filehandle. >> This should be done in the actual interface program, not in this generic >> code. >> > > well, I picked this spot because this is where just the last line of > the text might require wrapping, this makes the wrapping function > simpler. > > What do you think of mconf:show_help() before invoking > show_help_text() - is it the right spot to plug this in? Do you have a > suggestion? If you look at the expr_print() prototype, it takes a pointer to a callback and a data argument. This callback gets repeatedly called to store or display parts of the text. So you could create a new callback that pastes the parts together and inserts a newline if needed. That way, you don't have to memcpy() the text around afterwards. > And this brings the main question: how do we tell the window width in > different modes? Do we care to do this wrap in other than text > terminal modes? Qt and Gtk use widgets that take care of proper wrapping. oldconfig just prints the text on the terminal which does the wrapping (not at word boundaries, but that's IMO not an issue). So it's really just menuconfig (and nconfig, but porting your change to nconfig should be trivial). Michal -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
