• meu135

    I don't know that switching to full repo's solves the problem - you'll still end up with lots of forks, and keeping track of which is the latest and greatest is still going to be a problem. I think the issue is that in a lot of cases these scripts arose out of having an itch to scratch, they're not created as long-haul projects. So, once you've scratched your itch, you're not really interested in the maintenance. I know that was my case with gistcheck.

    I think that the real solution is finding someone who wants to manage the maintenance of these scripts. Once you have that, then your problem is largely solved - regardless of whether the scripts live in a gist or a full repo. With an active custodian, there could simply be a sticky thread in the forum with a link to the "official" version (which is maintained) and some bootstrap code to help you pull that down.

    That being said, it is confusing with all the variants out there, and it would be awesome if some one wanted to step up and maintain these resources.

    Just my $.02.

    posted in Pythonista read more
  • meu135

    The app is fricken awesome, but i do have one request: Could you make the '\r' carriage return character work in the console?

    posted in Pythonista read more
  • meu135

    There is an option in the settings for the actions menu that allows you to hide scripts in the library view if you've set those scripts as items in your action menu. Go to Settings->Actions Menu->Hide in Library. That way scripts that you're using as actions menu items won't clutter up the library.

    posted in Pythonista read more
  • meu135

    I wanted to be able to write repeatedly to the same gist, so I wrote a little script that lets you write to and pull from a gist.

    https://gist.github.com/4043334

    If you just run the script, it will write three additional small scripts into your library. These additional scripts provide editor actions to set the gist associated with a file, commit to a gist, and pull from a gist. I haven't added support for creating gists yet...

    Anyway if you have an exiting gist with a file that you want to pull, you can create a blank file in the library with the same file name, run the gistcheck_set action to set the associated gist for the file (the value you enter should just be the gist id, that is 4043334 in the link above), then run the gistcheck_pull action. You'll end up with a copy of the file from the gist. Edit it as you desire. Then you can publish the changed version back using the gistcheck_commit action.

    Don't know if anyone else will find this useful, but I hope it helps someone.

    posted in Pythonista read more

Internal error.

Oops! Looks like something went wrong!