mirror of
https://github.com/musix-org/musix-oss
synced 2024-12-23 16:13:18 +00:00
40 lines
1.7 KiB
Markdown
40 lines
1.7 KiB
Markdown
# ansi-regex [](https://travis-ci.org/chalk/ansi-regex)
|
|
|
|
> Regular expression for matching [ANSI escape codes](http://en.wikipedia.org/wiki/ANSI_escape_code)
|
|
|
|
|
|
## Install
|
|
|
|
```
|
|
$ npm install --save ansi-regex
|
|
```
|
|
|
|
|
|
## Usage
|
|
|
|
```js
|
|
const ansiRegex = require('ansi-regex');
|
|
|
|
ansiRegex().test('\u001b[4mcake\u001b[0m');
|
|
//=> true
|
|
|
|
ansiRegex().test('cake');
|
|
//=> false
|
|
|
|
'\u001b[4mcake\u001b[0m'.match(ansiRegex());
|
|
//=> ['\u001b[4m', '\u001b[0m']
|
|
```
|
|
|
|
## FAQ
|
|
|
|
### Why do you test for codes not in the ECMA 48 standard?
|
|
|
|
Some of the codes we run as a test are codes that we acquired finding various lists of non-standard or manufacturer specific codes. If I recall correctly, we test for both standard and non-standard codes, as most of them follow the same or similar format and can be safely matched in strings without the risk of removing actual string content. There are a few non-standard control codes that do not follow the traditional format (i.e. they end in numbers) thus forcing us to exclude them from the test because we cannot reliably match them.
|
|
|
|
On the historical side, those ECMA standards were established in the early 90's whereas the VT100, for example, was designed in the mid/late 70's. At that point in time, control codes were still pretty ungoverned and engineers used them for a multitude of things, namely to activate hardware ports that may have been proprietary. Somewhere else you see a similar 'anarchy' of codes is in the x86 architecture for processors; there are a ton of "interrupts" that can mean different things on certain brands of processors, most of which have been phased out.
|
|
|
|
|
|
## License
|
|
|
|
MIT © [Sindre Sorhus](http://sindresorhus.com)
|