| #!/usr/bin/python | |
| from __future__ import print_function | |
| import base64 | |
| import commands | |
| import json | |
| import sys | |
| import uuid | |
| import xmltodict |
| from Crypto.Cipher import AES | |
| from Crypto.Util import Counter | |
| import struct | |
| """ | |
| typedef struct boot_dat_hdr | |
| { | |
| unsigned char ident[0x10]; | |
| unsigned char sha2_s2[0x20]; | |
| unsigned int s2_dst; |
| author: JeremyRuston, Syrte | |
| core-version: >=5.0.0 | |
| dependents: | |
| description: Markdown parser | |
| list: readme usage howto | |
| plugin-type: plugin | |
| revision: 0 | |
| title: $:/plugins/tiddlywiki/markdown | |
| type: application/json | |
| version: 6.0.0 |
- Use
curlto get the JSON response for the latest release - Use
grepto find the line containing file URL - Use
cutandtrto extract the URL - Use
wgetto download it
curl -s https://api.github.com/repos/jgm/pandoc/releases/latest \
| grep "browser_download_url.*deb" \
| cut -d : -f 2,3 \
| tr -d \" \| 1. Go to Sublime Text to: Tools -> Build System -> New Build System | |
| and put the next lines: | |
| { | |
| "cmd": ["python3", "-i", "-u", "$file"], | |
| "file_regex": "^[ ]File \"(...?)\", line ([0-9]*)", | |
| "selector": "source.python" | |
| } | |
| Then save it with a meaningful name like: python3.sublime-build |
| /** | |
| ** ______ _ _____ _ _ _ | |
| ** | _ \ | | / ___| | | (_) | | | |
| ** | | | |__ _ _ __| | __ \ `--. ___ | | __ _ _ __ _ _______ __| | | |
| ** | | | / _` | '__| |/ / `--. \/ _ \| |/ _` | '__| |_ / _ \/ _` | | |
| ** | |/ / (_| | | | < /\__/ / (_) | | (_| | | | |/ / __/ (_| | | |
| ** |___/ \__,_|_| |_|\_\ \____/ \___/|_|\__,_|_| |_/___\___|\__,_| | |
| ** | |
| ** Quassel Theme | |
| ** |
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j
| /** | |
| * ____ _ ___ ___ _ _ | |
| * | _ \ | | | \/ | | | (_) | |
| * | | \ |__ _ _ __| | __ | . . | ___ _ __ ___ | | __ __ _ _ | |
| * | | | | _` | '__| |/ / | |\/| |/ _ \| '_ \ / _ \| |/ // _` | | | |
| * | |_/ /(_| | | | < | | | | (_) | | | | (_) | <| (_| | | | |
| * |____/\__,_|_| |_|\_\ \_| |_/\___/|_| |_|\___/|_|\_\\__,_|_| | |
| * | |
| * Quassel Theme | |
| * |