> It always has seemed to me to be a bit of a battle to handle continued > lines.
If you define a pattern like this: syn match escapedChar /\\\_./ or maybe in your case: syn match escapedChar /\\\n/ before any other rule, there might be a chance to handle these cases if escapedChar is included in a cluster and an eligible pattern at this position. At least, that's the way this is handled in viki. In most circumstances it would probably be preferable though to have a magic version of . or \_. that is aware of a filetype-specific continuation pattern. (In vimscript, the continuation is defined by the next line.) In conjunction with syn-region you could also use skip, I suppose. Regards, Thomas. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
