1
0
mirror of https://github.com/kellyjonbrazil/jc.git synced 2025-07-15 01:24:29 +02:00

updte todo and compatibility

This commit is contained in:
Kelly Brazil
2019-12-17 09:35:27 -08:00
parent efbf354960
commit 37afc7dc8a

View File

@ -1603,8 +1603,6 @@ $ w | jc --w -p
``` ```
## TODO ## TODO
Future parsers: Future parsers:
- nslookup
- journalctl
- /proc files - /proc files
- /sys files - /sys files
@ -1612,7 +1610,10 @@ Future parsers:
Feel free to add/improve code or parsers! You can use the `jc/parsers/foo.py` parser as a template and submit your parser with a pull request. Feel free to add/improve code or parsers! You can use the `jc/parsers/foo.py` parser as a template and submit your parser with a pull request.
## Compatibility ## Compatibility
Some parsers like `ls`, `ps`, `dig`, etc. will work on any platform. Other parsers that are platform-specific will generate a warning message if they are used on an unsupported platform. You may still use a parser on an unsupported platform - for example, you may want to parse a file with linux `lsof` output on an OSX laptop. In that case you can suppress the warning message with the `-q` cli option or the `quiet=True` function parameter in `parse()`: Some parsers like `ls`, `ps`, `dig`, etc. will work on any platform. Other parsers that are platform-specific will generate a warning message if they are used on an unsupported platform. To see all parser information, including compatibility, run `jc -a -p`.
You may still use a parser on an unsupported platform - for example, you may want to parse a file with linux `lsof` output on an OSX laptop. In that case you can suppress the warning message with the `-q` cli option or the `quiet=True` function parameter in `parse()`:
``` ```
$ cat lsof.out | jc --lsof -q $ cat lsof.out | jc --lsof -q