-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doco changes #24
base: master
Are you sure you want to change the base?
doco changes #24
Conversation
what do you think? |
These are all minor, |
yes, I see. it indeed might be confusing at first - it's the suffix of the search which defines the search behavior, e.g.: for all the numerical JSON searches:
Look, I will not merge this PR, but rather will work on a better wording for the lexemes explanation in the mini-guide (and will mentioned the |
I wrote some more doco changes. Unfortunately this current PR hasn't been closed, so I can't open a new PR. Here are the changes: soniah@661777b |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
elaborated a bit more on the requested changes
Updates made. |
- all _JSON iterables_ made of only _atomic values_ or empty iterables (`[]`, | ||
`{}`) are printed on a single line, the remainder are pretty-printed. The `t` | ||
suffix defaults to 3 spaces, this can be changed with an additional `N` suffix, | ||
for example `-tc5`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- it's way around:
The
-t
flag accepts an optionalc
suffix, ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything else looks good. I'll merge after fixing that typo.
No description provided.