*Kim Zick

Additionally, this resolves #27

I'm not really sure how to reproduce the error showing up on Travis, considering everything runs fine within a nix shell locally

Apparently it runs fine within a nix shell on Travis as well

Understandable. I don't know of any community syntax for this though, which is why I went with a leading comment, making it benign for anyone who doesn't use a syntax...

Some type of prefix could be handy to make it a bit more explicit. As far as flexibility goes though it's able to load any syntax available to vim itself,...

The `~` prefix matches any part of the command string, which can result in restoring commands that happen to have an argument that contains the text being matched

I'm seeing this with Neovim on NixOS (Linux) due to wrappings. Going to try @donat-b's changes, since they're in the same vein as what I was looking at doing.

Looks like it needed a small adjustment to disable wrapping output from `base64`. Submitting a PR

Custom rules require exposing full URLs to the API, which could be considered a major security risk if the URLs contain session or personal information

@Swiip If that's the decision, should the documentation be updated? This caught me off guard as well. Are the locations it needs to be updated shown in a search for...