st terminal: disable bold/italic font

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite
1












enter image description here



I'm using st terminal and I can't get rid of bold text, my curent font support bold and apply this patch doesn't help: https://st.suckless.org/patches/xresources/
with st.bold_font: 0 in .Xresources



Howto disable completely bold font with st?










share|improve this question





















  • The patch doesn't attempt to do what you want.
    – Thomas Dickey
    Sep 28 at 8:00










  • I tried other patches st.suckless.org/patches/solarized/st-no_bold_colors-0.8.1.diff and st.suckless.org/patches/disable_bold_italic_fonts separately, don't change the bold text either.
    – Tuyen Pham
    Sep 28 at 8:22














up vote
1
down vote

favorite
1












enter image description here



I'm using st terminal and I can't get rid of bold text, my curent font support bold and apply this patch doesn't help: https://st.suckless.org/patches/xresources/
with st.bold_font: 0 in .Xresources



Howto disable completely bold font with st?










share|improve this question





















  • The patch doesn't attempt to do what you want.
    – Thomas Dickey
    Sep 28 at 8:00










  • I tried other patches st.suckless.org/patches/solarized/st-no_bold_colors-0.8.1.diff and st.suckless.org/patches/disable_bold_italic_fonts separately, don't change the bold text either.
    – Tuyen Pham
    Sep 28 at 8:22












up vote
1
down vote

favorite
1









up vote
1
down vote

favorite
1






1





enter image description here



I'm using st terminal and I can't get rid of bold text, my curent font support bold and apply this patch doesn't help: https://st.suckless.org/patches/xresources/
with st.bold_font: 0 in .Xresources



Howto disable completely bold font with st?










share|improve this question













enter image description here



I'm using st terminal and I can't get rid of bold text, my curent font support bold and apply this patch doesn't help: https://st.suckless.org/patches/xresources/
with st.bold_font: 0 in .Xresources



Howto disable completely bold font with st?







suckless-terminal






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Sep 28 at 7:16









Tuyen Pham

30510




30510











  • The patch doesn't attempt to do what you want.
    – Thomas Dickey
    Sep 28 at 8:00










  • I tried other patches st.suckless.org/patches/solarized/st-no_bold_colors-0.8.1.diff and st.suckless.org/patches/disable_bold_italic_fonts separately, don't change the bold text either.
    – Tuyen Pham
    Sep 28 at 8:22
















  • The patch doesn't attempt to do what you want.
    – Thomas Dickey
    Sep 28 at 8:00










  • I tried other patches st.suckless.org/patches/solarized/st-no_bold_colors-0.8.1.diff and st.suckless.org/patches/disable_bold_italic_fonts separately, don't change the bold text either.
    – Tuyen Pham
    Sep 28 at 8:22















The patch doesn't attempt to do what you want.
– Thomas Dickey
Sep 28 at 8:00




The patch doesn't attempt to do what you want.
– Thomas Dickey
Sep 28 at 8:00












I tried other patches st.suckless.org/patches/solarized/st-no_bold_colors-0.8.1.diff and st.suckless.org/patches/disable_bold_italic_fonts separately, don't change the bold text either.
– Tuyen Pham
Sep 28 at 8:22




I tried other patches st.suckless.org/patches/solarized/st-no_bold_colors-0.8.1.diff and st.suckless.org/patches/disable_bold_italic_fonts separately, don't change the bold text either.
– Tuyen Pham
Sep 28 at 8:22










1 Answer
1






active

oldest

votes

















up vote
1
down vote



accepted










Patch



Unfortunately no one has made a patch for the current version (v0.8.1).



Fork



If you don't want to change the source code, then you can try the fork xst which has the ability to disable bold fonts, but also includes other patches.



Fontconfig



Another option (more of a workaround) is to disable bold monospaced (or specific) fonts everywhere by creating a config file for Fontconfig, for example in $HOME/.config/fontconfig/fonts.conf, or add to your existing, the following:



<?xml version='1.0'?>
<!DOCTYPE fontconfig SYSTEM 'fonts.dtd'>
<fontconfig>
<match target="pattern">
<test qual="any" name="family">
<string>monospace</string>
</test>
<test name="weight" compare="more">
<const>medium</const>
</test>
<edit name="weight" mode="assign" binding="same">
<const>medium</const>
</edit>
</match>
</fontconfig>


If you add to an existing file, make sure to remove the first three lines and the last line.



This assumes that you have compiled st with something like:



static char *font = "monospace:size=13:antialias=true:autohint=true";


In the config.h. Also that you have defined the font you use somewhere in your fontconfig something like this:



<alias>
<family>monospace</family>
<prefer>
<family>Px437 IBM VGA8</family>
</prefer>
</alias>
<alias>
<family>Px437 IBM VGA8</family>
<default>
<family>monospace</family>
</default>
</alias>


Then run the program fc-cache. Note that this will disable the Xresource colors color8 through color15 in st, but the patches might have done that as well.



Fontconfig can be a very difficult thing to configure, and it is very easy to make it do something that was not intended. Therefore, to cover this fully, is beyond the scope of this answer.






share|improve this answer






















  • Thanks, I don't mind to apply a patch to current version of st 0.8.1 but I don't like idea of xst that just includes multiple patches. Why don't just contribute via create / update patches to upstream st?
    – Tuyen Pham
    Sep 29 at 6:40










  • @TuyenPham You will have to ask the developer, I assume there is a demand for such preconfigurations. I have edited the answer and added another possible solution.
    – Klorax
    Sep 29 at 16:06










  • Thanks again, I tried xst and this fork is more stable than st itself - I suffered X crash a lot when using browers with st and only with this fork zsh substring can be able to work properly on xst-256color, I'll use this fork.
    – Tuyen Pham
    Sep 29 at 16:26











  • X crash even with xst, my bad. Chromium caused X crash under my wm. Have no idea what caused.
    – Tuyen Pham
    Sep 29 at 18:03






  • 1




    @TuyenPham It should not matter, just that it is both defined in the config.h and in the fontconfig. I have edited the answer further, but fontconfig is very complex so you might have to mess around quite a bit. Also I prefer defining monospace in every application that uses such font, then define the actual font in fontconfig (like tha answer above). You could compile with a specific font in config.h and then do the bold fix just for that specific font, i.e., <string>PX437 IBM VGA8</string> above.
    – Klorax
    Sep 29 at 20:37











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f471996%2fst-terminal-disable-bold-italic-font%23new-answer', 'question_page');

);

Post as a guest






























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
1
down vote



accepted










Patch



Unfortunately no one has made a patch for the current version (v0.8.1).



Fork



If you don't want to change the source code, then you can try the fork xst which has the ability to disable bold fonts, but also includes other patches.



Fontconfig



Another option (more of a workaround) is to disable bold monospaced (or specific) fonts everywhere by creating a config file for Fontconfig, for example in $HOME/.config/fontconfig/fonts.conf, or add to your existing, the following:



<?xml version='1.0'?>
<!DOCTYPE fontconfig SYSTEM 'fonts.dtd'>
<fontconfig>
<match target="pattern">
<test qual="any" name="family">
<string>monospace</string>
</test>
<test name="weight" compare="more">
<const>medium</const>
</test>
<edit name="weight" mode="assign" binding="same">
<const>medium</const>
</edit>
</match>
</fontconfig>


If you add to an existing file, make sure to remove the first three lines and the last line.



This assumes that you have compiled st with something like:



static char *font = "monospace:size=13:antialias=true:autohint=true";


In the config.h. Also that you have defined the font you use somewhere in your fontconfig something like this:



<alias>
<family>monospace</family>
<prefer>
<family>Px437 IBM VGA8</family>
</prefer>
</alias>
<alias>
<family>Px437 IBM VGA8</family>
<default>
<family>monospace</family>
</default>
</alias>


Then run the program fc-cache. Note that this will disable the Xresource colors color8 through color15 in st, but the patches might have done that as well.



Fontconfig can be a very difficult thing to configure, and it is very easy to make it do something that was not intended. Therefore, to cover this fully, is beyond the scope of this answer.






