#120 bold fonts gone in 0.5.3


As of mrxvt 0.5.3, I can no longer make bold text using bash escape sequences. Here, as an example, is my PS1:

PS1='\[\033[01;33m\][\t]\[\033[01;31m\][\u:\w]\[\033[00m\] \$ '

I tried svn with the same results. This text was bold in 0.5.2 and prior.


Debug mode : no
Private string functions : no
Rarely used features : yes

Scroll features:
Keep scroll : yes
Scroll on selection : yes
Mouse wheel scroll : yes
Slip mouse wheel scroll : no
RXVT style scrollbar : yes
NeXT style scrollbar : yes
Xterm style scrollbar : yes
Plain style scrollbar : yes
SGI IRIX style scrollbar : yes
Half shadow scrollbar : yes

Logging features:
Support utmp records : yes
Support wtmp records : yes
Support lastlog records : yes
Support X session manager : yes
Use utempter library : no

Visual features:
Support line space : yes
24 bits color mode : no
256 color mode : yes
Blink cursor : yes
Blank pointer : yes
Color text shadow : no
Smart resize : no
Menu bar : no

Background features:
Background image : yes
XPM background image : yes
JPEG background image : yes
PNG background image : yes
Transparent background : yes
Background tinting : yes (XRender)

Multi-language and font features:
Freetype Font : no
X Input Method : no
Greek keyboard : no
CJK multichar language : no

System features:
TTY gid : yes
Backspace key : yes
Delete key : yes
Use fifo : yes
X resources : yes
X default resources : no
Swap screen : yes
Old selection : no

Terminal name : rxvt
Maximal profiles : 5
Maximal tabs : 15
Extra height% of active tab : 20
Radius% of tab corners : 100
Line space : 0
Internal border width : 0
External border width : 0
Saved lines in scroll : 100


  • GI

    GI - 2007-08-28

    Logged In: YES
    Originator: NO

    We added two new options controlling the display of bold fonts. --veryBold and --veryBright. I personally think it looks better to have bolded primary colors displayed with bright colors instead of the bold font, hence these options. But if you set both these options to true, you should get the old behaviour.

    In hindsight, we should have enabled them by default. Oh well :)

  • GI

    GI - 2007-08-28
    • status: open --> closed-invalid

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks