nmap: add page #66
Merged
nmap: add page #66
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for that! And you're right it started off with a pretty strict "parser", but I'm not sure it's worth it in the end. I'm thinking of maybe relaxing it to just print any Markdown as nicely as possible. It did ensure a little consistency in the pages, but maybe that can just stabilise over time with PRs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Just a small example of how to use nmap.
I actually wanted to provide a few examples of nmap's target specification and octet ranges, but the formatter does not seem to support such descriptions (e.g. nested lists). In the end, I settled for a simple example that should suffice for most use cases.