XPM is the superior image format. Here's an example:
chromium.googlesource.com/chromium/src.g
Here's how it looks in Vim with true color support enabled:
paste.xinu.at/jF7MV
Most Vim users don't realize they're misusing an image manipulation tool as a text editor.
Conversation
Replying to
it's awesome that .xpm files are readable with ordinary text editors, but, take our word for it, raster graphics are not exactly a truly pleasant thing to deal with if you count in user interfaces, different resolutions and things like HiDPI
2
Replying to
I'm well aware of the benefits of vector graphics and compression.
The favicon for grapheneos.org in modern browsers is a 1306 byte SVG with dark mode support via a CSS query with (prefers-color-scheme:dark). 641 bytes in practice due to Brotli pre-compression.
1
1
1
I'm not seriously suggesting that XPM should be used over proper image formats. Rather, it's hilarious to have an image format defined as valid C code with WYSIWYG editing in Vim. Suggest looking at my thread again. I think it's fairly clear I was joking.
Quote Tweet
XPM is the superior image format. Here's an example:
chromium.googlesource.com/chromium/src.g
Here's how it looks in Vim with true color support enabled:
paste.xinu.at/jF7MV
Most Vim users don't realize they're misusing an image manipulation tool as a text editor.
en.wikipedia.org/wiki/X_PixMap
Show this thread
Quote Tweet
There are all these fancy modern image formats based on HEVC, AV1, etc. but how many of them can be compiled to an object file with Clang and loaded in a debugger? Clearly, something went wrong standardizing those.
Show this thread
1
1
2
Quote Tweet
In case you actually want to know something useful, here's how to enable true color support for console Vim:
let &t_8f="\<Esc>[38;2;%lu;%lu;%lum"
let &t_8b="\<Esc>[48;2;%lu;%lu;%lum"
set termguicolors
Once that's enabled, it will render XPM images using syntax highlighting.
Show this thread
1