`metaGo.cursorSpaceWordLeftSelect` functionality change

[omgreenfield]

Summary

The cursorSpaceWord suite of commands has had a shift in functionality and it seems unintentional since, from my point of view, it's less useful. If it was intentional, I think a great addition would be the ability to configure one approach over the other.

Examples

I used to be able to select large uninterrupted strings with a single key press, but now I need to make additional key presses depending on the situation.

The below examples show my cursor position as _.

Example 1

Previously, the metaGo.cursorSpaceWordLeftSelect and similar commands would move to up to the next available space. Now it moves past every non-broken whitespace

# Start:
some_variable_name = "some:really:long:string:with/delimiters-that-make-it-multiple-words"_

# Invoke `metaGo.cursorSpaceWordLeftSelect`

# Before, cursor would end up here:
some_variable_name = _"some:really:long:string:with/delimiters-that-make-it-multiple-words"

# Now, cursor ends up here
some_variable_name =_ "some:really:long:string:with/delimiters-that-make-it-multiple-words"

Example 2

          # Start
          "some/intended/long/collection/of/characters"_

          # Invoke `metaGo.cursorSpaceWordLeftSelect`

          # Before, cursor would end up here:
          _"some/intended/long/collection/of/characters"

          # Now, cursor ends up here
_         "some/intended/long/collection/of/characters"

If this was intentional, could you share what its purpose is?

---

I appreciate your creation and your time. Thanks for all you do.