Dag Odenhall

This works in fish without nuggets.

I actually often find myself typing CTRL-A `echo` ENTER to see what command would actually execute before finally running it, and I imagine CTRL-X could be a better workflow that...

Working prototype, @gustafj might be interested: ``` function __fish_list for item in $argv echo $item | sed -e 's/ /\\\\ /g' end end function __fish_eval_token set -l token (commandline -t)...

Slightly better version: ``` function __fish_eval_token set -l token (commandline -t) if test -n "$token" set -l value (eval __fish_list $token | tr \n ' ') if test -n "$value"...

I've noticed it includes dots in word motions but thought it was something I did myself, intentionally, for sake of qualified names. However looking at the source I only ever...

So the definition of a "word" in Vim depends on the buffer-local `iskeyword` option, and the dot is probably included in `sh.vim` because dots are perfectly valid in shellscript keywords...

We could work around it on a per-option basis, which assumes we catch all problems and new ones aren't added. Basically ``` vim let l:iskeyword = &l:iskeyword syntax include ......

Yes, I notice it if I scroll quickly in a larger file (_edit: actually, this turns out to be mainly due to my using relativenumber_). In part it might be...

BTW: - Do you use any of these settings: relativenumber, cursorline, cursorcolumn, colorcolumn? - Do you use GVim or terminal Vim? - What kind of computer are you trying this...

You could try: - Disable settings that slow down drawing (see previous comment) - Play with `:syn sync` yourself (it turns out to be hard for me to figure out...