Daniel Hahler
Daniel Hahler
It should undo what `:HighlightTags` did, and therefore act on the current file / buffer. `:ClearTags!` might then act on every (affected) buffer maybe.
Thanks! > I prefer :HighlightTagsOff over :ClearTags :+1:
Used this `.vintrc.yml`: ```yaml policies: ProhibitUnnecessaryDoubleQuote: enabled: no ```
Something like [autoclose (my fork)](https://github.com/blueyed/vim-autoclose) (or snippets, e.g. via [snipMate](https://github.com/MarcWeber/snipmate.vim)) might work better in this case, or good enough as a workaround for now.
There is a test in endwise.vim which invokes/includes the previously defined mapping: ``` elseif maparg('','i') =~ '' exe "imap ".maparg('','i')."AlwaysEnd" exe "imap ".maparg('','i')."DiscretionaryEnd" ``` Considering the recommended mapping of `inoremap...
See also https://github.com/ervandew/supertab/commit/c6d704c6daf64b85828d99a88f9099efc7e01299 for inspiration.
@pjg Did you get this resolved back then? You might want to check out my pull request, which improves the mapping setup: https://github.com/tpope/vim-endwise/pull/50
Great. This issue might get closed then probably. > YouCompleteMe+Eclim > :+1:
@chrisnicola What is your mapping for `:imap `? (I am using a custom function, where I chain multiple plugins:) ``` fun! My_CR_map() " "" via delimitMateCR let r = "\delimitMateCR"...
The vim-session plugin has an option `g:session_persist_globals` to define a list of globals that should get persisted (FWIW, it also executes `sessionoptions-=options` unconditionally).