Skip to content
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

Clarify why *input* is for one-liners only #14

Open
borkdude opened this issue Dec 3, 2020 · 0 comments
Open

Clarify why *input* is for one-liners only #14

borkdude opened this issue Dec 3, 2020 · 0 comments

Comments

@borkdude
Copy link
Contributor

borkdude commented Dec 3, 2020

9:21 AM
jumar In https://book.babashka.org/#_scripts there's this:
When writing scripts instead of one-liners on the command line, it is not recommended to use input
May ask about more details why this isn't recommended?
E.g. Nate uses user/input in his scripts: https://github.com/justone/bb-scripts/blob/master/src/comb.clj#L31
src/comb.clj:31
(->> (map (partial process options) user/input)
https://github.com/justone/bb-scripts|justone/bb-scriptsjustone/bb-scripts | Added by GitHub
9:23 AM
borkdude @jumar I prefer not to since it's not obvious from the script what the corresponding i/o flags on the command line should be
New
9:24 AM
jumar Ah, so the shape of input will vary depending on -i vs -I but in stays the same, right?
It would be great to add a little note to the babashka book's section referenced above
9:25 AM
borkdude ok, will do

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant