Web Links Provider shouldn't accept "<>" Characters in opening / ending Clauses

[pattch]

Details

• Browser and browser version: All
• OS version: All

Steps to reproduce

1. Enter $ echo "\<http://test.com\>"
2. Hover over the link printed on the next line, which should be <http://test.com>
3. Observe that the link that is validated corresponds to http://test.com> which doesn't make much sense

Simply adding the <> characters to NEGATED_PATH_CHARACTER_SET and NEGATED_DOMAIN_CHARACTER_SET somewhat resolves this issue, but also has the issue that the test case above won't validate the link inside of the <> brackets as well.

[silamon]

> is being matched as the path of the url here: ([^:"\'\\s]).

xterm.js/addons/xterm-addon-web-links/src/WebLinksAddon.ts

Lines 18 to 19 in 6c18b7f

	const pathCharacterSet = '(\\/[\\/\\w\\.\\-%~:+@]*)*([^:"\'\\s])';
	const pathClause = '(' + pathCharacterSet + ')?';

[Tyriar]

Seems fixed: