When indenting or unindenting a code block, I normally visually select
it and use < or >. However, both of these unselect the selection.
The mappings make vim also do gv after such an action which re-selects
the previous selection.
File was simply taken from my old Vim configuration.
It inherits most of the html syntax as it is set on responses as well as
requests
Also, adds some request / response specific highlighting for things like
http method etc.
By default, vim's reg-ex matching is weird. For example:
> * is special when not escaped but…
> + is special when escaped
> \{x,y} (escaping only the opening bracket) works but…
> You have to use \( \) (escape both parens)
> [] is special when both are unescaped
Source: https://wincent.com/wiki/Vim_regexes
For more details, check out Greg Hurrell's screencast:
https://www.youtube.com/watch?v=VjOcINs6QWs
Vim can open external files when the cursor is "over" them by pushing gx
If in a netrw window, simply x is used.
This is useful when in, for example, a markdown file. I can view the
image by putting the cursor over the path and pushing gx
Defines functions for each as autoload functions. I need to look into
weather it would be better to have this as a local function in a plugin.
The function for url encoding was taken from vim-unimpared:
https://github.com/tpope/vim-unimpaired
I don't need all the functionality it provides
The function for base64 encoding was taken from vim-base64:
https://github.com/christianrondeau/vim-base64
although I use it with mappings in the vim-unimpared style
[b and ]b base64 encode and decode respectively
[u url encodes characters that are normally encodede in a url
[U url encodes all characters
]u and ]U both urldecode all encodede characters
Writing mode is to be used when I am writing prose rather than code, for
example markdown files or emails.
Currently, it enables spellcheck and adds insert mode mappings that add
undo points when certain punctuation is inserted, such as full stops or
commas.
Currently this is used for markdown files, emails and git commits
The shebang line is used to determine which should interpreter should be
used when executing the file
The mapping here adds the string `#!/usr/bin/env ` at the begining of
the line.
https://en.wikipedia.org/wiki/Shebang_(Unix)
Jonathan Hodgson