saret/ChocolateyPackages
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

feat(ST2.GitPackages): bump up all packages

Browse Source 
- Refresh PackageCache with latest versions of everything
This commit is contained in:
Iristyle
2013-09-16 22:32:31 -04:00
parent fad58909f7
commit 3a0c5ce9e2
43 changed files with 6367 additions and 1395 deletions
Download Patch File Download Diff File Expand all files Collapse all files

110
EthanBrown.SublimeText2.GitPackages/tools/PackageCache/sublime-github/README.md
View File

@@ -1,38 +1,24 @@
# Sublime GitHub
This is a plugin for the [Sublime Text 2](http://www.sublimetext.com/) text
editor that allows you to create and browse your [GitHub Gists](http://gist.github.com).
This is a plugin for the [Sublime Text](http://www.sublimetext.com/) text
editor (both versions 2 and 3) that provides a number of useful commands for GitHub, including creating and browsing gists,
opening and editing files on GitHub, and bringing up the blame and commit history views.
## Installation
**The easiest way to install is via the** [**Sublime Package Control**](http://wbond.net/sublime_packages/package_control) **plugin.**
Just open "Package Control: Install Package" in your Command Palette and search for
"sublime-github" (or, if you already have it installed, select "Package Control: Upgrade Package"
to upgrade).
To install it manually in a shell/Terminal (on OS X, Linux or Cygwin), via git:
cd ~/"Library/Application Support/Sublime Text 2/Packages/" # location on OS X; will be different on Linux & Windows
git clone https://github.com/bgreenlee/sublime-github.git
or, if you don't have git installed:
cd ~/"Library/Application Support/Sublime Text 2/Packages/"
rm -rf bgreenlee-sublime-github* # remove any old versions
curl -L https://github.com/bgreenlee/sublime-github/tarball/master | tar xf -
The plugin should be picked up automatically. If not, restart Sublime Text.
You can install via [**Sublime Package Control**](http://wbond.net/sublime_packages/package_control) plugin.
Just open "Package Control: Install Package" in your Command Palette and search for "sublime-github". The plugin should be picked up automatically. If not, restart Sublime Text.
## Usage
The first time you run one of the commands, it will ask you for your GitHub
username and password in order to create a GitHub API access token, which gets saved
in the Sublime GitHub user settings file. Your username and password are not
stored anywhere, but if you would rather generate the access token yourself, see
the "Generating Your Own Access Token" section below.
The first time you run one of the commands, it will ask you for your GitHub username and password in order to create a GitHub API access token, which gets saved in the Sublime GitHub user settings file. Your username and password are not stored anywhere, but if you would rather generate the access token yourself, see the "Generating Your Own Access Token" section below.
The following commands are available in the Command Palette:
* **GitHub: Switch Accounts**
Switch to another GitHub account (see Adding Additional Accounts below)
* **GitHub: Private Gist from Selection**
Create a private gist from the currently selected text (or, if nothing is selected,
@@ -77,21 +63,27 @@ The following commands are available in the Command Palette:
Update the gist open in the current editor.
* **GitHub: Switch Accounts**
Switch to another GitHub account (see Adding Additional Accounts below)
**The following commands require the Git plugin, available through the Package Manager. After installing, restart Sublime Text.**
* **GitHub: Open Remote URL in Browser**
Open the current file's location in the repository in the browser. *Note:* Requires
the Git plugin, available through the Package Manager. After installing, restart
Sublime Text.
Open the current file's location in the repository in the browser.
* **GitHub: Copy Remote URL to Clipboard**
Put the url of the current file's location in the repository into the clipboard.
*Note:* Requires the Git plugin, available through the Package Manager. After
installing, restart Sublime Text.
* **GitHub: Blame**
Open the GitHub blame view of the current file in the browser
* **GitHub: History**
Open the GitHub commit history view of the current file in the browser.
* **GitHub: Edit**
Open the current file for editing on GitHub. I'm not sure why you'd want to do that, but it was easy enough to add.
## Adding Additional Accounts
@@ -116,40 +108,42 @@ whatever the base url is for your private GitHub, plus "/api/v3". For example:
{
"base_uri": "https://github.yourco.com/api/v3",
"github_token": ""
},
}
}
Don't worry about setting the `github_token`--that will be set for you automatically, after you
switch accounts (Shift-Cmd-P, "GitHub: Switch Accounts").
## Key Bindings
You can add your own keyboard shortcuts in Preferences -> Key Bindings - User. For example:
[
{ "keys": ["ctrl+super+g", "ctrl+super+n"], "command": "public_gist_from_selection" },
{ "keys": ["ctrl+super+g", "ctrl+super+p","super+n"], "command": "private_gist_from_selection" },
{ "keys": ["ctrl+super+g", "ctrl+super+o"], "command": "open_gist_in_editor" },
{ "keys": ["ctrl+super+g", "ctrl+super+c"], "command": "open_gist_url" }
]
(Note that `ctrl+super+g` (^⌘G) conflicts with Sublime Text's Quick Find All, so adjust accordingly.)
Available commands can be seen in <https://github.com/bgreenlee/sublime-github/blob/master/Github.sublime-commands>.
## Issues
* Linux requires the [curl](http://curl.haxx.se/) binary to be installed on your system (in one of:
`/usr/local/sbin`, `/usr/local/bin`, `/usr/sbin`, `/usr/bin`, `/sbin`, or `/bin`).
* Depending on the number of gists you have, there can be a considerable delay the first time
your list of gists is fetched. Subsequent requests will be cached and should be a bit faster
(although the GitHub API's ETags are currently not correct; once that fix that, it should speed
things up). In the meantime, if there are gists that you open frequently, open them on GitHub and
"Star" them, then access them via the Open/Copy Starred Gist commands.
* Depending on the number of gists you have, there can be a considerable delay the first time your list of gists is fetched. Subsequent requests will be cached and should be a bit faster (although the GitHub API's ETags are currently not correct; once they fix that, it should speed things up). In the meantime, if there are gists that you open frequently, open them on GitHub and "Star" them, then access them via the Open/Copy Starred Gist commands.
* Setting the file type for syntax highlighting when opening a gist in the editor does not work
in Linux. I could get it to work with significant effort, so if you desperately want it, open
an issue.
* Setting the file type for syntax highlighting when opening a gist in the editor does not work in Linux. I could get it to work with significant effort, so if you desperately want it, open an issue.
## Generating Your Own Access Token
If you feel uncomfortable giving your GitHub username and password to the
plugin, you can generate a GitHub API access token yourself. Just open up
a Terminal window/shell (on OS X, Linux or Cygwin), and run:
If you feel uncomfortable giving your GitHub username and password to the plugin, you can generate a GitHub API access token yourself. Just open up a Terminal window/shell (on OS X, Linux or Cygwin), and run:
curl -u username -d '{"scopes":["gist"]}' https://api.github.com/authorizations
where `username` is your GitHub username. You'll be prompt for your password first. Then you'll get back
a response that includes a 40-digit "token" value (e.g. `6423ba8429a152ff4a7279d1e8f4674029d3ef87`).
Go to Sublime Text 2 -> Preferences -> Package Settings -> GitHub -> Settings - User,
and insert the token there. It should look like:
where `username` is your GitHub username. You'll be prompt for your password first. Then you'll get back a response that includes a 40-digit "token" value (e.g. `6423ba8429a152ff4a7279d1e8f4674029d3ef87`). Go to Sublime Text 2 -> Preferences -> Package Settings -> GitHub -> Settings - User, and insert the token there. It should look like:
{
"github_token": "6423ba8429a152ff4a7279d1e8f4674029d3ef87"
@@ -159,6 +153,24 @@ Restart Sublime.
That's it!
## Configuring a proxy
If you are behind a proxy you can configure it for each account.
Note that until a [bug](https://github.com/shazow/urllib3/pull/170) in urllib3 is fixed, in order to use a proxy you also have to force curl mode (Curl is required obviously).
For example:
"accounts":
{
"GitHub":
{
"base_uri": "https://api.github.com",
"https_proxy": "...",
"force_curl": true
}
}
## Bugs and Feature Requests
<http://github.com/bgreenlee/sublime-github/issues>