From 37afc7dc8ae30342d01f3f72e73646fa60bb5294 Mon Sep 17 00:00:00 2001 From: Kelly Brazil Date: Tue, 17 Dec 2019 09:35:27 -0800 Subject: [PATCH] updte todo and compatibility --- README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 3e47c7f1..e953161e 100755 --- a/README.md +++ b/README.md @@ -1603,8 +1603,6 @@ $ w | jc --w -p ``` ## TODO Future parsers: -- nslookup -- journalctl - /proc 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. ## 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