On 2016-05-25 03:12, Carpii UK wrote:
Looks interesting, I will have a play around with this when I can I was hoping I might be able to call out to ImageMagick to generate a suitable ICNS icon, but from what I can see it doesn't support ICNS forma, which is a shame.
I don't think ICNS is a requirement. The built-in icons, error and warning, use PDF, IIRC.
- Do 'marks' persist in any way, in projects or maybe tm settings?
Ie, if I was to pass a /tmp/some_temp_file.icns, would that cause an issue later if the /tmp file was later deleted and Tm relaunched?
- I wonder how feasible it would be for TM to allow a new switch in the
mark API, something like... "$TM_MATE" --set-mark-bg-color "#FF0000" --line 3
This would let us set the background color of the gutter, irrespective of the theme And also allow it to be used independantly of the current monochrome marks feature.
Just a thought anyway, not sure how easy it would be
Probably not that hard.
If mark icons are used for this I can see that this could cause conflicts with errors or warnings for something like a CSS preprocessor (Sass, LESS) or perhaps a CSS linter. I assume the mark icons for the color should be persistent, but, as far as I know, it's only possible to have one icon per line. If one runs a build command for Sass or LESS which use marks to report errors they would override the colors.
I think setting the background color as the Atom Pigments pulgin does would be pretty cool. Just make sure it's possible to turn off somehow. The Atom Pigments plugins has a couple of different ways to display the colors .
An additional alternative would be to have a tooltip showing the color on mouse hover. Or is it important that the color is always visible?