Twitter command always thinks "as" == (as twitter username)
At some point Ubiquity's Twitter command was updated to allow a modifier (as twitter username).
I've noticed recently (using 0.1.6), every usage of the word "as" triggers this modifier code. Even if I hit the down-arrow there is never an interpretation that treats an occurrence of "as" correctly (i.e., not as a modifier but as a word).
Am I missing something?
I've noticed recently (using 0.1.6), every usage of the word "as" triggers this modifier code. Even if I hit the down-arrow there is never an interpretation that treats an occurrence of "as" correctly (i.e., not as a modifier but as a word).
Am I missing something?
7
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?My recommendation is that the Twitter command logic should only match (as twitter username) if "as" is the second to last word and if the very last word is a valid twitter username.
I’m trying to be helpful.
-
Inappropriate?I am grappling with this issue for a few days now.. Googling/looking into documentation/forums/view code etc. There doesn't seem to be any apparent identification or resolution immediately available. And sure, while using Ubiquity extensively it can get a bit frustrating at times.
Since twitter status text is expected to follow normal English usage, giving an 'escape' for "as" (like \as) would be unintuitive.
I would suggest to 1) un-reserve "as" and return it to the English usage, and 2) escape "as" for twitter username until a better implementation is found.
I’m lost over an explanation
-
Inappropriate?Argh, sorry about this guys. It's a known bug in Ubiquity and we're going to try to fix it as soon as we can:
https://ubiquity.mozilla.com/trac/tic... -
Inappropriate?Er, this is actually the real bug:
https://ubiquity.mozilla.com/trac/tic...
And it just got fixed, so we'll be pushing out a new version of Ubiquity as soon as we can!
1 person says
this solves the problem
-
Inappropriate?Ok now, the command doesn't accept the 'as' keyword anymore:
e.g. twitter Bla bla bla this [address bar selection] as [username]
actually posts:
Bla bla bla [address] as [username]
Also, it keeps asking me for my username and password now, even tho it's been told to save it!
I’m frustrated
-
Inappropriate?Which Ubiquity skin are you using? Unfortunately some skins (such as Simpliquity) don't allow you to choose between multiple options and just present the first one. The new command behavior treats "as" literally first and as a modifier second.
Switching to a skin such as "Ubiquity Evolved" should allow you to choose between the multiple options.
As for the username and password prompt, I believe it should prompt once per browser session. It's the least annoying of the possible options at this point because other ways of remedying it break things in worse ways. -
The prompt is most definitely not once per session (it's every time). I'm trying the new skin. I'll let you know how it works once I've played with it a bit. -
The new skin seems to be giving me the right preview, and also automatically tinyurl'ing addresses (which it wasn't doing before - not sure if this was a fix with the skin being used, or the recent update to Ubiquity 0.2). -
I believe the issues were probably fixed in the latest beta version and now the latest release.
As for the prompting issue, it might be helpful to either post your Ubiquity/Firefox/OS versions and if you are using a master password, or to file a bug report on trac. -
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-GB; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3
0.2pre29
No master password.
Cheers, -
Inappropriate?Oh, it looks like Simpliquity does allow you to choose between options. You can use the down arrow key to select the second option.
-
Inappropriate?Kop,
Just in case it comes up again, which skin were you using before?
I'll try to replicate the behavior you're talking about and file a bug. I've had some inconsistent behavior too, but I don't use the twitter command enough to track down the issue.
Thanks!
Heather
1 person says
this solves the problem
-
Inappropriate?I was using the 'Custom' option. I haven't had a chance to switch back down and see if it's happening on both 0.1 and 0.2. I'll give it a go when I have some time.
Cheers,
I’m thankful
Loading Profile...




