On Tue, August 20, 2013 09:02, Ingo Karkat wrote: > Note that concealing has to extend the existing syntax, which can break > it.
Well changing the syntax rules is of course a way of breaking it, but I think it should work well enough most of the times. And while I am not very proficient with syntax highlighting, I haven't seen it break yet. > You need autocmds to set it up (and keep it when the syntax > changes). You usually want to create a toggle, so you could simply create a custom command that set's up the highlighting. To disable it, it should be enough to call :syntax enable. Not sure, how often you will encounter "syntax changes" after the buffer has been loaded into a window. > And it's buffer-local, not window-local like :set list. So > while it is a workaround, it is not a particularly good one. You can use :ownsyntax to work around this as well. >> Anyway for me *listchars* seems like the way it should be . > > Since there seems to be quite some interest in this, offering this via > 'listchars' indeed looks like the preferable solution. +1 I don't have a particular strong opinion about that, I just wanted to point out an existing alternative. regards, Christian -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
