Execution word boundaries should be different from movement word boundaries

[driusan]

The word boundaries used for executing a text selection shouldn't be the same as the movement commands. The movement command word boundaries should be the same as in vi, but for the sake of executing a word it should be a little looser about what it considers a boundary (for instance, . and / are often part of a filename or path, so they shouldn't be considered separators when middle clicking or hitting enter.)

[driusan]

Commands are now only deliminated by whitespace, and movement words by various other characters. (If the characters don't match up with vi, it should be added to issue #1)