Loading Profile...
Chained commands in Ubiquity
One of the first things I tried to do in Ubiquity was post to twitter with a tiny'd URL. Obviously this is currently not possible with the first word being the command, but something like the below would be truly awesome:
twitter Hello world here's my link (tinyurl http://foo.longurl.com)
Imagine other uses like:
email Hey come to my house here: (map 33 foo st, bar, CA) to Fred
Ubiquity ROCKS.
twitter Hello world here's my link (tinyurl http://foo.longurl.com)
Imagine other uses like:
email Hey come to my house here: (map 33 foo st, bar, CA) to Fred
Ubiquity ROCKS.
I’m excited
27
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company has this under consideration.
The best point from the company
-
I've begun a blog series on exploring command chaining—bringing up different considerations which must be made before making command chaining happen. I'd love to get comments on these posts. Here's the first:
http://mitcho.com/blog/projects/explo...
The company thinks
this is one of the best points
The best point from everyone
-
In keeping with the natural language flow of Ubiquity, chaining using "and" would be nice. Ex: tinyurl this and twitter ...
5 people think
this is one of the best points
-
Inappropriate?http://groups.google.com/group/ubiqui...
Here is some more info, Thats one of the first things I tried too :)
I’m excited
-
Inappropriate?You can actually chain commands together (in a very basic way) in Ubiquity 0.1. It's an undocumented feature, and doesn't work with all commands, but it works for simple use cases. Try this:
* translate hello to korean
* (execute it, then with no selection do:)
* email it to (person)
Note that the output from the first command has become the input to the second command.
I wrote more about this in
my blog post today.
I’m confident
-
Inappropriate?hmmm chaining worked for me.
I successfully did :
twitter Ubiquity for firefox ROCKS ! tinyurl http://labs.mozilla.com/2008/08/intro...
I’m happy
-
Inappropriate?Henti, Twitter automatically Tiny URL's links of a certain size. Hence your twit probably has "tinyurl" in it before the tinyurl link :).
I would greatly appreciate linux like CLI functionality. the ability to "map michigan | email here is a map of michigan to contact" would be phenomenal.
I’m hopeful
1 person thinks
this is one of the best points
1 Comment Add a comment
This is one of the best points
-
ahh indeed it did, and here I thought I was being clever :) -
Inappropriate?In keeping with the natural language flow of Ubiquity, chaining using "and" would be nice. Ex: tinyurl this and twitter ...
5 people think
this is one of the best points
1 Comment Add a comment
This is one of the best points
-
That would be great to.
tinyurl this and email it to contact would be incredibly natural. -
Inappropriate?I see this as an absolute must, and I'm hoping it is something Muppet Labs are already working on.
As another post mentioned, using "it" as a pronoun referencing the previous command output would be a good natural language way of expressing piped commands without resorting to shell tricks like |.
map joes pizza joint somecity tx and email it to jim
Also useful would be a way of feeding the same input to multiple commands ("yelp and map some address") ...
yelp and map joes pizza joint, somecity, tx and email it to jim
-- hugh
2 people think
this is one of the best points
-
Inappropriate?It's a bummer this hasn't received any attention in Ubiquity 0.5! I agree this would be a powerful ability, and is something very natural for early users to try (and be disappointed with when it doesn't work as expected)
I’m hopeful
-
Inappropriate?This is definitely a feature the Ubiquity team wants to implement, but it's actually quite technically difficult. We've put it on the roadmap for the future though, which you can read here if you're interested:
Ubiquity Roadmap -
Inappropriate?I've begun a blog series on exploring command chaining—bringing up different considerations which must be made before making command chaining happen. I'd love to get comments on these posts. Here's the first:
http://mitcho.com/blog/projects/explo...
The company thinks
this is one of the best points
EMPLOYEE
EMPLOYEE
