Steven Lu

Great! It works just like the other commands, which is consistent, which is good. Are you continuing to work on it? Maybe I will fork and try my hand at...

I noticed you changed the .history directory so that it no longer gets copied out when the plugin is updated. That's great. Do you think you can get a keyboard-issuable...

@vishr I know you posted on the forum but have you done so here? http://sublimetext.userecho.com/

I posted a plug for this plugin on this topic: http://sublimetext.userecho.com/topic/20126-undo-even-after-closing-and-reopening-file-storing-entire-undo-history/

I really wanted to implement logical statement text objects today, and this is holding me back. I was told in my topic https://github.com/wellle/targets.vim/issues/254 that these are regexes but I suspect...

OK from the code e.g. [implementation of argument text object](https://github.com/wellle/targets.vim/blob/master/autoload/targets/sources/argument.vim) we can see that some simple regexes are built and used for matching, but the mechanism seems to be that...

The way to deal with this is should probably be to leverage syntax highlighting state as a hint... Also the (pretty old) argtextobj vim plugin handles this case correctly, but...

``` [lspconfig] cmd ("cargo metadata --no-deps --format-version 1") failed: error: could not find `Cargo.toml` in `/` or any parent directory ``` from `:LspInfo`

I don't know what prompted it, but some sort of overlay showed up displaying: ``` ~ Language client log: /root/.local/state/nvim/lsp.log ~ Detected filetype: rust ~ ~ 0 client(s) attached to...

And here's what it shows on initial startup ``` Error detected while processing :source (no file) called at command line:0: E185: Cannot find color scheme 'nord' E5108: Error executing lua...