-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature-request] command-line 'iskeyword' #14475
Comments
I guess it makes more sense to use the global |
Yes, global is fine too. Can such change break |
There are two distinct usages of command-line in this context. Issuing shell commands and issuing Vim commands. It would probably be ideal to have different iskeyword for each, but then it becomes sort of a rabbit hole. Also I feel like this comes up, as is the example above, with paths mostly. Edit: actually, in the shell I have two bindings: |
I use the config for the feature. " Better for <C-w> deletion
autocmd CmdlineEnter *
\ : let s:save_iskeyword = &l:iskeyword
\ | setlocal iskeyword+=.
\ | setlocal iskeyword-=/
\ | setlocal iskeyword+=-
autocmd CmdlineLeave *
\ let &l:iskeyword = s:save_iskeyword |
Is your feature request about something that is currently impossible or hard to do? Please describe the problem.
Currently, for some reason command-line is dependent on buffer-local
'iskeyword'
option. So for each buffer using command-line is inconsistent. Let's say buffer-local'iskeyword'
includes/
. Then trying to remove part of the path with<C-w>
in:e /some/path/to/file.txt
will remove whole path. It is really habit killer. Why it behaves like this? Why it depends oniskeyword
of specific language when command-line is more like for vimscript, path and sometimes shell commands?Describe the solution you'd like
Add new option to configure
iskeyword
only for command-line.The text was updated successfully, but these errors were encountered: