Add support for ^[[1m before/after color

[phmarek]

Please compare cat with vim for that one:

^[[1;31m[root@node1:~]#^[[0m crm configure
^[[32m^[[1mcrm(live)configure# ^[[0;10mshow
^[[33mnode^[[0;10m 01d9dc65-cb74-4b86-9b6e-edc617889193: ^[[0;10mnode1^[[0;10m \
    ^[[33mattributes^[[0;10m ^[[36mstandby^[[0;10m=^[[31moff^[[0;10m

Thank you very much!

[powerman]

Well… the sad truth is this plugin will never be able to handle all possible ANSI escape sequences - because this will require adding all possible combinations of all sequences into plugin code. And even this won't work because vim is not capable to handle so many syntax highlight rules. I've no idea is it possible to implement this functionality in some other way, without creating crazy amount of syntax highlighting rules.

So, this plugin is trying to support only most often used combinations of sequences, not all of them. If you believe this combination of sequences is used often enough to worth be supported - let me know and I'll try to add it.

[phmarek]

Uh, I thought these are "just" some more fore/background colors... basically, what some commands use when printing to a tty.

Basically, to get commands' output to HTML, my current workflow is ssh <host> -tt | tee /tmp/logfile, run the commands, then edit the logfile - and then I export my work via :TOHtml.
I don't need clear, cursor position, or similar things - just the colors should work as displayed.

Is there anything unusual in my output?

[powerman]

As far as I see it's ^[[32m^[[1m - which is same as ^[[1;32m (which is supported). Another one way to implement it is ^[[1m^[[32m, which is also not supported right now.

[powerman]

Actually I'd like to add support for ^[[1m before/after color, because I believe bold+color or color+bold is very common. But I'm afraid it'll be non-trivial change, at least at a glance I don't see easy way to do it. And right now I don't have enough spare time, so I'll keep this issue open and try to implement it later.

[joeytwiddle]

Worth nothing that the bold code won't necessarily come immediately after the colour. It could come later in the line, or even on a different line!

^[[32mThis line is regular green
^[[1mThis line is bold green
^[[32mThis line is still bold green!
^[[0;32mThis line is regular green

Certainly not trivial to syntax match.

I wonder if we could make ansiGreen a container, and have other matches inside it, e.g. ansiBoldInsideGreen.

But there are many more attributes than just bold (reverse and underline being quite popular). Even using a generator, generating syntax rules for every possibility ansiBoldInsideItalicInsideGreenInsideReverseInsideUnderline would be unfeasible due to exponential growth.

^[[mRESET
^[[32mThis line is regular green
^[[1mThis line is bold green
^[[4mThis line is underlined bold green
^[[7mThis line is underlined bold green reversed
^[[27mThis line is underlined bold green (reverse cancelled)
^[[mRESET

(Some of the SGR codes stack, some do nothing if already applied, a few cancel earlier codes. I haven't found any which toggle.)

Perhaps we could detect and generate only the rules needed for the current file.