Hi Jonathan, When you subscribe to a command, on the warning screen that comes up, there should be a check box at the bottom of the screen that says "auto-update this feed". If you check that box, then the commands in the feed get re-loaded each time you hit the ubiquity hotkeys. So that's what most command developers do. You might have to unsubscribe from your own feed and then resubscribe by visiting the page and clicking the subscribe button.
I don't know exactly how you have your CGI set up, or whether that would be interefering with normal re-loading of commands. May I ask why you have a cgi script that generates them, instead of a static javascript file? Another thing you might consider is debugging in the built-in command editor (you can get there with the "command-editor" command) and then moving the code to its final location once the debugging is done. --Jono On May 19, 3:18 pm, Jonathan Micklos <[email protected]> wrote: > At work, I have a cgi which generates at least 100+ ubiquity commands. > Anytime I update this cgi, debugging is a pain because I have resubscribe or > close and reopen Firefox every time I want to see my changes. Is there an > easier way to refresh the cache of the commands for a given subscription > source? If not, would it be possible to place an update link on the homepage > next to each subscription? > > Thanks! > > -Jonathan > > -- > Jonathan Daniel Micklos | Software Development Engineer | Amazon.com > [email protected] > > Work hard. Have fun. Make history.http://Amazon.com/Careers --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ubiquity-firefox" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/ubiquity-firefox?hl=en -~----------~----~----~----~------~----~------~--~---
