>> I find it very confusing to use, since it returns too verbose text to skim
>> through. Probably the search function should be split into "only search
>> titles[*]" and "search description too".
>
>Re verbosity: do you know that menuconfig search (/) takes regular
>expressions?
Regexes are not mentioned in the "Help" menu.
>That could help someone limit the amount of output
>from it.
>Can you give an example of being too verbose?
/ UNIX
Symbol: UNIX [=y]
Prompt: Unix domain sockets
Defined at net/unix/Kconfig:5
Depends on: NET
Location:
-> Networking
-> Networking support (NET [=y])
-> Networking options
Symbol: UNIXWARE_DISKSLICES ...
...
What would be more useful:
UNIX
Unix domain sockets
Networking > Networking Support > Networking options
UNIXWARE_DISKSLICES
Unixware slices support
File systems > Advanced ...
I.e. strip the Defined and Depends lines and crunch the Location lines inasfar
as that the full width of the window is used (break at col 70).
DEEP_FS
Just a symbol
File systems > Advanced filesystems > Very advanced filesystems >\n
Extremely advanced filesystems > Deep filesystem
>I have just modified menuconfig search to make displaying the
>Selects: and Selected by: output be an option (actually it's a
>different search command (\) to not see those lines.
>Would that help any regarding verbosity?
At the moment, entering e.g. UNIX in both the / and \ menus return the very
same output. Bug?
The \ should include everything what the original / had, plus the symbol
description ("Say Y here if ....").
Jan Engelhardt
--
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]