Search addon: Return the number of results of a search

[Tyriar]

This request may impact performance, this should be evaluated.

Plan issue: #705

[noamyogev84]

Hi @Tyriar
I'm trying to understand this enhancement. Currently the search addon only supports find next & find previous. what is your expectation regarding the number of results?

• how should it be outputted?

[Tyriar]

@noamyogev84 currently the search addon returns a boolean, I think we should return a number instead:

xterm.js/src/addons/search/SearchHelper.ts

Line 26 in 9e446a9

public findNext(term: string, searchOptions?: ISearchOptions): boolean {

It's probably also a good idea to return only 0 or 1 unless a new option to return number of results (countResults: boolean?) is set:

xterm.js/src/addons/search/Interfaces.ts

Lines 24 to 28 in 9e446a9

	export interface ISearchOptions {
	regex?: boolean;
	wholeWord?: boolean;
	caseSensitive?: boolean;
	}

[noamyogev84]

Hi @Tyriar,
Although I have some pretty straight forward implementation for this, I do have some wonderings:

1. Why do we need this second iteration? (line 48)
   

   xterm.js/src/addons/search/SearchHelper.ts

   Lines 39 to 55 in 9e446a9

   	// Search from ydisp + 1 to end
   	for (let y = startRow + 1; y < this._terminal._core.buffer.ybase + this._terminal.rows; y++) {
   	result = this._findInLine(term, y, searchOptions);
   	if (result) {
   	break;
   	}
   	}
   	// Search from the top to the current ydisp
   	if (!result) {
   	for (let y = 0; y < startRow; y++) {
   	result = this._findInLine(term, y, searchOptions);
   	if (result) {
   	break;
   	}
   	}
   	}

2. Currently for multiple matches in the same line it only returns (and counts) the first occurrence. do you think this should first be redesigned before we return the number of results? In reference to Search addon: Allow finding multiple instances on the same line #1654

[Tyriar]

@noamyogev84 sorry about the delay. 1: the second iteration is because findNext does not start from the top:

• First iteration: Search from the top of the viewport to the bottom of the buffer
• Second iteration: Search from the top of the buffer to the top of the viewport

2: I think the code to collect the total should look a little different to the current code, if it's true we want to continue searching until we've wrapped around to the start.