You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if this might be intended, but for example if my cursor | is on a word like |xSide , if I do a subword selection it selects Side, but if I'm on sideX|, I get X. Using camelcase I would expect x to also be a subword here and not jump ahead.
I see some commands are forward seeking but as far as I understood the table subword shouldn't be, but I'm getting jumping in cases like | xSide => Side as well.
I know it sounds maybe a bit odd to want a single character subword but reason I ran into this is I'm making a word cycling plugin and using this plugin to get the subword. And I'd like to be able to make single character replacements (e.g. x for y). I can work around this I think, but would be nice to just use subword directly.
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, for example "bump", and it will be kept open.
Bug Description
Not sure if this might be intended, but for example if my cursor
|
is on a word like|xSide
, if I do a subword selection it selectsSide
, but if I'm onsideX|
, I getX
. Using camelcase I would expectx
to also be a subword here and not jump ahead.I see some commands are forward seeking but as far as I understood the table subword shouldn't be, but I'm getting jumping in cases like
| xSide
=>Side
as well.I know it sounds maybe a bit odd to want a single character subword but reason I ran into this is I'm making a word cycling plugin and using this plugin to get the subword. And I'd like to be able to make single character replacements (e.g. x for y). I can work around this I think, but would be nice to just use subword directly.
Relevant Screenshot
No response
Reproduction & Sample Text
before:
|xSide
after:x|Side|
expect:|x|Side
before:
| xSide
after:x|Side|
expect:|x|Side
neovim version
Make sure you have done the following
The text was updated successfully, but these errors were encountered: