For example suppose we have the following where | is point and $ is mark and
execute evil-numbers/inc-at-point.

```
|9 9$
```

Expected:

```
10 10
```

Actual:

```
10 9
```

This is because we would save the beginning and end of the region before we do
any changes, so the second 9 is pushed out of the saved region bounds by the
first 9 turning into a 10.

E.g. in the following position (where ^ shows where point is) we want to
increase 2, not 1 when calling inc-at-pt.

1 2
 ^

Previously negative numbers were not padded at all. Specifically calling
inc-at-pt on -1 yields +1.

This can help people who defer a lot of package-loading.

Explicitly require evil.

The magic autoload comment only works automatically for defun and the like. For
macros such as evil-define-operator it will copy over the whole definition
resulting in errors due to other parts of the file not being loaded.

Autoload operators as interactive commands

Imagine we're editing hyphen-separated numbers like the following:

    cursor:          v
    text:   2020-01-02

When we invoke 'inc-at-pt', we want the last number to change:

    cursor:          v
    text:   2020-01-01

(Note that the number is decremented instead of being incremented due to
the leading '-'. This also matches Vim behavior)

However, evil-numbers currently change the first number instead:

    cursor:    v
    text:   2021-01-02

This patch fixes evil-numbers to match the expected behavior.

fix: handle hyphen-separated numbers correctly

Resolve Warning: looking-back called with 1 argument, but requires 2-3.

Resolve looking-back warnings

Quiet checkdoc warnings

Enable lexical binding, remove unused function 'pad'

Tabs were used inconsistently in a few places.

- Start summery with upper-case.
- Only use keywords in finder-known-keywords.
- Depend on emacs 24.1 (since lexical binding was added).

Move the 't' condition onto the next line to avoid right shift.

Currently package-lint-current-buffer warns about breaking
the convention of using dashes for separators.

While this can't be changed with the public functions,
the convention can be used for private functions.

This also has the advantage of abbreviating function display
with nameless-mode.

Cleanup: use '--' separator for private functions

Avoids right-shift.

Replace logic for scanning the number that works in both directions.

Prepare for fixing #17

When decrementing 0x0 for eg. it became 0x-1 instead of -0x1.

Making the code easier to follow.

Only apply the cursor motion on success.

Quiet checkdoc warning

Forward padding as an argument.

Instead of searching for a number when handling selection,
make evil-numbers/inc-at-pt responsible for finding the next number.

This check relates to an implementation detail of how looking-back works,
the caller should not have to be aware of this.

This argument is an absolute position,
not relative to the point.

Also apply limit to skip-chars-forward.

Can't use `end' as this value changes while looping.

Gives nicer preview, already used for the readme.

- Add myself as a contributor.
- Use capitals, full-stops.
- Capitalize VIM.
- Clarify that this works with the cursor before the numeric literal.

This simplifies evil-numbers/dec-at-pt point placement and error
handling, as this logic is called direction and in a loop.

`evil-numbers--search-and-replace` now takes decode/encode functions
so it can be used with subscript and superscript characters.

This avoids an entirely separate code-path for decimal operations.

Resolves #19

While the difference isn't significant in this case,
matching a single character as whats intended.

Since the caller takes limits, it makes sense to forward them
to evil-numbers--search-and-replace instead of using the line bounds.

Use more conventional naming for settings.

Instead, use simple search, rely on `evil-numbers--search-and-replace'
to perform more detailed checks.

This allows us to have a single place where parsing and searching
is performed.

- Split key bindings into their own section.
- Add use-package example.
- Add myself as a contributor.

This isn't needed.

Allow setting the default case for hexadecimal values.

Optionally support numbers with single separators such as:

- `16_777_216`
- `0x10_000`
- `4,294,967,296`

Reads a little nicer.

This opens up possibilities for changing the number in other ways
besides addition.

When the cursor couldn't move forward numbers directly before it
were manipulated.