The <HELP> state is willing to consume config options as part of help
texts AFAICT:
(1) [ \t]+ {
(2) \n/[^ \t\n] {
(3) [ \t]*\n {
(4) [^ \t\n].* {
(5) <<EOF>> {
Now consider: "\tSome help text.\n\t\nconfig FOO\n\tdepends on BAR\n"
"\tSome help text." is consumed by (1).
"\n" is consumed by (3).
"\t\n" is consumed by (3) again.
"config FOO" is consumed by (4), which resets first_ts to last_ts,
which does not actually change the value of first_ts.
"\tdepends on BAR\n" is consumed by (1), and does not zconf_endhelp()
as the indentation level is the same as for "\tSome help text."
Better boundary detection logic is needed here.
Thanks,
Bill
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Dec 31 2002 - 22:00:14 EST