eeafd6cfe0
With the recent inspect search highlight provisions in place, the lack of highlighting in task based searches has grown from being only irritating to a real defect. Thus, this commit introduces parallel functionality to those searches initiated within a visible task window. And just as separate inspect searches are possible for each selection, per window task searches are provided. However, it should be noted that there are differences between task based searches and inspect type searches: * There is no concept of out-of-view data when dealing . with task rows -- if the data can't bee seen, it has . not, in fact, been constructed from a proc_t struct. * While inspect data is output at the character level, . up to now all task display data was only potentially . output and it was always based on a complete string. * With task search highlighting, rows now containing a . match must be output in pieces and, therefore, can't . be optimized away like other rows which haven't been . been altered. This is because top cannot predict the . the contents of a search string or, how many matches . might occur in a given row. Short search strings and . many matches would raise buffer needs geometrically. (now that we know a '.' + 2 spaces is squeezed to one) (everything's perfectly justified, but it's just luck) Signed-off-by: Jim Warner <james.warner@comcast.net>
COMPATIBILITY
This code is intended for use with Linux 2.6.xx, 3.x and
hopefully all future kernels.
INSTALLATION
If you are using git version of the project you need extra step.
./autogen.sh
After that, and everyone using .tar.xz version of procps-ng, can
do normal build. Read './configure --help' to select options for
your needs.
./configure
make
make install
If you have DejaGNU installed you can run optional test suite.
make check
HOW TO CONTRIBUTE
See Documentation/BUGS file.
PACKAGING
If you are a downstream maintainer (packager) for a Linux
distribution, please avoid causing troubles. This section
applies to you.
Avoid maintaining distribution specific patches. Send your
patches to upstream, where they are at least reviewed, if not
included.
Please forward bug reports. If your bug database is public and
busy enough to bother with, please make this known. Follow
Debian's lead in making the bug database easy to comment on via
email without need for an account.
For normal packages, ensure that you do not add debugging flags
to the CFLAGS variable.
UPSTREAM & BUG REPORTS
procps-ng <procps@freelists.org>