share|improve this answer






















  • Thanks, I don't mind to apply a patch to current version of st 0.8.1 but I don't like idea of xst that just includes multiple patches. Why don't just contribute via create / update patches to upstream st?
    – Tuyen Pham
    Sep 29 at 6:40










  • @TuyenPham You will have to ask the developer, I assume there is a demand for such preconfigurations. I have edited the answer and added another possible solution.
    – Klorax
    Sep 29 at 16:06










  • Thanks again, I tried xst and this fork is more stable than st itself - I suffered X crash a lot when using browers with st and only with this fork zsh substring can be able to work properly on xst-256color, I'll use this fork.
    – Tuyen Pham
    Sep 29 at 16:26











  • X crash even with xst, my bad. Chromium caused X crash under my wm. Have no idea what caused.
    – Tuyen Pham
    Sep 29 at 18:03






  • 1




    @TuyenPham It should not matter, just that it is both defined in the config.h and in the fontconfig. I have edited the answer further, but fontconfig is very complex so you might have to mess around quite a bit. Also I prefer defining monospace in every application that uses such font, then define the actual font in fontconfig (like tha answer above). You could compile with a specific font in config.h and then do the bold fix just for that specific font, i.e., <string>PX437 IBM VGA8</string> above.
    – Klorax
    Sep 29 at 20:37















up vote
1
down vote



accepted










Patch



Unfortunately no one has made a patch for the current version (v0.8.1).



Fork



If you don't want to change the source code, then you can try the fork xst which has the ability to disable bold fonts, but also includes other patches.



Fontconfig



Another option (more of a workaround) is to disable bold monospaced (or specific) fonts everywhere by creating a config file for Fontconfig, for example in $HOME/.config/fontconfig/fonts.conf, or add to your existing, the following:



<?xml version='1.0'?>
<!DOCTYPE fontconfig SYSTEM 'fonts.dtd'>
<fontconfig>
<match target="pattern">
<test qual="any" name="family">
<string>monospace</string>
</test>
<test name="weight" compare="more">
<const>medium</const>
</test>
<edit name="weight" mode="assign" binding="same">
<const>medium</const>
</edit>
</match>
</fontconfig>


If you add to an existing file, make sure to remove the first three lines and the last line.



This assumes that you have compiled st with something like:



static char *font = "monospace:size=13:antialias=true:autohint=true";


In the config.h. Also that you have defined the font you use somewhere in your fontconfig something like this:



<alias>
<family>monospace</family>
<prefer>
<family>Px437 IBM VGA8</family>
</prefer>
</alias>
<alias>
<family>Px437 IBM VGA8</family>
<default>
<family>monospace</family>
</default>
</alias>


Then run the program fc-cache. Note that this will disable the Xresource colors color8 through color15 in st, but the patches might have done that as well.



Fontconfig can be a very difficult thing to configure, and it is very easy to make it do something that was not intended. Therefore, to cover this fully, is beyond the scope of this answer.






share|improve this answer






















  • Thanks, I don't mind to apply a patch to current version of st 0.8.1 but I don't like idea of xst that just includes multiple patches. Why don't just contribute via create / update patches to upstream st?
    – Tuyen Pham
    Sep 29 at 6:40










  • @TuyenPham You will have to ask the developer, I assume there is a demand for such preconfigurations. I have edited the answer and added another possible solution.
    – Klorax
    Sep 29 at 16:06










  • Thanks again, I tried xst and this fork is more stable than st itself - I suffered X crash a lot when using browers with st and only with this fork zsh substring can be able to work properly on xst-256color, I'll use this fork.
    – Tuyen Pham
    Sep 29 at 16:26











  • X crash even with xst, my bad. Chromium caused X crash under my wm. Have no idea what caused.
    – Tuyen Pham
    Sep 29 at 18:03






  • 1




    @TuyenPham It should not matter, just that it is both defined in the config.h and in the fontconfig. I have edited the answer further, but fontconfig is very complex so you might have to mess around quite a bit. Also I prefer defining monospace in every application that uses such font, then define the actual font in fontconfig (like tha answer above). You could compile with a specific font in config.h and then do the bold fix just for that specific font, i.e., <string>PX437 IBM VGA8</string> above.
    – Klorax
    Sep 29 at 20:37













up vote
1
down vote



accepted







up vote
1
down vote



accepted






Patch



Unfortunately no one has made a patch for the current version (v0.8.1).



Fork



If you don't want to change the source code, then you can try the fork xst which has the ability to disable bold fonts, but also includes other patches.



Fontconfig



Another option (more of a workaround) is to disable bold monospaced (or specific) fonts everywhere by creating a config file for Fontconfig, for example in $HOME/.config/fontconfig/fonts.conf, or add to your existing, the following:



<?xml version='1.0'?>
<!DOCTYPE fontconfig SYSTEM 'fonts.dtd'>
<fontconfig>
<match target="pattern">
<test qual="any" name="family">
<string>monospace</string>
</test>
<test name="weight" compare="more">
<const>medium</const>
</test>
<edit name="weight" mode="assign" binding="same">
<const>medium</const>
</edit>
</match>
</fontconfig>


If you add to an existing file, make sure to remove the first three lines and the last line.



This assumes that you have compiled st with something like:



static char *font = "monospace:size=13:antialias=true:autohint=true";


In the config.h. Also that you have defined the font you use somewhere in your fontconfig something like this:



<alias>
<family>monospace</family>
<prefer>
<family>Px437 IBM VGA8</family>
</prefer>
</alias>
<alias>
<family>Px437 IBM VGA8</family>
<default>
<family>monospace</family>
</default>
</alias>


Then run the program fc-cache. Note that this will disable the Xresource colors color8 through color15 in st, but the patches might have done that as well.



Fontconfig can be a very difficult thing to configure, and it is very easy to make it do something that was not intended. Therefore, to cover this fully, is beyond the scope of this answer.






share|improve this answer














Patch



Unfortunately no one has made a patch for the current version (v0.8.1).



Fork



If you don't want to change the source code, then you can try the fork xst which has the ability to disable bold fonts, but also includes other patches.



Fontconfig



Another option (more of a workaround) is to disable bold monospaced (or specific) fonts everywhere by creating a config file for Fontconfig, for example in $HOME/.config/fontconfig/fonts.conf, or add to your existing, the following:



<?xml version='1.0'?>
<!DOCTYPE fontconfig SYSTEM 'fonts.dtd'>
<fontconfig>
<match target="pattern">
<test qual="any" name="family">
<string>monospace</string>
</test>
<test name="weight" compare="more">
<const>medium</const>
</test>
<edit name="weight" mode="assign" binding="same">
<const>medium</const>
</edit>
</match>
</fontconfig>


If you add to an existing file, make sure to remove the first three lines and the last line.



This assumes that you have compiled st with something like:



static char *font = "monospace:size=13:antialias=true:autohint=true";


In the config.h. Also that you have defined the font you use somewhere in your fontconfig something like this:



<alias>
<family>monospace</family>
<prefer>
<family>Px437 IBM VGA8</family>
</prefer>
</alias>
<alias>
<family>Px437 IBM VGA8</family>
<default>
<family>monospace</family>
</default>
</alias>


Then run the program fc-cache. Note that this will disable the Xresource colors color8 through color15 in st, but the patches might have done that as well.



Fontconfig can be a very difficult thing to configure, and it is very easy to make it do something that was not intended. Therefore, to cover this fully, is beyond the scope of this answer.







share|improve this answer














share|improve this answer



share|improve this answer








edited Sep 29 at 20:35

























answered Sep 28 at 13:12









Klorax

2615




