Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

24
  • +1e100 I see you went after the other half of the cash! See my "answer" for a bug report. I don't know if it's specific to your version or also applies to the original. Commented Mar 16, 2011 at 1:34
  • 1
    @Dennis: Please take a look at the note I added to this post. Commented Mar 16, 2011 at 19:16
  • In his updated original post, Jakub asks "BTW does the auto-update system work?" Is this functional in your build for the end user (e.g. me)? Commented Mar 20, 2011 at 20:07
  • @Dennis: It should be. I just checked and it seems like the build script is functioning as expected. Commented Mar 20, 2011 at 20:33
  • So I don't need to manually update? Commented Mar 20, 2011 at 20:37
  • @Dennis: Sorry, yes - you do need to update. What is meant by 'auto-update' is that the script you update from is itself updated daily directly from the source code on GitHub. Commented Mar 20, 2011 at 21:00
  • OK, since Jakub didn't qualify his question I though he meant that code had been added to auto-update the end-users installed copy. Sorry for the confusion. Commented Mar 20, 2011 at 21:12
  • @Dennis: No problem. I understand the confusion - although an auto-update for the installed copy would be nice! Commented Mar 20, 2011 at 21:18
  • @Dennis the autoupdating I had in mind is a Safari feature that should automatically update the extension based on this file gampleman.github.com/SE-Editor-Toolkit/updates.plist Commented Mar 22, 2011 at 16:34
  • The userscript doesn't seem to work - have tried in Firefox 3.6 and 4.0... Commented Mar 26, 2011 at 6:52
  • @studiohack: What errors do you get when running the script? Commented Mar 26, 2011 at 19:34
  • @GeorgeEdison: I don't get anything, nothing shows up at all...I've seen screenshots of what it is supposed to look like, but nothing seems to appear...I've had several other users (on SU) also say the same thing... Commented Mar 26, 2011 at 19:41
  • @studiohack: It currently only works on Meta.SO. Commented Mar 26, 2011 at 20:26
  • 1
    @Jakub: I haven't had time to set that up yet. But it's planned. Commented Mar 27, 2011 at 16:43
  • 2
    As per @Sathya's bug report below, is there any chance of fixing this for inline editing? Can't get it to work on Chrome Dev. Commented Aug 25, 2011 at 10:55