#4 "Paste All" feature

[Eliot Lash]

I've updated Jumpcut to build against the OSX 10.11 SDK and added a "Paste All" menu item that merges the entire clipping history into a single paste. A new build is included along with git and standard patches. I also set up a git fork here:
https://github.com/fadookie/jumpcut

As this project seems to have been abandoned by its maintainer, perhaps we should fork it and move future work to github?

[Tybion]

Brilliant. Just what I needed. Have downloaded and using in Sierra.

[Eliot Lash]

Thanks! One caveat, I think there may be a bug in my implementation at the moment, see https://github.com/fadookie/jumpcut/issues/1

[Steve C]

Abandoned by its author is almost but not quite entirely accurate (I am the author). I've been thinking that I should do a new release soon to deal with legitimate security concerns about use of non-HTTPS downloads of the Sparkle appcast. The last thing I want is for someone to get their computer rootkitted because they use Jumpcut.

I make no promises about the likelihood of a new release, but if it does happen, it's going to happen on GitHub. I'd encourage you to fork there, and if I do find the time and energy to make a new release happen, I will examine pull requests.

[Steve C]

https://github.com/snark/jumpcut

[Eliot Lash]

Thanks for the update, Steve. I did eventually find the new github repo, but only after I spent a few hours getting the svn trunk to build against the OSX 10.11 SDK and making my changes there, which is why I submitted this issue about deprecating the sourceforge page: https://github.com/snark/jumpcut/issues/9

As you're not sure if you will be able to continue maintenance, would you consider the possibility of allowing in some additional maintaners? I will volunteer as an interim maintainer if that would be helpful. At this point I don't know if I could take that on long-term, but I depend daily on Jumpcut and I'd be happy to lend a hand, especially to help ease the transition to spreading out maintenance duties to several volunteers. We could have a github organization which owns the "official" repo. I'm also happy to help clean up this sourceforge project to point people towards github. Its high pagerank and amount of highly visible inbound links means I think that people will wind up here for a good while when looking for the latest jumpcut release and development activity.