Hope this helps otherwise, just reply (within 30 days) or contact me e.g. It *can* be installed to overwrite Fixed 9x18/18x18ko as well (the fixedmir.ed script patches the files to use the Fixed font names, and possibly other (compatibility) changes), but does not need to be (FixedMisc uses mirf16v8.bdf, mirf18fw.bdf, mirf18hw.bdf as names whereas Fixed uses 9x18.bdf, 18x18ko.bdf, and does not have a matching 8x16 VGA font). misc-fixed-medium-r-normal-ko-18-120-100-100-c-180-iso10646-1įixedMisc used the -ko- variant of 18x18 as base, but took some glyphs from the -ja- variant instead. The stock equivalents of these from Fixed are: (Also in MirBSD… in case anyone uses it.) If you install xfonts-base from above, the aliases mirhw, mirfw, mirvga (in this order hw=halfwidth, fw=fullwidth) will be predefined. There’s also an 8x16 VGA variant for e.g. The X long font descriptions for the font I mean (for -fn and -fw for xterm, for example) are: The 9x18/18x18 are not standard aliases, I just use them to describe the font sizes. is the easier way, it contains a replacement xfonts-base package with all the standard fonts (although not in the version in Debian, but in the latest one from XFree86® (which has fixes over X.org) plus fixes _from_ X.org plus fixes of my own), plus FixedMisc. bdf, but it takes much longer to load).įor Debian users. pcf for installation you can also install the. bdf (and then the usual bdftopcf from XFree86®/X.org to convert to. It lives in CVS at (ignore the 9x18/ subdirectory there for now, I never got around to finishing that idea), but needs bdfctool from to compile from. To the majority of the world of terminals nowadays, boldface means actual boldface, a change in font weight, not colour.ĭo not use it as if it were a colour change.I occasionally publish snapshots at but that’s been a while. Only the linux-16color terminal type in the terminfo database tries to set colours 8 to 15 that way, in fact. Ironically, the hardwiring that you, or the person who did that in your prompt, have chosen applies to a small minority of terminal types. Then it will work with many types of terminal and not just the one that you have hardwired. Generate them with tput setaf and tput setab and use command substitution to place the result into your PS1 shell variable. The other programs are not hardwiring control sequences, which is why they work. If you look carefully at your UXTerm screenshot you will see that that is exactly what UXTerm has in fact done, set a low-numbered colour and turned boldface on, just as your prompt asked. Your prompt is trying to set colours 8 to 15 by setting colours 0–7 instead, and turning on boldface (with SGR 1).(The rest of the gibberish specifies that it sets colours 16 and upwards in response to SGR 38:5 and SGR 48:5, with the faulty separators.) Your terminal sets colours 8 to 15 in response to SGR 90–97 and SGR 100–107, which is what all the gibberish in the setaf and setab actually does.It has hardcoded SGR control sequences for changing colour, and it has hardcoded the wrong ones, for another terminal type. Your prompt is not correct for your terminal type. UXTerm's infocmp, if it helps: Reconstructed via infocmp from file: /lib/terminfo/x/xterm-256colorĪm, bce, ccc, km, mc5i, mir, msgr, npc, xenl,Ĭolors#0x100, cols#80, it#8, lines#24, pairs#0x10000,Īcsc=``aaffggiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz%-%d%e38 5 %p1%d% m, ~/.alacritty.yml: # Colors (Solarized Light)īut they show completely different behaviours color-wise:īoth pass this test I've found: #!/usr/bin/env bash I'm using Solarized Light color theme for Alacritty and UXTerm. I don't quite understand XTerm's (UXTerm's in this case) behaviour regarding colors.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |