ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Bitly

by the0ther ST2

No description provided

Details

  • 0.1.4
  • github.​com
  • github.​com
  • 11 years ago
  • 36 minutes ago
  • 11 years ago

Installs

  • Total 25
  • Win 14
  • Mac 8
  • Linux 3
Nov 21 Nov 20 Nov 19 Nov 18 Nov 17 Nov 16 Nov 15 Nov 14 Nov 13 Nov 12 Nov 11 Nov 10 Nov 9 Nov 8 Nov 7 Nov 6 Nov 5 Nov 4 Nov 3 Nov 2 Nov 1 Oct 31 Oct 30 Oct 29 Oct 28 Oct 27 Oct 26 Oct 25 Oct 24 Oct 23 Oct 22 Oct 21 Oct 20 Oct 19 Oct 18 Oct 17 Oct 16 Oct 15 Oct 14 Oct 13 Oct 12 Oct 11 Oct 10 Oct 9 Oct 8
Windows 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Mac 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Linux 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

Bit.ly Sublime Plugin

Hello, this is a small plugin I've put together based on a demo I found on the web at Nettuts+.

I find the URL-shortening service Bit.ly to be quite handy. Short URLs are aesthetically pleasing, to be sure. The thing I really like about Bit.ly though are the reports I can get about shortened links I've sent others.

This is an early release.

Contributions are welcome, there are some bugs I'm quite sure. A little short on time here…aren't we all?

Settings

The only settings for this plugin are account-related. You can use this plugin with your own account by using the following settings:

{
    "api_login": "<YOUR_BITLY_USERNAME_HERE>",
    "api_key": "<YOUR_API_KEY_HERE>"
}

To get a new API key from Bit.ly visit this link.

Todos

  • Add instructions for obtaining API from Bit.ly
  • Add in contextual menu, so you can choose 1 URL to shorten
  • Check config, provide user feedback if the user provides invalid username/api-key
  • New Features
    • “Shorten all Markdown formatted links”
  • Rebrand/Rename this as a tool to “Monitor Links”, the way I use it to verify if people bother to look at links I've put into a document.

Issues

  1. Needs tests
  2. The regular expression used to detect URLs is not well-tested.
  3. May change so it ensures no spaces in the highlighted string, as a safety precaution. As it works now a user may select a large string with spaces and this has unpredictable behavior. At least test out what happens and perhaps update the code to prevent it, if that is not already happening.