You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How do you feel about jet having a config file where certain default options/preferences can be specified?
What's the benefit?
For example input and out formats by default are EDN. But what if you happen to work with JSON more as the default input format, could there be a way to specify that the default format should be JSON?
One way I figured that this could be implemented is by having a config file where you could specify the default input format.
It could be something like ~/.jet.edn the config could look like:
Could be useful eventually, but I would like to wait for some more feedback/upvotes on this one. If people would like to change the defaults they could also make a bash alias:
How do you feel about
jet
having a config file where certain default options/preferences can be specified?For example input and out formats by default are EDN. But what if you happen to work with JSON more as the default input format, could there be a way to specify that the default format should be JSON?
One way I figured that this could be implemented is by having a config file where you could specify the default input format.
It could be something like
~/.jet.edn
the config could look like:So that instead of typing:
it could be typed as:
Where the
:from
&:to
options would be read from~/.jet.edn
.The text was updated successfully, but these errors were encountered: