<commit_before>![Preview](https://raw.githubusercontent.com/mschuchard/linter-puppet-parsing/master/linter_puppet_parsing.png)

Image displays example of simultaneous use of `Linter-Puppet-Parsing` with `Linter-Puppet-Lint`.

### Linter-Puppet-Parsing
[![Build Status](https://travis-ci.org/mschuchard/linter-puppet-parsing.svg?branch=master)](https://travis-ci.org/mschuchard/linter-puppet-parsing)

`Linter-Puppet-Parsing` aims to provide functional and robust `puppet parser validate` linting functionality in Atom.

### Installation
The `Puppet` or `Puppet Enterprise` Agent is required to be installed (preferably from a package or a gem) before using this. The `Linter` and `Language-Puppet` Atom packages are also required.

### Usage
- Avoid specifying arguments (e.g. --debug`) that greatly affect the formatting of the parser output.  These will cause issues.
- The `Puppet` parser is slower than most linter executables and its errors may require a few seconds after saving to display.
- The `Puppet` parser only throws errors for the first line of errors it encounters in a manifest so this linter only displays one line of errors at a time. However, multiple lines of warnings will be displayed.
<commit_msg>Update README with instructions for windows<commit_after>![Preview](https://raw.githubusercontent.com/mschuchard/linter-puppet-parsing/master/linter_puppet_parsing.png)

Image displays example of simultaneous use of `Linter-Puppet-Parsing` with `Linter-Puppet-Lint`.

### Linter-Puppet-Parsing
[![Build Status](https://travis-ci.org/mschuchard/linter-puppet-parsing.svg?branch=master)](https://travis-ci.org/mschuchard/linter-puppet-parsing)

`Linter-Puppet-Parsing` aims to provide functional and robust `puppet parser validate` linting functionality in Atom.

### Installation
The `Puppet` or `Puppet Enterprise` Agent is required to be installed (preferably from a package or a gem) before using this. The `Linter` and `Language-Puppet` Atom packages are also required.

### Usage
- Avoid specifying arguments (e.g. --debug`) that greatly affect the formatting of the parser output.  These will cause issues.
- The `Puppet` parser is slower than most linter executables and its errors may require a few seconds after saving to display.
- The `Puppet` parser only throws errors for the first line of errors it encounters in a manifest so this linter only displays one line of errors at a time. However, multiple lines of warnings will be displayed.
- On Windows, you have to specify the whole path to the puppet executable, even if it is in PATH, e.g.: C:\Program Files\Puppet Labs\Puppet\bin\puppet

{'fraction_non_alphanumeric': 0.08882958444529165, 'fraction_numerical': 0.0, 'mean_word_length': 4.963636363636364, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 6, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5463270', 'n_tokens_mistral': 788, 'n_tokens_neox': 773, 'n_words': 300}