Kenneth Ballenegger

Okay… so, after a bit more digging I've narrowed down the cause of the issue to any of 3 custom rules I've added: ``` call lexima#add_rule({'char': ''}) call lexima#add_rule({'char': '>',...

`nvim --version` ``` NVIM 0.1.7 Build type: RelWithDebInfo Compilation: /usr/local/Homebrew/Library/Homebrew/shims/super/clang -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -g -DDISABLE_LOG -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -DHAVE_CONFIG_H -I/tmp/neovim-20170116-138-1h33iaz/neovim-0.1.7/build/config -I/tmp/neovim-20170116-138-1h33iaz/neovim-0.1.7/src -I/usr/local/include...

Is anybody interested in pointing me in the right direction for building this myself?

It doesn't really make a difference. The `IndentGuideEnable` command is global, it enables it for all buffers.

Is this issue dead? This is still very much a problem for me day-to-day :(.

Not sure how to re-open this, but I don't find `indent_guides_exclude_filetypes` to be sufficient. It's unreasonable to list every possible filetype in a blacklist when all you're looking is to...

It's funny because except for the application folder, I've pretty much moved to exactly the structure I describe in here and it's working out awesome. I have a github fork...

I hadn't thought of doing it as an explicit "transaction." I think that'd solve the problem I'm describing. However, I was thinking that it'd be better to make a conceptual...

I can **try**[1] to make a pull request to show you what I mean, if that's something that sounds interesting to you. However, what I'm suggesting would change the semantics...

Any thoughts on moving towards something like this after all?