Skip to main content

Installing fonts and using it in Xresources

Drop the .otf/.ttf font file in ~/.local/share/fonts (or the deprecated ~/.fonts/)

Rehash fonts db using: fc-cache -f -v (or reboot)

Find the font family name by grepping for it like: fc-list -v | grep "Nerd font" | grep "family:"

My result was "DroidSansMono Nerd Font"

In ~/.Xresources, put in this line: xterm*faceName: xterm*faceName: DroidSansMono Nerd Font:size=16:antialias=true

And finally: xrdb ~/.Xresources

Comments

Post a Comment

Popular posts from this blog

Docker CE on openSUSE tumbleweed

Getting the docker community edition installed and running on openSUSE can be difficult because there are no official docs on how to do it for openSUSE, specifically the tumbleweed version of it. Here's what I did to make it work: Add the Virtualization:containers repo of openSUSE Tumbleweed and install docker as shown below. (This should install Docker CE) sudo zypper addrepo https://download.opensuse.org/repositories/Virtualization:containers/openSUSE_Tumbleweed/Virtualization:containers.repo sudo zypper refresh && sudo zypper install docker Disable the docker daemon that was started from systemd if any.  sudo sysctl stop docker Starting docker service using the bundled systemd config seems to be causing issues with some docker functions. I wasn't able to get to the root of the problem, but I found out that running the daemon manually seemed to fix the errors I had from having the docker started via systemd. Start containerd (and keep it running): sudo cont...
4 comments
moar!

Out of sync audio video on linux?

Couple of days back, I played around with pulseaudio modules, sources and sinks and all that stuff (Obviously not knowing what I was doing). Few days later, I noticed that video playback from youtube (or any audio visual content) started to become choppy and slow often to the point of audio getting out of sync very quickly. I wasn't sure what the cause of this problem was. I initially thought my CPU was stepping down due to the heat. But it turns out that it was my screwed up pulseaudio config. Doing `rm -rf ~/.config/pulse` followed by `pulseaudio -k` (kill the pulseaudio daemon) instantly fixed this issue. 
Post a Comment
moar!