-
Notifications
You must be signed in to change notification settings - Fork 11
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
Pretty printer #14
Comments
Yep the pretty-printer could be an option, especially if we have 2+ choices, but I'd rather have a good default (otherwise the CLI might become tedious to use). |
So you want the pretty printer to be in the repository? |
No, not at all (it might be a separate package, or it might live in the repository at the start, whichever you prefer) -- I just want to have a default executable name to call it. (logipedia-pp or similar?)
… De: "Gabriel Hondet" ***@***.***>
À: "Deducteam/Logipedia" ***@***.***>
Cc: "Romain Primet" ***@***.***>, "Comment"
***@***.***>
Envoyé: Jeudi 17 Octobre 2019 13:35:58
Objet: Re: [Deducteam/Logipedia] Pretty printer (#14)
So you want the pretty printer to be in the repository?
—
You are receiving this because you commented.
Reply to this email directly, [
#14?email_source=notifications&email_token=ACO7RM2WUCM2VIBKHOJUBQTQPBEZ5A5CNFSM4JBUZNIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBPY3EY#issuecomment-543133075
| view it on GitHub ] , or [
https://github.com/notifications/unsubscribe-auth/ACO7RM2ZZSNDZ422HWZXC5DQPBEZ5ANCNFSM4JBUZNIA
| unsubscribe ] .
|
Come to think of it, being able to set the pretty-printer executable through an environment variable (e.g LOGIPEDIA_PP or similar) might also be a good choice (but then we need to define a priority order...) |
Ah all right, that's a good idea. I think we should
so that if both are set, the command line flag is taken into account. Why not |
Could the binary of the pretty printer be passed as an argument of logigen? For instance, one would use
logigen -i json/ -o web --pp /usr/bin/ppt
. By default, the json object could be printed (although it's not pretty).The text was updated successfully, but these errors were encountered: