GLOOM-OS

[logandaddy12-dot]

OS

NAME="Gloom-OS"
PRETTY_NAME="Gloom-OS"
ID=gloom-os
ID_LIKE=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;255;30;30"
HOME_URL="https://rxvyedits.com/"
DOCUMENTATION_URL="https://rxvyedits.com/"
SUPPORT_URL="https://rxvyedits.com/"
BUG_REPORT_URL="https://rxvyedits.com/"
LOGO=gloom-os

Distro Website

rxvyedits.com

ASCII Art

^[[38;2;255;30;30m                    ╋      ╋
^[[38;2;255;40;30m                  ▟▛      ╜▙
^[[38;2;255;50;30m     ▞▀▖       ▟▛        ▜▙      ▝▀▖
^[[38;2;255;60;30m    ▌  ▜▙     ▟▛          ▜▙    ▟▛  ▐
^[[38;2;255;70;30m   ▙   ▜▙   ▟▛   ▗▟▀▙▖   ▜▙   ▟▛   ▟
^[[38;2;255;80;30m  ▜▙   ▜▙ ▟▛   ▟▛ █ ▜▙   ▜▙ ▟▛  ▟▛
^[[38;2;255;90;30m      ▜▙  ▀▟▛   ▟▛  █  ▜▙   ▜▙▀  ▟▛
^[[38;2;255;100;30m        ▜▙      ▟▛   █  ▜▙     ▂▟▛
^[[38;2;255;90;30m        ▜▙    ▟▛  ▗▟█▙▖  ▜▙   ▂▟▛
^[[38;2;255;80;30m         ▜▙  ▟▛  ▟▛ █ ▜▙  ▜▙  ▟▛
^[[38;2;255;70;30m          ▜▙▟▛  ▟▛  █  ▜▙  ▜▙▟▛
^[[38;2;255;60;30m             ▜▛   ▜▙  █  ▟▛   ▜▛
^[[38;2;240;50;30m              ▜▙   ▜▙ █ ▟▛   ▟▛
^[[38;2;220;40;30m                ▜▙   ▜██▛   ▟▛
^[[38;2;200;35;30m                 ▜▙   ▜▛   ▟▛
^[[38;2;180;30;30m                   ▜▙      ▟▛
^[[38;2;160;25;30m                    ▜▙   ▂▟▛
^[[38;2;140;20;30m                     ▜▙  ▟▛
^[[38;2;120;15;30m                      ▜▙▟▛
^[[38;2;100;10;30m                        ▜▛

Original Image URL

No response

Checklist

• The ASCII art is smaller than 50x20 characters (W x H).
• The ASCII art includes color codes, or the color codes are available in os-release.
• The ASCII art has no internal padding (spaces at the start and/or end of lines).

[logandaddy12-dot]

Issue: Literal ANSI Sequence Rendering in Custom LogoThe Problem:When using custom TrueColor (24-bit) sequences (e.g., ^[[38;2;R;G;Bm) in a logo source file, Fastfetch is treating the caret-notation (^[) as literal ASCII characters rather than the ESC control character ($U+001B$).This causes two issues:Visual Noise: The raw escape codes are printed to the terminal instead of being interpreted as colors.Alignment Breakage: The terminal parser calculates the width of the line including the literal characters of the escape code. When the terminal eventually tries to render, it "collapses" those codes to zero-width, causing the ASCII art to shift left and lose symmetry.Proposed Solution/Feature Request:The logo parser should support a "raw" or "processed" mode that automatically converts literal escape shorthand (like \e[, \x1b[, or \u001b[) into the actual ESC control character before piping to the TTY.Currently, users have to manually "bake" the invisible escape character into .txt files using sed or printf, which makes the logo files difficult to edit or share without corruption. Supporting a standardized escape initiator in the logo source would ensure 24-bit color gradients work reliably across different terminal environments.