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

enhancement: `k=@file` #22

Closed
bibby opened this Issue Mar 10, 2016 · 6 comments

Comments

Projects
None yet
3 participants
@bibby

bibby commented Mar 10, 2016

Great project, @jpmens .
An easily dismissable feature idea for you;

As with curl and vault, it could be nice to serialize the contents of a file using the @ prefix.

Example:

$ jo -p authors=@AUTHORS
{
   "authors": "Jan-Piet Mens <jpmens@gmail.com>"
}

Currently I'm using cat, which is fine, honestly.

$ jo -p authors="$(cat AUTHORS)"
@jpmens

This comment has been minimized.

Show comment
Hide comment
@jpmens

jpmens Mar 11, 2016

Owner

I'd thought of doing that (in spite of feature creep :-)
What I don't like about it is that it clashes with my (probably bad) choice of using @ for indicating booleans: this makes my eyes water:

$ jo pass@T authors=@AUTHORS

Let's think about this a bit.

Owner

jpmens commented Mar 11, 2016

I'd thought of doing that (in spite of feature creep :-)
What I don't like about it is that it clashes with my (probably bad) choice of using @ for indicating booleans: this makes my eyes water:

$ jo pass@T authors=@AUTHORS

Let's think about this a bit.

@itchyny

This comment has been minimized.

Show comment
Hide comment
@itchyny

itchyny Mar 11, 2016

Contributor

We can already specify boolean with =true so dropping support for @T is easy to fix. The change breaks the backwards compatibility though.

Contributor

itchyny commented Mar 11, 2016

We can already specify boolean with =true so dropping support for @T is easy to fix. The change breaks the backwards compatibility though.

@jpmens

This comment has been minimized.

Show comment
Hide comment
@jpmens

jpmens Mar 11, 2016

Owner

The proposed change doesn't break backward compatibility. Consider the difference:

$ jo bool@T
$ jo file=@AUTHORS
Owner

jpmens commented Mar 11, 2016

The proposed change doesn't break backward compatibility. Consider the difference:

$ jo bool@T
$ jo file=@AUTHORS
@itchyny

This comment has been minimized.

Show comment
Hide comment
@itchyny

itchyny Mar 11, 2016

Contributor

Oh, yes. You are right. Sorry.

Contributor

itchyny commented Mar 11, 2016

Oh, yes. You are right. Sorry.

@jpmens

This comment has been minimized.

Show comment
Hide comment
@jpmens

jpmens Mar 11, 2016

Owner

@bibby I like this, and it's going to happen with a twist. Stay tuned. 😃

Owner

jpmens commented Mar 11, 2016

@bibby I like this, and it's going to happen with a twist. Stay tuned. 😃

@jpmens jpmens added the enhancement label Mar 11, 2016

@jpmens jpmens closed this in 5b84494 Mar 11, 2016

@bibby

This comment has been minimized.

Show comment
Hide comment
@bibby

bibby Mar 11, 2016

I look forward to it. jo has saved me quite a bit of time this week.

bibby commented Mar 11, 2016

I look forward to it. jo has saved me quite a bit of time this week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment