XTerm*faceName in .Xresources are not reflected












0















I've tried customizing zsh's prompt with change the font but during it, xterm become not to reflect the XTerm*faceName in~/.Xresources.



Here is my dot files:




~/.xinitrc




#!/bin/sh

# /etc/X11/xinit/xinitrc
#
# global xinitrc file, used by all X sessions started by xinit(startx)

# invoke global X session script
. /etc/X11/Xsession

xrdb -merge $HOME/.Xresources
exec awesome



~/.Xresources




XTerm*termName: xterm-256color
XTerm*locale: true
XTerm*selectToClipboard: true
XTerm*faceName: Shure Tech Mono Nerd Font Complete
XTerm*faceSize: 12

!TomorrowNightEighties
#define t_background #2d2d2d
#define t_current_line #393939
#define t_selection #515151
#define t_foreground #cccccc
#define t_comment #999999
#define t_red #f2777a
#define t_orange #f99157
#define t_yellow #ffcc66
#define t_green #99cc99
#define t_aqua #66cccc
#define t_blue #6699cc
#define t_purple #cc99cc


*.foreground: t_foreground
*.background: t_background
*.cursorColor: #aeafad

! Black / Grey
*.color0: #000000
*.color8: #666666

! Red / Bright Red
*.color1: t_red
*.color9: #FF3334

! Green + Bright Green
*.color2: t_green
*.color10: #9ec400

! Yellow (Orange) + Bright Yellow (Yellow)
*.color3: t_orange
*.color11: t_yellow

! Blue + Bright Blue
*.color4: t_blue
*.color12: t_blue

! Magenta (Purple) + Bright Magenta
*.color5: t_purple
*.color13: #b777e0

! Cyan (Aqua) + Bright Cyan
*.color6: t_aqua
*.color14: #54ced6

! Light Grey (Selection) + White (Current Line)
*.color7: t_selection
*.color15: t_current_line


Here is the screenshot:



The screenshot: left is the true font I want but actually show as right



Although I'd already restart vm (= restart X), the font was still old one although other elements like theme were reflected properly.



Other information:



Ubuntu 18.04 on vmware



awesomewm as a window manager



zsh as shell










share|improve this question

























  • Looking at the manpage, faceName requires FreeType support compiled into xterm. No idea if your version of xterm has that. Does font etc. work (with the usual bitmap fonts)?

    – dirkt
    Dec 7 '18 at 11:44











  • I tried writing "XTerm.font = Shure Tech.." and restarting, but the result is the same. Also, I tried xterm -fa "Shure Tech..." and xterm -fn "Shure Tech..." and both are same, old font was shown.

    – Szkieletor
    Dec 7 '18 at 13:02













  • If "Shure Tech ..." isn't a bitmap font, this won't work. Run xfontsel or xlsfonts, pick a standard font that's installed, e.g. -misc-fixed-medium-*, try *.font: misc-fixed-medium-* or xterm -fn 'misc-fixed-medium-*' (but use a proper size). This won't tell you if faceName works, if will tell you only whether you can set fonts in principle. Next step is to use FreeType tools to list your installed fonts, and try one of those with faceName.

    – dirkt
    Dec 7 '18 at 13:28
















0















I've tried customizing zsh's prompt with change the font but during it, xterm become not to reflect the XTerm*faceName in~/.Xresources.



Here is my dot files:




~/.xinitrc




#!/bin/sh

# /etc/X11/xinit/xinitrc
#
# global xinitrc file, used by all X sessions started by xinit(startx)

# invoke global X session script
. /etc/X11/Xsession

xrdb -merge $HOME/.Xresources
exec awesome



~/.Xresources




XTerm*termName: xterm-256color
XTerm*locale: true
XTerm*selectToClipboard: true
XTerm*faceName: Shure Tech Mono Nerd Font Complete
XTerm*faceSize: 12

!TomorrowNightEighties
#define t_background #2d2d2d
#define t_current_line #393939
#define t_selection #515151
#define t_foreground #cccccc
#define t_comment #999999
#define t_red #f2777a
#define t_orange #f99157
#define t_yellow #ffcc66
#define t_green #99cc99
#define t_aqua #66cccc
#define t_blue #6699cc
#define t_purple #cc99cc


*.foreground: t_foreground
*.background: t_background
*.cursorColor: #aeafad

! Black / Grey
*.color0: #000000
*.color8: #666666

! Red / Bright Red
*.color1: t_red
*.color9: #FF3334

! Green + Bright Green
*.color2: t_green
*.color10: #9ec400

! Yellow (Orange) + Bright Yellow (Yellow)
*.color3: t_orange
*.color11: t_yellow

! Blue + Bright Blue
*.color4: t_blue
*.color12: t_blue

! Magenta (Purple) + Bright Magenta
*.color5: t_purple
*.color13: #b777e0

! Cyan (Aqua) + Bright Cyan
*.color6: t_aqua
*.color14: #54ced6

! Light Grey (Selection) + White (Current Line)
*.color7: t_selection
*.color15: t_current_line


Here is the screenshot:



The screenshot: left is the true font I want but actually show as right



Although I'd already restart vm (= restart X), the font was still old one although other elements like theme were reflected properly.



Other information:



Ubuntu 18.04 on vmware



awesomewm as a window manager



zsh as shell










share|improve this question

























  • Looking at the manpage, faceName requires FreeType support compiled into xterm. No idea if your version of xterm has that. Does font etc. work (with the usual bitmap fonts)?

    – dirkt
    Dec 7 '18 at 11:44











  • I tried writing "XTerm.font = Shure Tech.." and restarting, but the result is the same. Also, I tried xterm -fa "Shure Tech..." and xterm -fn "Shure Tech..." and both are same, old font was shown.

    – Szkieletor
    Dec 7 '18 at 13:02













  • If "Shure Tech ..." isn't a bitmap font, this won't work. Run xfontsel or xlsfonts, pick a standard font that's installed, e.g. -misc-fixed-medium-*, try *.font: misc-fixed-medium-* or xterm -fn 'misc-fixed-medium-*' (but use a proper size). This won't tell you if faceName works, if will tell you only whether you can set fonts in principle. Next step is to use FreeType tools to list your installed fonts, and try one of those with faceName.

    – dirkt
    Dec 7 '18 at 13:28














0












0








0








I've tried customizing zsh's prompt with change the font but during it, xterm become not to reflect the XTerm*faceName in~/.Xresources.



Here is my dot files:




~/.xinitrc




#!/bin/sh

# /etc/X11/xinit/xinitrc
#
# global xinitrc file, used by all X sessions started by xinit(startx)

# invoke global X session script
. /etc/X11/Xsession

xrdb -merge $HOME/.Xresources
exec awesome



~/.Xresources




XTerm*termName: xterm-256color
XTerm*locale: true
XTerm*selectToClipboard: true
XTerm*faceName: Shure Tech Mono Nerd Font Complete
XTerm*faceSize: 12

!TomorrowNightEighties
#define t_background #2d2d2d
#define t_current_line #393939
#define t_selection #515151
#define t_foreground #cccccc
#define t_comment #999999
#define t_red #f2777a
#define t_orange #f99157
#define t_yellow #ffcc66
#define t_green #99cc99
#define t_aqua #66cccc
#define t_blue #6699cc
#define t_purple #cc99cc


*.foreground: t_foreground
*.background: t_background
*.cursorColor: #aeafad

! Black / Grey
*.color0: #000000
*.color8: #666666

! Red / Bright Red
*.color1: t_red
*.color9: #FF3334

! Green + Bright Green
*.color2: t_green
*.color10: #9ec400

! Yellow (Orange) + Bright Yellow (Yellow)
*.color3: t_orange
*.color11: t_yellow

! Blue + Bright Blue
*.color4: t_blue
*.color12: t_blue

! Magenta (Purple) + Bright Magenta
*.color5: t_purple
*.color13: #b777e0

! Cyan (Aqua) + Bright Cyan
*.color6: t_aqua
*.color14: #54ced6

! Light Grey (Selection) + White (Current Line)
*.color7: t_selection
*.color15: t_current_line


Here is the screenshot:



The screenshot: left is the true font I want but actually show as right



Although I'd already restart vm (= restart X), the font was still old one although other elements like theme were reflected properly.



Other information:



Ubuntu 18.04 on vmware



awesomewm as a window manager



zsh as shell










share|improve this question
















I've tried customizing zsh's prompt with change the font but during it, xterm become not to reflect the XTerm*faceName in~/.Xresources.



Here is my dot files:




~/.xinitrc




#!/bin/sh

# /etc/X11/xinit/xinitrc
#
# global xinitrc file, used by all X sessions started by xinit(startx)

# invoke global X session script
. /etc/X11/Xsession

xrdb -merge $HOME/.Xresources
exec awesome



~/.Xresources




XTerm*termName: xterm-256color
XTerm*locale: true
XTerm*selectToClipboard: true
XTerm*faceName: Shure Tech Mono Nerd Font Complete
XTerm*faceSize: 12

!TomorrowNightEighties
#define t_background #2d2d2d
#define t_current_line #393939
#define t_selection #515151
#define t_foreground #cccccc
#define t_comment #999999
#define t_red #f2777a
#define t_orange #f99157
#define t_yellow #ffcc66
#define t_green #99cc99
#define t_aqua #66cccc
#define t_blue #6699cc
#define t_purple #cc99cc


*.foreground: t_foreground
*.background: t_background
*.cursorColor: #aeafad

! Black / Grey
*.color0: #000000
*.color8: #666666

! Red / Bright Red
*.color1: t_red
*.color9: #FF3334

! Green + Bright Green
*.color2: t_green
*.color10: #9ec400

! Yellow (Orange) + Bright Yellow (Yellow)
*.color3: t_orange
*.color11: t_yellow

! Blue + Bright Blue
*.color4: t_blue
*.color12: t_blue

! Magenta (Purple) + Bright Magenta
*.color5: t_purple
*.color13: #b777e0

! Cyan (Aqua) + Bright Cyan
*.color6: t_aqua
*.color14: #54ced6

! Light Grey (Selection) + White (Current Line)
*.color7: t_selection
*.color15: t_current_line


Here is the screenshot:



The screenshot: left is the true font I want but actually show as right



Although I'd already restart vm (= restart X), the font was still old one although other elements like theme were reflected properly.



Other information:



Ubuntu 18.04 on vmware



awesomewm as a window manager



zsh as shell







xorg xterm fontconfig x-resources






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 7 '18 at 21:40









Thomas Dickey

52.5k596167




52.5k596167










asked Dec 7 '18 at 11:16









SzkieletorSzkieletor

32




32













  • Looking at the manpage, faceName requires FreeType support compiled into xterm. No idea if your version of xterm has that. Does font etc. work (with the usual bitmap fonts)?

    – dirkt
    Dec 7 '18 at 11:44











  • I tried writing "XTerm.font = Shure Tech.." and restarting, but the result is the same. Also, I tried xterm -fa "Shure Tech..." and xterm -fn "Shure Tech..." and both are same, old font was shown.

    – Szkieletor
    Dec 7 '18 at 13:02













  • If "Shure Tech ..." isn't a bitmap font, this won't work. Run xfontsel or xlsfonts, pick a standard font that's installed, e.g. -misc-fixed-medium-*, try *.font: misc-fixed-medium-* or xterm -fn 'misc-fixed-medium-*' (but use a proper size). This won't tell you if faceName works, if will tell you only whether you can set fonts in principle. Next step is to use FreeType tools to list your installed fonts, and try one of those with faceName.

    – dirkt
    Dec 7 '18 at 13:28



















  • Looking at the manpage, faceName requires FreeType support compiled into xterm. No idea if your version of xterm has that. Does font etc. work (with the usual bitmap fonts)?

    – dirkt
    Dec 7 '18 at 11:44











  • I tried writing "XTerm.font = Shure Tech.." and restarting, but the result is the same. Also, I tried xterm -fa "Shure Tech..." and xterm -fn "Shure Tech..." and both are same, old font was shown.

    – Szkieletor
    Dec 7 '18 at 13:02













  • If "Shure Tech ..." isn't a bitmap font, this won't work. Run xfontsel or xlsfonts, pick a standard font that's installed, e.g. -misc-fixed-medium-*, try *.font: misc-fixed-medium-* or xterm -fn 'misc-fixed-medium-*' (but use a proper size). This won't tell you if faceName works, if will tell you only whether you can set fonts in principle. Next step is to use FreeType tools to list your installed fonts, and try one of those with faceName.

    – dirkt
    Dec 7 '18 at 13:28

















Looking at the manpage, faceName requires FreeType support compiled into xterm. No idea if your version of xterm has that. Does font etc. work (with the usual bitmap fonts)?

– dirkt
Dec 7 '18 at 11:44





Looking at the manpage, faceName requires FreeType support compiled into xterm. No idea if your version of xterm has that. Does font etc. work (with the usual bitmap fonts)?

– dirkt
Dec 7 '18 at 11:44













I tried writing "XTerm.font = Shure Tech.." and restarting, but the result is the same. Also, I tried xterm -fa "Shure Tech..." and xterm -fn "Shure Tech..." and both are same, old font was shown.

– Szkieletor
Dec 7 '18 at 13:02







I tried writing "XTerm.font = Shure Tech.." and restarting, but the result is the same. Also, I tried xterm -fa "Shure Tech..." and xterm -fn "Shure Tech..." and both are same, old font was shown.

– Szkieletor
Dec 7 '18 at 13:02















If "Shure Tech ..." isn't a bitmap font, this won't work. Run xfontsel or xlsfonts, pick a standard font that's installed, e.g. -misc-fixed-medium-*, try *.font: misc-fixed-medium-* or xterm -fn 'misc-fixed-medium-*' (but use a proper size). This won't tell you if faceName works, if will tell you only whether you can set fonts in principle. Next step is to use FreeType tools to list your installed fonts, and try one of those with faceName.

– dirkt
Dec 7 '18 at 13:28





If "Shure Tech ..." isn't a bitmap font, this won't work. Run xfontsel or xlsfonts, pick a standard font that's installed, e.g. -misc-fixed-medium-*, try *.font: misc-fixed-medium-* or xterm -fn 'misc-fixed-medium-*' (but use a proper size). This won't tell you if faceName works, if will tell you only whether you can set fonts in principle. Next step is to use FreeType tools to list your installed fonts, and try one of those with faceName.

– dirkt
Dec 7 '18 at 13:28










2 Answers
2






active

oldest

votes


















1














The relevant font family name is ShureTechMono NF, which you can find using fc-list. Here is a screenshot.
xterm using ShureTechMono NF



The fc-list manual page suggests this command (: matches everything, the family parameter shows the face-family used by xterm):



fc-list : family


The xterm manual page entry for faceName also gives an example using fc-list:



fc-list :scalable=true:spacing=mono: family





share|improve this answer


























  • This, fc-list : family works for me. The problem occured by using fc-list : file | grep "Shure" = Shure Tech Mono... but fc-list : family | grep "Shure" suggests ShureTechMono... (=no space between these three). After I follow it, the font get changed (I need Nerd Font in order to use plugin).

    – Szkieletor
    Dec 8 '18 at 4:18





















0














Have you tried using the -fn parameter, and entering the font name using Pango notation e.g. ShureTechMono Nerd Font Regular:px=11



I've done it this way, with a different font, trial-and-error style, before I made the final entry in .Xresources. In this example, I would not use "Complete" but "Regular" as shown explicitly in the pic.





share








New contributor




a purugganan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















    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',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    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%2f486562%2fxtermfacename-in-xresources-are-not-reflected%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    The relevant font family name is ShureTechMono NF, which you can find using fc-list. Here is a screenshot.
    xterm using ShureTechMono NF



    The fc-list manual page suggests this command (: matches everything, the family parameter shows the face-family used by xterm):



    fc-list : family


    The xterm manual page entry for faceName also gives an example using fc-list:



    fc-list :scalable=true:spacing=mono: family





    share|improve this answer


























    • This, fc-list : family works for me. The problem occured by using fc-list : file | grep "Shure" = Shure Tech Mono... but fc-list : family | grep "Shure" suggests ShureTechMono... (=no space between these three). After I follow it, the font get changed (I need Nerd Font in order to use plugin).

      – Szkieletor
      Dec 8 '18 at 4:18


















    1














    The relevant font family name is ShureTechMono NF, which you can find using fc-list. Here is a screenshot.
    xterm using ShureTechMono NF



    The fc-list manual page suggests this command (: matches everything, the family parameter shows the face-family used by xterm):



    fc-list : family


    The xterm manual page entry for faceName also gives an example using fc-list:



    fc-list :scalable=true:spacing=mono: family





    share|improve this answer


























    • This, fc-list : family works for me. The problem occured by using fc-list : file | grep "Shure" = Shure Tech Mono... but fc-list : family | grep "Shure" suggests ShureTechMono... (=no space between these three). After I follow it, the font get changed (I need Nerd Font in order to use plugin).

      – Szkieletor
      Dec 8 '18 at 4:18
















    1












    1








    1







    The relevant font family name is ShureTechMono NF, which you can find using fc-list. Here is a screenshot.
    xterm using ShureTechMono NF



    The fc-list manual page suggests this command (: matches everything, the family parameter shows the face-family used by xterm):



    fc-list : family


    The xterm manual page entry for faceName also gives an example using fc-list:



    fc-list :scalable=true:spacing=mono: family





    share|improve this answer















    The relevant font family name is ShureTechMono NF, which you can find using fc-list. Here is a screenshot.
    xterm using ShureTechMono NF



    The fc-list manual page suggests this command (: matches everything, the family parameter shows the face-family used by xterm):



    fc-list : family


    The xterm manual page entry for faceName also gives an example using fc-list:



    fc-list :scalable=true:spacing=mono: family






    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Dec 7 '18 at 21:31

























    answered Dec 7 '18 at 21:21









    Thomas DickeyThomas Dickey

    52.5k596167




    52.5k596167













    • This, fc-list : family works for me. The problem occured by using fc-list : file | grep "Shure" = Shure Tech Mono... but fc-list : family | grep "Shure" suggests ShureTechMono... (=no space between these three). After I follow it, the font get changed (I need Nerd Font in order to use plugin).

      – Szkieletor
      Dec 8 '18 at 4:18





















    • This, fc-list : family works for me. The problem occured by using fc-list : file | grep "Shure" = Shure Tech Mono... but fc-list : family | grep "Shure" suggests ShureTechMono... (=no space between these three). After I follow it, the font get changed (I need Nerd Font in order to use plugin).

      – Szkieletor
      Dec 8 '18 at 4:18



















    This, fc-list : family works for me. The problem occured by using fc-list : file | grep "Shure" = Shure Tech Mono... but fc-list : family | grep "Shure" suggests ShureTechMono... (=no space between these three). After I follow it, the font get changed (I need Nerd Font in order to use plugin).

    – Szkieletor
    Dec 8 '18 at 4:18







    This, fc-list : family works for me. The problem occured by using fc-list : file | grep "Shure" = Shure Tech Mono... but fc-list : family | grep "Shure" suggests ShureTechMono... (=no space between these three). After I follow it, the font get changed (I need Nerd Font in order to use plugin).

    – Szkieletor
    Dec 8 '18 at 4:18















    0














    Have you tried using the -fn parameter, and entering the font name using Pango notation e.g. ShureTechMono Nerd Font Regular:px=11



    I've done it this way, with a different font, trial-and-error style, before I made the final entry in .Xresources. In this example, I would not use "Complete" but "Regular" as shown explicitly in the pic.





    share








    New contributor




    a purugganan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.

























      0














      Have you tried using the -fn parameter, and entering the font name using Pango notation e.g. ShureTechMono Nerd Font Regular:px=11



      I've done it this way, with a different font, trial-and-error style, before I made the final entry in .Xresources. In this example, I would not use "Complete" but "Regular" as shown explicitly in the pic.





      share








      New contributor




      a purugganan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.























        0












        0








        0







        Have you tried using the -fn parameter, and entering the font name using Pango notation e.g. ShureTechMono Nerd Font Regular:px=11



        I've done it this way, with a different font, trial-and-error style, before I made the final entry in .Xresources. In this example, I would not use "Complete" but "Regular" as shown explicitly in the pic.





        share








        New contributor




        a purugganan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.










        Have you tried using the -fn parameter, and entering the font name using Pango notation e.g. ShureTechMono Nerd Font Regular:px=11



        I've done it this way, with a different font, trial-and-error style, before I made the final entry in .Xresources. In this example, I would not use "Complete" but "Regular" as shown explicitly in the pic.






        share








        New contributor




        a purugganan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.








        share


        share






        New contributor




        a purugganan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        answered 2 mins ago









        a purugganana purugganan

        1




        1




        New contributor




        a purugganan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





        New contributor





        a purugganan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        a purugganan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f486562%2fxtermfacename-in-xresources-are-not-reflected%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Loup dans la culture

            How to solve the problem of ntp “Unable to contact time server” from KDE?

            ASUS Zenbook UX433/UX333 — Configure Touchpad-embedded numpad on Linux