2615











  • Thanks, I don't mind to apply a patch to current version of st 0.8.1 but I don't like idea of xst that just includes multiple patches. Why don't just contribute via create / update patches to upstream st?
    – Tuyen Pham
    Sep 29 at 6:40










  • @TuyenPham You will have to ask the developer, I assume there is a demand for such preconfigurations. I have edited the answer and added another possible solution.
    – Klorax
    Sep 29 at 16:06










  • Thanks again, I tried xst and this fork is more stable than st itself - I suffered X crash a lot when using browers with st and only with this fork zsh substring can be able to work properly on xst-256color, I'll use this fork.
    – Tuyen Pham
    Sep 29 at 16:26











  • X crash even with xst, my bad. Chromium caused X crash under my wm. Have no idea what caused.
    – Tuyen Pham
    Sep 29 at 18:03






  • 1




    @TuyenPham It should not matter, just that it is both defined in the config.h and in the fontconfig. I have edited the answer further, but fontconfig is very complex so you might have to mess around quite a bit. Also I prefer defining monospace in every application that uses such font, then define the actual font in fontconfig (like tha answer above). You could compile with a specific font in config.h and then do the bold fix just for that specific font, i.e., <string>PX437 IBM VGA8</string> above.
    – Klorax
    Sep 29 at 20:37

















  • Thanks, I don't mind to apply a patch to current version of st 0.8.1 but I don't like idea of xst that just includes multiple patches. Why don't just contribute via create / update patches to upstream st?
    – Tuyen Pham
    Sep 29 at 6:40










  • @TuyenPham You will have to ask the developer, I assume there is a demand for such preconfigurations. I have edited the answer and added another possible solution.
    – Klorax
    Sep 29 at 16:06










  • Thanks again, I tried xst and this fork is more stable than st itself - I suffered X crash a lot when using browers with st and only with this fork zsh substring can be able to work properly on xst-256color, I'll use this fork.
    – Tuyen Pham
    Sep 29 at 16:26











  • X crash even with xst, my bad. Chromium caused X crash under my wm. Have no idea what caused.
    – Tuyen Pham
    Sep 29 at 18:03






  • 1




    @TuyenPham It should not matter, just that it is both defined in the config.h and in the fontconfig. I have edited the answer further, but fontconfig is very complex so you might have to mess around quite a bit. Also I prefer defining monospace in every application that uses such font, then define the actual font in fontconfig (like tha answer above). You could compile with a specific font in config.h and then do the bold fix just for that specific font, i.e., <string>PX437 IBM VGA8</string> above.
    – Klorax
    Sep 29 at 20:37
















Thanks, I don't mind to apply a patch to current version of st 0.8.1 but I don't like idea of xst that just includes multiple patches. Why don't just contribute via create / update patches to upstream st?
– Tuyen Pham
Sep 29 at 6:40




Thanks, I don't mind to apply a patch to current version of st 0.8.1 but I don't like idea of xst that just includes multiple patches. Why don't just contribute via create / update patches to upstream st?
– Tuyen Pham
Sep 29 at 6:40












@TuyenPham You will have to ask the developer, I assume there is a demand for such preconfigurations. I have edited the answer and added another possible solution.
– Klorax
Sep 29 at 16:06




@TuyenPham You will have to ask the developer, I assume there is a demand for such preconfigurations. I have edited the answer and added another possible solution.
– Klorax
Sep 29 at 16:06












Thanks again, I tried xst and this fork is more stable than st itself - I suffered X crash a lot when using browers with st and only with this fork zsh substring can be able to work properly on xst-256color, I'll use this fork.
– Tuyen Pham
Sep 29 at 16:26





Thanks again, I tried xst and this fork is more stable than st itself - I suffered X crash a lot when using browers with st and only with this fork zsh substring can be able to work properly on xst-256color, I'll use this fork.
– Tuyen Pham
Sep 29 at 16:26













X crash even with xst, my bad. Chromium caused X crash under my wm. Have no idea what caused.
– Tuyen Pham
Sep 29 at 18:03




X crash even with xst, my bad. Chromium caused X crash under my wm. Have no idea what caused.
– Tuyen Pham
Sep 29 at 18:03




1




1




@TuyenPham It should not matter, just that it is both defined in the config.h and in the fontconfig. I have edited the answer further, but fontconfig is very complex so you might have to mess around quite a bit. Also I prefer defining monospace in every application that uses such font, then define the actual font in fontconfig (like tha answer above). You could compile with a specific font in config.h and then do the bold fix just for that specific font, i.e., <string>PX437 IBM VGA8</string> above.
– Klorax
Sep 29 at 20:37





@TuyenPham It should not matter, just that it is both defined in the config.h and in the fontconfig. I have edited the answer further, but fontconfig is very complex so you might have to mess around quite a bit. Also I prefer defining monospace in every application that uses such font, then define the actual font in fontconfig (like tha answer above). You could compile with a specific font in config.h and then do the bold fix just for that specific font, i.e., <string>PX437 IBM VGA8</string> above.
– Klorax
Sep 29 at 20:37


















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f471996%2fst-terminal-disable-bold-italic-font%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

How to check contact read email or not when send email to Individual?

Bahrain

Postfix configuration issue with fips on centos 7; mailgun relay