dotfiles/.config/alacritty/alacritty.yml

565 lines
16 KiB
YAML
Raw Normal View History

Added Alacritty config and TERMINAL variable. Now I know Thomas is gonna get really pissy that I'm not using st, but frankly I don't give a shit what he thinks. What Thomas doesn't realise is that his way is not the best way. There are no best ways, just better ways. Sure, st is a good terminal, but I'm literally using Alacritty to type this message, and I like it. It is easy to configure and has GPU acceleration which makes it fast enough to literally watch a 360p video in text mode (possibly more, didn't test much since it already wiped st off the face of the planet). "aLAcRitTY is bLOaT" shut. the. fuck. up. If you cared about bloat that much you'd be using Artix, or better yet, NixOS. Instead, you're using a distro that literally stores 2 copies of every package you download and the 20 billion dependencies that come with it. You regularly bitch about how many dependencies KDE has but you haven't stopped to look at your own dependency clusterfuck. KDE is a perfectly fine desktop with plenty of features built in fully configured for your enjoyment (if you couldn't tell from my dotfiles its not my favorite, but I'll definitely admit to using KDE when I'm feeling lazy on a new install). You're probably going to say that its bloat because of that, but you clearly don't give a shit because you're still on vanilla Arch. Part of the Linux experience is being able to pick and choose your own experience. Maybe some don't want to use a tiling window manager. Sure, its more efficient once you get to know it, but not everyone is capable of learning the drastically different workflow that comes with TWMs/DWMs. Maybe they don't have the days, possibly weeks to setup everything to a usable state. Maybe they just want a computer that works. Now, I do get pretty pissed if you complain about problems that come with your choice of Linux lifestyle and A. Don't do anything to address them or B. Blame something else. Ex. Clay regularly complains about "Wine crashes all the time and has poor compatability". This was probably true back in Wine 2.0 when Clay was probably not even alive, but times have changed. Furthermore, I come to find out that the problems he is having either exist on Windows (ex. Into the Breach maximize button being useless) or are because of his WM (he uses Linux Mint Cinnamon btw). What I'm trying to say is, Thomas, be more open. Just because someone uses KDE doesn't mean that they're not good enough to setup i3. And to anyone else reading this, find what works best for you. I'm not saying to completely ignore what other people prefer, but don't just do something because someone on the internet told you to. Experiment with new things and refine what already works for you. Sorry about the rant. But hey, now that you're at the bottom, how about giving alacritty a try? If you're on Arch just go over to your local neighborhood terminal and smack your keyboard in a fashion that inputs `sudo pacman -S alacritty` into it (or use whatever pacman wrapper you want, I don't care). Feel free to steal my alacritty dotfiles too (although they're kinda basic) (if you are Thomas though you won't like the fonts since you care too much about what fonts people use). More information can be found on their Github page here: https://github.com/alacritty/alacritty Signed-off-by: Logan Gartner <logan2611@gmail.com>
2020-07-01 04:22:51 -04:00
# Configuration for Alacritty, the GPU enhanced terminal emulator.
# Any items in the `env` entry below will be added as
# environment variables. Some entries may override variables
# set by alacritty itself.
env:
Added Alacritty config and TERMINAL variable. Now I know Thomas is gonna get really pissy that I'm not using st, but frankly I don't give a shit what he thinks. What Thomas doesn't realise is that his way is not the best way. There are no best ways, just better ways. Sure, st is a good terminal, but I'm literally using Alacritty to type this message, and I like it. It is easy to configure and has GPU acceleration which makes it fast enough to literally watch a 360p video in text mode (possibly more, didn't test much since it already wiped st off the face of the planet). "aLAcRitTY is bLOaT" shut. the. fuck. up. If you cared about bloat that much you'd be using Artix, or better yet, NixOS. Instead, you're using a distro that literally stores 2 copies of every package you download and the 20 billion dependencies that come with it. You regularly bitch about how many dependencies KDE has but you haven't stopped to look at your own dependency clusterfuck. KDE is a perfectly fine desktop with plenty of features built in fully configured for your enjoyment (if you couldn't tell from my dotfiles its not my favorite, but I'll definitely admit to using KDE when I'm feeling lazy on a new install). You're probably going to say that its bloat because of that, but you clearly don't give a shit because you're still on vanilla Arch. Part of the Linux experience is being able to pick and choose your own experience. Maybe some don't want to use a tiling window manager. Sure, its more efficient once you get to know it, but not everyone is capable of learning the drastically different workflow that comes with TWMs/DWMs. Maybe they don't have the days, possibly weeks to setup everything to a usable state. Maybe they just want a computer that works. Now, I do get pretty pissed if you complain about problems that come with your choice of Linux lifestyle and A. Don't do anything to address them or B. Blame something else. Ex. Clay regularly complains about "Wine crashes all the time and has poor compatability". This was probably true back in Wine 2.0 when Clay was probably not even alive, but times have changed. Furthermore, I come to find out that the problems he is having either exist on Windows (ex. Into the Breach maximize button being useless) or are because of his WM (he uses Linux Mint Cinnamon btw). What I'm trying to say is, Thomas, be more open. Just because someone uses KDE doesn't mean that they're not good enough to setup i3. And to anyone else reading this, find what works best for you. I'm not saying to completely ignore what other people prefer, but don't just do something because someone on the internet told you to. Experiment with new things and refine what already works for you. Sorry about the rant. But hey, now that you're at the bottom, how about giving alacritty a try? If you're on Arch just go over to your local neighborhood terminal and smack your keyboard in a fashion that inputs `sudo pacman -S alacritty` into it (or use whatever pacman wrapper you want, I don't care). Feel free to steal my alacritty dotfiles too (although they're kinda basic) (if you are Thomas though you won't like the fonts since you care too much about what fonts people use). More information can be found on their Github page here: https://github.com/alacritty/alacritty Signed-off-by: Logan Gartner <logan2611@gmail.com>
2020-07-01 04:22:51 -04:00
# TERM variable
#
# This value is used to set the `$TERM` environment variable for
# each instance of Alacritty. If it is not present, alacritty will
# check the local terminfo database and use `alacritty` if it is
# available, otherwise `xterm-256color` is used.
TERM: xterm-256color
Added Alacritty config and TERMINAL variable. Now I know Thomas is gonna get really pissy that I'm not using st, but frankly I don't give a shit what he thinks. What Thomas doesn't realise is that his way is not the best way. There are no best ways, just better ways. Sure, st is a good terminal, but I'm literally using Alacritty to type this message, and I like it. It is easy to configure and has GPU acceleration which makes it fast enough to literally watch a 360p video in text mode (possibly more, didn't test much since it already wiped st off the face of the planet). "aLAcRitTY is bLOaT" shut. the. fuck. up. If you cared about bloat that much you'd be using Artix, or better yet, NixOS. Instead, you're using a distro that literally stores 2 copies of every package you download and the 20 billion dependencies that come with it. You regularly bitch about how many dependencies KDE has but you haven't stopped to look at your own dependency clusterfuck. KDE is a perfectly fine desktop with plenty of features built in fully configured for your enjoyment (if you couldn't tell from my dotfiles its not my favorite, but I'll definitely admit to using KDE when I'm feeling lazy on a new install). You're probably going to say that its bloat because of that, but you clearly don't give a shit because you're still on vanilla Arch. Part of the Linux experience is being able to pick and choose your own experience. Maybe some don't want to use a tiling window manager. Sure, its more efficient once you get to know it, but not everyone is capable of learning the drastically different workflow that comes with TWMs/DWMs. Maybe they don't have the days, possibly weeks to setup everything to a usable state. Maybe they just want a computer that works. Now, I do get pretty pissed if you complain about problems that come with your choice of Linux lifestyle and A. Don't do anything to address them or B. Blame something else. Ex. Clay regularly complains about "Wine crashes all the time and has poor compatability". This was probably true back in Wine 2.0 when Clay was probably not even alive, but times have changed. Furthermore, I come to find out that the problems he is having either exist on Windows (ex. Into the Breach maximize button being useless) or are because of his WM (he uses Linux Mint Cinnamon btw). What I'm trying to say is, Thomas, be more open. Just because someone uses KDE doesn't mean that they're not good enough to setup i3. And to anyone else reading this, find what works best for you. I'm not saying to completely ignore what other people prefer, but don't just do something because someone on the internet told you to. Experiment with new things and refine what already works for you. Sorry about the rant. But hey, now that you're at the bottom, how about giving alacritty a try? If you're on Arch just go over to your local neighborhood terminal and smack your keyboard in a fashion that inputs `sudo pacman -S alacritty` into it (or use whatever pacman wrapper you want, I don't care). Feel free to steal my alacritty dotfiles too (although they're kinda basic) (if you are Thomas though you won't like the fonts since you care too much about what fonts people use). More information can be found on their Github page here: https://github.com/alacritty/alacritty Signed-off-by: Logan Gartner <logan2611@gmail.com>
2020-07-01 04:22:51 -04:00
window:
# Window dimensions (changes require restart)
#
# Specified in number of columns/lines, not pixels.
# If both are `0`, this setting is ignored.
#dimensions:
# columns: 0
# lines: 0
# Window position (changes require restart)
#
# Specified in number of pixels.
# If the position is not set, the window manager will handle the placement.
#position:
# x: 0
# y: 0
# Window padding (changes require restart)
#
# Blank space added around the window in pixels. This padding is scaled
# by DPI and the specified value is always added at both opposing sides.
#padding:
# x: 0
# y: 0
# Spread additional padding evenly around the terminal content.
#dynamic_padding: false
# Window decorations
#
# Values for `decorations`:
# - full: Borders and title bar
# - none: Neither borders nor title bar
#
# Values for `decorations` (macOS only):
# - transparent: Title bar, transparent background and title bar buttons
# - buttonless: Title bar, transparent background, but no title bar buttons
decorations: none
# Startup Mode (changes require restart)
#
# Values for `startup_mode`:
# - Windowed
# - Maximized
# - Fullscreen
#
# Values for `startup_mode` (macOS only):
# - SimpleFullscreen
startup_mode: Windowed
# Window title
#title: Alacritty
# Window class (Linux/BSD only):
#class:
# Application instance name
#instance: Alacritty
# General application class
#general: Alacritty
# GTK theme variant (Linux/BSD only)
#
# Override the variant of the GTK theme. Commonly supported values are `dark` and `light`.
# Set this to `None` to use the default theme variant.
#gtk_theme_variant: None
#scrolling:
# Maximum number of lines in the scrollback buffer.
# Specifying '0' will disable scrolling.
#history: 10000
# Number of lines the viewport will move for every line scrolled when
# scrollback is enabled (history > 0).
#multiplier: 3
# Font configuration
font:
# Normal (roman) font face
normal:
# Font family
#
# Default:
# - (macOS) Menlo
# - (Linux/BSD) monospace
# - (Windows) Consolas
2021-05-28 02:14:38 -04:00
#family: Liberation Mono
family: Source Code Pro
Added Alacritty config and TERMINAL variable. Now I know Thomas is gonna get really pissy that I'm not using st, but frankly I don't give a shit what he thinks. What Thomas doesn't realise is that his way is not the best way. There are no best ways, just better ways. Sure, st is a good terminal, but I'm literally using Alacritty to type this message, and I like it. It is easy to configure and has GPU acceleration which makes it fast enough to literally watch a 360p video in text mode (possibly more, didn't test much since it already wiped st off the face of the planet). "aLAcRitTY is bLOaT" shut. the. fuck. up. If you cared about bloat that much you'd be using Artix, or better yet, NixOS. Instead, you're using a distro that literally stores 2 copies of every package you download and the 20 billion dependencies that come with it. You regularly bitch about how many dependencies KDE has but you haven't stopped to look at your own dependency clusterfuck. KDE is a perfectly fine desktop with plenty of features built in fully configured for your enjoyment (if you couldn't tell from my dotfiles its not my favorite, but I'll definitely admit to using KDE when I'm feeling lazy on a new install). You're probably going to say that its bloat because of that, but you clearly don't give a shit because you're still on vanilla Arch. Part of the Linux experience is being able to pick and choose your own experience. Maybe some don't want to use a tiling window manager. Sure, its more efficient once you get to know it, but not everyone is capable of learning the drastically different workflow that comes with TWMs/DWMs. Maybe they don't have the days, possibly weeks to setup everything to a usable state. Maybe they just want a computer that works. Now, I do get pretty pissed if you complain about problems that come with your choice of Linux lifestyle and A. Don't do anything to address them or B. Blame something else. Ex. Clay regularly complains about "Wine crashes all the time and has poor compatability". This was probably true back in Wine 2.0 when Clay was probably not even alive, but times have changed. Furthermore, I come to find out that the problems he is having either exist on Windows (ex. Into the Breach maximize button being useless) or are because of his WM (he uses Linux Mint Cinnamon btw). What I'm trying to say is, Thomas, be more open. Just because someone uses KDE doesn't mean that they're not good enough to setup i3. And to anyone else reading this, find what works best for you. I'm not saying to completely ignore what other people prefer, but don't just do something because someone on the internet told you to. Experiment with new things and refine what already works for you. Sorry about the rant. But hey, now that you're at the bottom, how about giving alacritty a try? If you're on Arch just go over to your local neighborhood terminal and smack your keyboard in a fashion that inputs `sudo pacman -S alacritty` into it (or use whatever pacman wrapper you want, I don't care). Feel free to steal my alacritty dotfiles too (although they're kinda basic) (if you are Thomas though you won't like the fonts since you care too much about what fonts people use). More information can be found on their Github page here: https://github.com/alacritty/alacritty Signed-off-by: Logan Gartner <logan2611@gmail.com>
2020-07-01 04:22:51 -04:00
# The `style` can be specified to pick a specific face.
style: Regular
# Bold font face
bold:
# Font family
#
# If the bold family is not specified, it will fall back to the
# value specified for the normal font.
2021-05-28 02:14:38 -04:00
#family: Liberation Mono
family: Source Code Pro
Added Alacritty config and TERMINAL variable. Now I know Thomas is gonna get really pissy that I'm not using st, but frankly I don't give a shit what he thinks. What Thomas doesn't realise is that his way is not the best way. There are no best ways, just better ways. Sure, st is a good terminal, but I'm literally using Alacritty to type this message, and I like it. It is easy to configure and has GPU acceleration which makes it fast enough to literally watch a 360p video in text mode (possibly more, didn't test much since it already wiped st off the face of the planet). "aLAcRitTY is bLOaT" shut. the. fuck. up. If you cared about bloat that much you'd be using Artix, or better yet, NixOS. Instead, you're using a distro that literally stores 2 copies of every package you download and the 20 billion dependencies that come with it. You regularly bitch about how many dependencies KDE has but you haven't stopped to look at your own dependency clusterfuck. KDE is a perfectly fine desktop with plenty of features built in fully configured for your enjoyment (if you couldn't tell from my dotfiles its not my favorite, but I'll definitely admit to using KDE when I'm feeling lazy on a new install). You're probably going to say that its bloat because of that, but you clearly don't give a shit because you're still on vanilla Arch. Part of the Linux experience is being able to pick and choose your own experience. Maybe some don't want to use a tiling window manager. Sure, its more efficient once you get to know it, but not everyone is capable of learning the drastically different workflow that comes with TWMs/DWMs. Maybe they don't have the days, possibly weeks to setup everything to a usable state. Maybe they just want a computer that works. Now, I do get pretty pissed if you complain about problems that come with your choice of Linux lifestyle and A. Don't do anything to address them or B. Blame something else. Ex. Clay regularly complains about "Wine crashes all the time and has poor compatability". This was probably true back in Wine 2.0 when Clay was probably not even alive, but times have changed. Furthermore, I come to find out that the problems he is having either exist on Windows (ex. Into the Breach maximize button being useless) or are because of his WM (he uses Linux Mint Cinnamon btw). What I'm trying to say is, Thomas, be more open. Just because someone uses KDE doesn't mean that they're not good enough to setup i3. And to anyone else reading this, find what works best for you. I'm not saying to completely ignore what other people prefer, but don't just do something because someone on the internet told you to. Experiment with new things and refine what already works for you. Sorry about the rant. But hey, now that you're at the bottom, how about giving alacritty a try? If you're on Arch just go over to your local neighborhood terminal and smack your keyboard in a fashion that inputs `sudo pacman -S alacritty` into it (or use whatever pacman wrapper you want, I don't care). Feel free to steal my alacritty dotfiles too (although they're kinda basic) (if you are Thomas though you won't like the fonts since you care too much about what fonts people use). More information can be found on their Github page here: https://github.com/alacritty/alacritty Signed-off-by: Logan Gartner <logan2611@gmail.com>
2020-07-01 04:22:51 -04:00
# The `style` can be specified to pick a specific face.
style: Bold
# Italic font face
italic:
# Font family
#
# If the italic family is not specified, it will fall back to the
# value specified for the normal font.
2021-05-28 02:14:38 -04:00
#family: Liberation Mono
family: Source Code Pro
Added Alacritty config and TERMINAL variable. Now I know Thomas is gonna get really pissy that I'm not using st, but frankly I don't give a shit what he thinks. What Thomas doesn't realise is that his way is not the best way. There are no best ways, just better ways. Sure, st is a good terminal, but I'm literally using Alacritty to type this message, and I like it. It is easy to configure and has GPU acceleration which makes it fast enough to literally watch a 360p video in text mode (possibly more, didn't test much since it already wiped st off the face of the planet). "aLAcRitTY is bLOaT" shut. the. fuck. up. If you cared about bloat that much you'd be using Artix, or better yet, NixOS. Instead, you're using a distro that literally stores 2 copies of every package you download and the 20 billion dependencies that come with it. You regularly bitch about how many dependencies KDE has but you haven't stopped to look at your own dependency clusterfuck. KDE is a perfectly fine desktop with plenty of features built in fully configured for your enjoyment (if you couldn't tell from my dotfiles its not my favorite, but I'll definitely admit to using KDE when I'm feeling lazy on a new install). You're probably going to say that its bloat because of that, but you clearly don't give a shit because you're still on vanilla Arch. Part of the Linux experience is being able to pick and choose your own experience. Maybe some don't want to use a tiling window manager. Sure, its more efficient once you get to know it, but not everyone is capable of learning the drastically different workflow that comes with TWMs/DWMs. Maybe they don't have the days, possibly weeks to setup everything to a usable state. Maybe they just want a computer that works. Now, I do get pretty pissed if you complain about problems that come with your choice of Linux lifestyle and A. Don't do anything to address them or B. Blame something else. Ex. Clay regularly complains about "Wine crashes all the time and has poor compatability". This was probably true back in Wine 2.0 when Clay was probably not even alive, but times have changed. Furthermore, I come to find out that the problems he is having either exist on Windows (ex. Into the Breach maximize button being useless) or are because of his WM (he uses Linux Mint Cinnamon btw). What I'm trying to say is, Thomas, be more open. Just because someone uses KDE doesn't mean that they're not good enough to setup i3. And to anyone else reading this, find what works best for you. I'm not saying to completely ignore what other people prefer, but don't just do something because someone on the internet told you to. Experiment with new things and refine what already works for you. Sorry about the rant. But hey, now that you're at the bottom, how about giving alacritty a try? If you're on Arch just go over to your local neighborhood terminal and smack your keyboard in a fashion that inputs `sudo pacman -S alacritty` into it (or use whatever pacman wrapper you want, I don't care). Feel free to steal my alacritty dotfiles too (although they're kinda basic) (if you are Thomas though you won't like the fonts since you care too much about what fonts people use). More information can be found on their Github page here: https://github.com/alacritty/alacritty Signed-off-by: Logan Gartner <logan2611@gmail.com>
2020-07-01 04:22:51 -04:00
# The `style` can be specified to pick a specific face.
style: Italic
# Bold italic font face
bold_italic:
# Font family
#
# If the bold italic family is not specified, it will fall back to the
# value specified for the normal font.
2021-05-28 02:14:38 -04:00
#family: Liberation Mono
family: Source Code Pro
Added Alacritty config and TERMINAL variable. Now I know Thomas is gonna get really pissy that I'm not using st, but frankly I don't give a shit what he thinks. What Thomas doesn't realise is that his way is not the best way. There are no best ways, just better ways. Sure, st is a good terminal, but I'm literally using Alacritty to type this message, and I like it. It is easy to configure and has GPU acceleration which makes it fast enough to literally watch a 360p video in text mode (possibly more, didn't test much since it already wiped st off the face of the planet). "aLAcRitTY is bLOaT" shut. the. fuck. up. If you cared about bloat that much you'd be using Artix, or better yet, NixOS. Instead, you're using a distro that literally stores 2 copies of every package you download and the 20 billion dependencies that come with it. You regularly bitch about how many dependencies KDE has but you haven't stopped to look at your own dependency clusterfuck. KDE is a perfectly fine desktop with plenty of features built in fully configured for your enjoyment (if you couldn't tell from my dotfiles its not my favorite, but I'll definitely admit to using KDE when I'm feeling lazy on a new install). You're probably going to say that its bloat because of that, but you clearly don't give a shit because you're still on vanilla Arch. Part of the Linux experience is being able to pick and choose your own experience. Maybe some don't want to use a tiling window manager. Sure, its more efficient once you get to know it, but not everyone is capable of learning the drastically different workflow that comes with TWMs/DWMs. Maybe they don't have the days, possibly weeks to setup everything to a usable state. Maybe they just want a computer that works. Now, I do get pretty pissed if you complain about problems that come with your choice of Linux lifestyle and A. Don't do anything to address them or B. Blame something else. Ex. Clay regularly complains about "Wine crashes all the time and has poor compatability". This was probably true back in Wine 2.0 when Clay was probably not even alive, but times have changed. Furthermore, I come to find out that the problems he is having either exist on Windows (ex. Into the Breach maximize button being useless) or are because of his WM (he uses Linux Mint Cinnamon btw). What I'm trying to say is, Thomas, be more open. Just because someone uses KDE doesn't mean that they're not good enough to setup i3. And to anyone else reading this, find what works best for you. I'm not saying to completely ignore what other people prefer, but don't just do something because someone on the internet told you to. Experiment with new things and refine what already works for you. Sorry about the rant. But hey, now that you're at the bottom, how about giving alacritty a try? If you're on Arch just go over to your local neighborhood terminal and smack your keyboard in a fashion that inputs `sudo pacman -S alacritty` into it (or use whatever pacman wrapper you want, I don't care). Feel free to steal my alacritty dotfiles too (although they're kinda basic) (if you are Thomas though you won't like the fonts since you care too much about what fonts people use). More information can be found on their Github page here: https://github.com/alacritty/alacritty Signed-off-by: Logan Gartner <logan2611@gmail.com>
2020-07-01 04:22:51 -04:00
# The `style` can be specified to pick a specific face.
style: Bold Italic
# Point size
size: 8.0
Added Alacritty config and TERMINAL variable. Now I know Thomas is gonna get really pissy that I'm not using st, but frankly I don't give a shit what he thinks. What Thomas doesn't realise is that his way is not the best way. There are no best ways, just better ways. Sure, st is a good terminal, but I'm literally using Alacritty to type this message, and I like it. It is easy to configure and has GPU acceleration which makes it fast enough to literally watch a 360p video in text mode (possibly more, didn't test much since it already wiped st off the face of the planet). "aLAcRitTY is bLOaT" shut. the. fuck. up. If you cared about bloat that much you'd be using Artix, or better yet, NixOS. Instead, you're using a distro that literally stores 2 copies of every package you download and the 20 billion dependencies that come with it. You regularly bitch about how many dependencies KDE has but you haven't stopped to look at your own dependency clusterfuck. KDE is a perfectly fine desktop with plenty of features built in fully configured for your enjoyment (if you couldn't tell from my dotfiles its not my favorite, but I'll definitely admit to using KDE when I'm feeling lazy on a new install). You're probably going to say that its bloat because of that, but you clearly don't give a shit because you're still on vanilla Arch. Part of the Linux experience is being able to pick and choose your own experience. Maybe some don't want to use a tiling window manager. Sure, its more efficient once you get to know it, but not everyone is capable of learning the drastically different workflow that comes with TWMs/DWMs. Maybe they don't have the days, possibly weeks to setup everything to a usable state. Maybe they just want a computer that works. Now, I do get pretty pissed if you complain about problems that come with your choice of Linux lifestyle and A. Don't do anything to address them or B. Blame something else. Ex. Clay regularly complains about "Wine crashes all the time and has poor compatability". This was probably true back in Wine 2.0 when Clay was probably not even alive, but times have changed. Furthermore, I come to find out that the problems he is having either exist on Windows (ex. Into the Breach maximize button being useless) or are because of his WM (he uses Linux Mint Cinnamon btw). What I'm trying to say is, Thomas, be more open. Just because someone uses KDE doesn't mean that they're not good enough to setup i3. And to anyone else reading this, find what works best for you. I'm not saying to completely ignore what other people prefer, but don't just do something because someone on the internet told you to. Experiment with new things and refine what already works for you. Sorry about the rant. But hey, now that you're at the bottom, how about giving alacritty a try? If you're on Arch just go over to your local neighborhood terminal and smack your keyboard in a fashion that inputs `sudo pacman -S alacritty` into it (or use whatever pacman wrapper you want, I don't care). Feel free to steal my alacritty dotfiles too (although they're kinda basic) (if you are Thomas though you won't like the fonts since you care too much about what fonts people use). More information can be found on their Github page here: https://github.com/alacritty/alacritty Signed-off-by: Logan Gartner <logan2611@gmail.com>
2020-07-01 04:22:51 -04:00
# Offset is the extra space around each character. `offset.y` can be thought of
# as modifying the line spacing, and `offset.x` as modifying the letter spacing.
#offset:
# x: 0
# y: 0
# Glyph offset determines the locations of the glyphs within their cells with
# the default being at the bottom. Increasing `x` moves the glyph to the right,
# increasing `y` moves the glyph upwards.
#glyph_offset:
# x: 0
# y: 0
# Thin stroke font rendering (macOS only)
#
# Thin strokes are suitable for retina displays, but for non-retina screens
# it is recommended to set `use_thin_strokes` to `false`
#
# macOS >= 10.14.x:
#
# If the font quality on non-retina display looks bad then set
# `use_thin_strokes` to `true` and enable font smoothing by running the
# following command:
# `defaults write -g CGFontRenderingFontSmoothingDisabled -bool NO`
#
# This is a global setting and will require a log out or restart to take
# effect.
#use_thin_strokes: true
# If `true`, bold text is drawn using the bright color variants.
#draw_bold_text_with_bright_colors: false
# Colors (Tomorrow Night Bright)
colors:
# Default colors
primary:
background: '#000000'
foreground: '#eaeaea'
Added Alacritty config and TERMINAL variable. Now I know Thomas is gonna get really pissy that I'm not using st, but frankly I don't give a shit what he thinks. What Thomas doesn't realise is that his way is not the best way. There are no best ways, just better ways. Sure, st is a good terminal, but I'm literally using Alacritty to type this message, and I like it. It is easy to configure and has GPU acceleration which makes it fast enough to literally watch a 360p video in text mode (possibly more, didn't test much since it already wiped st off the face of the planet). "aLAcRitTY is bLOaT" shut. the. fuck. up. If you cared about bloat that much you'd be using Artix, or better yet, NixOS. Instead, you're using a distro that literally stores 2 copies of every package you download and the 20 billion dependencies that come with it. You regularly bitch about how many dependencies KDE has but you haven't stopped to look at your own dependency clusterfuck. KDE is a perfectly fine desktop with plenty of features built in fully configured for your enjoyment (if you couldn't tell from my dotfiles its not my favorite, but I'll definitely admit to using KDE when I'm feeling lazy on a new install). You're probably going to say that its bloat because of that, but you clearly don't give a shit because you're still on vanilla Arch. Part of the Linux experience is being able to pick and choose your own experience. Maybe some don't want to use a tiling window manager. Sure, its more efficient once you get to know it, but not everyone is capable of learning the drastically different workflow that comes with TWMs/DWMs. Maybe they don't have the days, possibly weeks to setup everything to a usable state. Maybe they just want a computer that works. Now, I do get pretty pissed if you complain about problems that come with your choice of Linux lifestyle and A. Don't do anything to address them or B. Blame something else. Ex. Clay regularly complains about "Wine crashes all the time and has poor compatability". This was probably true back in Wine 2.0 when Clay was probably not even alive, but times have changed. Furthermore, I come to find out that the problems he is having either exist on Windows (ex. Into the Breach maximize button being useless) or are because of his WM (he uses Linux Mint Cinnamon btw). What I'm trying to say is, Thomas, be more open. Just because someone uses KDE doesn't mean that they're not good enough to setup i3. And to anyone else reading this, find what works best for you. I'm not saying to completely ignore what other people prefer, but don't just do something because someone on the internet told you to. Experiment with new things and refine what already works for you. Sorry about the rant. But hey, now that you're at the bottom, how about giving alacritty a try? If you're on Arch just go over to your local neighborhood terminal and smack your keyboard in a fashion that inputs `sudo pacman -S alacritty` into it (or use whatever pacman wrapper you want, I don't care). Feel free to steal my alacritty dotfiles too (although they're kinda basic) (if you are Thomas though you won't like the fonts since you care too much about what fonts people use). More information can be found on their Github page here: https://github.com/alacritty/alacritty Signed-off-by: Logan Gartner <logan2611@gmail.com>
2020-07-01 04:22:51 -04:00
# Bright and dim foreground colors
#
# The dimmed foreground color is calculated automatically if it is not present.
# If the bright foreground color is not set, or `draw_bold_text_with_bright_colors`
# is `false`, the normal foreground color will be used.
#dim_foreground: '#9a9a9a'
#bright_foreground: '#ffffff'
# Cursor colors
#
# Colors which should be used to draw the terminal cursor. If these are unset,
# the cursor color will be the inverse of the cell color.
#cursor:
# text: '#000000'
# cursor: '#ffffff'
# Selection colors
#
# Colors which should be used to draw the selection area. If selection
# background is unset, selection color will be the inverse of the cell colors.
# If only text is unset the cell text color will remain the same.
#selection:
# text: '#eaeaea'
# background: '#404040'
# Normal colors
normal:
black: '#000000'
red: '#b21818'
green: '#18b218'
yellow: '#b26818'
blue: '#1818b2'
magenta: '#b218b2'
cyan: '#18b2b2'
white: '#b2b2b2'
# Bright colors
bright:
black: '#686868'
red: '#ff5454'
green: '#54ff54'
yellow: '#ffff54'
blue: '#5454ff'
magenta: '#ff54ff'
cyan: '#54ffff'
white: '#ffffff'
# Dim colors
#
# If the dim colors are not set, they will be calculated automatically based
# on the `normal` colors.
#dim:
# black: '#000000'
# red: '#8c3336'
# green: '#7a8530'
# yellow: '#97822e'
# blue: '#506d8f'
# magenta: '#80638e'
# cyan: '#497e7a'
# white: '#9a9a9a'
# Indexed Colors
#
# The indexed colors include all colors from 16 to 256.
# When these are not set, they're filled with sensible defaults.
#
# Example:
# `- { index: 16, color: '#ff00ff' }`
#
#indexed_colors: []
# Visual Bell
#
# Any time the BEL code is received, Alacritty "rings" the visual bell. Once
# rung, the terminal background will be set to white and transition back to the
# default background color. You can control the rate of this transition by
# setting the `duration` property (represented in milliseconds). You can also
# configure the transition function by setting the `animation` property.
#
# Values for `animation`:
# - Ease
# - EaseOut
# - EaseOutSine
# - EaseOutQuad
# - EaseOutCubic
# - EaseOutQuart
# - EaseOutQuint
# - EaseOutExpo
# - EaseOutCirc
# - Linear
#
# Specifying a `duration` of `0` will disable the visual bell.
#visual_bell:
# animation: EaseOutExpo
# duration: 0
# color: '#ffffff'
# Background opacity
#
# Window opacity as a floating point number from `0.0` to `1.0`.
# The value `0.0` is completely transparent and `1.0` is opaque.
background_opacity: 0.8
#selection:
#semantic_escape_chars: ",│`|:\"' ()[]{}<>\t"
# When set to `true`, selected text will be copied to the primary clipboard.
#save_to_clipboard: false
# Allow terminal applications to change Alacritty's window title.
#dynamic_title: true
Added Alacritty config and TERMINAL variable. Now I know Thomas is gonna get really pissy that I'm not using st, but frankly I don't give a shit what he thinks. What Thomas doesn't realise is that his way is not the best way. There are no best ways, just better ways. Sure, st is a good terminal, but I'm literally using Alacritty to type this message, and I like it. It is easy to configure and has GPU acceleration which makes it fast enough to literally watch a 360p video in text mode (possibly more, didn't test much since it already wiped st off the face of the planet). "aLAcRitTY is bLOaT" shut. the. fuck. up. If you cared about bloat that much you'd be using Artix, or better yet, NixOS. Instead, you're using a distro that literally stores 2 copies of every package you download and the 20 billion dependencies that come with it. You regularly bitch about how many dependencies KDE has but you haven't stopped to look at your own dependency clusterfuck. KDE is a perfectly fine desktop with plenty of features built in fully configured for your enjoyment (if you couldn't tell from my dotfiles its not my favorite, but I'll definitely admit to using KDE when I'm feeling lazy on a new install). You're probably going to say that its bloat because of that, but you clearly don't give a shit because you're still on vanilla Arch. Part of the Linux experience is being able to pick and choose your own experience. Maybe some don't want to use a tiling window manager. Sure, its more efficient once you get to know it, but not everyone is capable of learning the drastically different workflow that comes with TWMs/DWMs. Maybe they don't have the days, possibly weeks to setup everything to a usable state. Maybe they just want a computer that works. Now, I do get pretty pissed if you complain about problems that come with your choice of Linux lifestyle and A. Don't do anything to address them or B. Blame something else. Ex. Clay regularly complains about "Wine crashes all the time and has poor compatability". This was probably true back in Wine 2.0 when Clay was probably not even alive, but times have changed. Furthermore, I come to find out that the problems he is having either exist on Windows (ex. Into the Breach maximize button being useless) or are because of his WM (he uses Linux Mint Cinnamon btw). What I'm trying to say is, Thomas, be more open. Just because someone uses KDE doesn't mean that they're not good enough to setup i3. And to anyone else reading this, find what works best for you. I'm not saying to completely ignore what other people prefer, but don't just do something because someone on the internet told you to. Experiment with new things and refine what already works for you. Sorry about the rant. But hey, now that you're at the bottom, how about giving alacritty a try? If you're on Arch just go over to your local neighborhood terminal and smack your keyboard in a fashion that inputs `sudo pacman -S alacritty` into it (or use whatever pacman wrapper you want, I don't care). Feel free to steal my alacritty dotfiles too (although they're kinda basic) (if you are Thomas though you won't like the fonts since you care too much about what fonts people use). More information can be found on their Github page here: https://github.com/alacritty/alacritty Signed-off-by: Logan Gartner <logan2611@gmail.com>
2020-07-01 04:22:51 -04:00
#cursor:
# Cursor style
#
# Values for `style`:
# - ▇ Block
# - _ Underline
# - | Beam
#style: Block
# If this is `true`, the cursor will be rendered as a hollow box when the
# window is not focused.
#unfocused_hollow: true
# Live config reload (changes require restart)
#live_config_reload: true
# Shell
#
# You can set `shell.program` to the path of your favorite shell, e.g. `/bin/fish`.
# Entries in `shell.args` are passed unmodified as arguments to the shell.
#
# Default:
# - (macOS) /bin/bash --login
# - (Linux/BSD) user login shell
# - (Windows) powershell
#shell:
# program: /bin/bash
# args:
# - --login
# Startup directory
#
# Directory the shell is started in. If this is unset, or `None`, the working
# directory of the parent process will be used.
#working_directory: None
# WinPTY backend (Windows only)
#
# Alacritty defaults to using the newer ConPTY backend if it is available,
# since it resolves a lot of bugs and is quite a bit faster. If it is not
# available, the the WinPTY backend will be used instead.
#
# Setting this option to `true` makes Alacritty use the legacy WinPTY backend,
# even if the ConPTY backend is available.
#winpty_backend: false
# Send ESC (\x1b) before characters when alt is pressed.
#alt_send_esc: true
#mouse:
# Click settings
#
# The `double_click` and `triple_click` settings control the time
# alacritty should wait for accepting multiple clicks as one double
# or triple click.
#double_click: { threshold: 300 }
#triple_click: { threshold: 300 }
# If this is `true`, the cursor is temporarily hidden when typing.
#hide_when_typing: false
#url:
# URL launcher
#
# This program is executed when clicking on a text which is recognized as a URL.
# The URL is always added to the command as the last parameter.
#
# When set to `None`, URL launching will be disabled completely.
#
# Default:
# - (macOS) open
# - (Linux/BSD) xdg-open
# - (Windows) explorer
#launcher:
# program: xdg-open
# args: []
# URL modifiers
#
# These are the modifiers that need to be held down for opening URLs when clicking
# on them. The available modifiers are documented in the key binding section.
#modifiers: None
# Mouse bindings
#
# Mouse bindings are specified as a list of objects, much like the key
# bindings further below.
#
# To trigger mouse bindings when an application running within Alacritty captures the mouse, the
# `Shift` modifier is automatically added as a requirement.
#
# Each mouse binding will specify a:
#
# - `mouse`:
#
# - Middle
# - Left
# - Right
# - Numeric identifier such as `5`
#
# - `action` (see key bindings)
#
# And optionally:
#
# - `mods` (see key bindings)
#mouse_bindings:
# - { mouse: Middle, action: PasteSelection }
# Key bindings
#
# Key bindings are specified as a list of objects. For example, this is the
# default paste binding:
#
# `- { key: V, mods: Control|Shift, action: Paste }`
#
# Each key binding will specify a:
#
# - `key`: Identifier of the key pressed
#
# - A-Z
# - F1-F24
# - Key0-Key9
#
# A full list with available key codes can be found here:
# https://docs.rs/glutin/*/glutin/event/enum.VirtualKeyCode.html#variants
#
# Instead of using the name of the keys, the `key` field also supports using
# the scancode of the desired key. Scancodes have to be specified as a
# decimal number. This command will allow you to display the hex scancodes
# for certain keys:
#
# `showkey --scancodes`.
#
# Then exactly one of:
#
# - `chars`: Send a byte sequence to the running application
#
# The `chars` field writes the specified string to the terminal. This makes
# it possible to pass escape sequences. To find escape codes for bindings
# like `PageUp` (`"\x1b[5~"`), you can run the command `showkey -a` outside
# of tmux. Note that applications use terminfo to map escape sequences back
# to keys. It is therefore required to update the terminfo when changing an
# escape sequence.
#
# - `action`: Execute a predefined action
#
# - Copy
# - Paste
# - PasteSelection
# - IncreaseFontSize
# - DecreaseFontSize
# - ResetFontSize
# - ScrollPageUp
# - ScrollPageDown
# - ScrollLineUp
# - ScrollLineDown
# - ScrollToTop
# - ScrollToBottom
# - ClearHistory
# - Hide
# - Minimize
# - Quit
# - ToggleFullscreen
# - SpawnNewInstance
# - ClearLogNotice
# - ReceiveChar
# - None
#
# (macOS only):
# - ToggleSimpleFullscreen: Enters fullscreen without occupying another space
#
# - `command`: Fork and execute a specified command plus arguments
#
# The `command` field must be a map containing a `program` string and an
# `args` array of command line parameter strings. For example:
# `{ program: "alacritty", args: ["-e", "vttest"] }`
#
# And optionally:
#
# - `mods`: Key modifiers to filter binding actions
#
# - Command
# - Control
# - Option
# - Super
# - Shift
# - Alt
#
# Multiple `mods` can be combined using `|` like this:
# `mods: Control|Shift`.
# Whitespace and capitalization are relevant and must match the example.
#
# - `mode`: Indicate a binding for only specific terminal reported modes
#
# This is mainly used to send applications the correct escape sequences
# when in different modes.
#
# - AppCursor
# - AppKeypad
# - Alt
#
# A `~` operator can be used before a mode to apply the binding whenever
# the mode is *not* active, e.g. `~Alt`.
#
# Bindings are always filled by default, but will be replaced when a new
# binding with the same triggers is defined. To unset a default binding, it can
# be mapped to the `ReceiveChar` action. Alternatively, you can use `None` for
# a no-op if you do not wish to receive input characters for that binding.
#
# If the same trigger is assigned to multiple actions, all of them are executed
# at once.
#key_bindings:
# (Windows, Linux, and BSD only)
#- { key: V, mods: Control|Shift, action: Paste }
#- { key: C, mods: Control|Shift, action: Copy }
#- { key: Insert, mods: Shift, action: PasteSelection }
#- { key: Key0, mods: Control, action: ResetFontSize }
#- { key: Equals, mods: Control|Shift, action: IncreaseFontSize }
#- { key: Add, mods: Control|Shift, action: IncreaseFontSize }
#- { key: Subtract, mods: Control|Shift, action: DecreaseFontSize }
#- { key: Minus, mods: Control|Shift, action: DecreaseFontSize }
# (Windows only)
#- { key: Return, mods: Alt, action: ToggleFullscreen }
# (macOS only)
#- { key: Key0, mods: Command, action: ResetFontSize }
#- { key: Equals, mods: Command, action: IncreaseFontSize }
#- { key: Add, mods: Command, action: IncreaseFontSize }
#- { key: Minus, mods: Command, action: DecreaseFontSize }
#- { key: K, mods: Command, action: ClearHistory }
#- { key: K, mods: Command, chars: "\x0c" }
#- { key: V, mods: Command, action: Paste }
#- { key: C, mods: Command, action: Copy }
#- { key: H, mods: Command, action: Hide }
#- { key: M, mods: Command, action: Minimize }
#- { key: Q, mods: Command, action: Quit }
#- { key: W, mods: Command, action: Quit }
#- { key: F, mods: Command|Control, action: ToggleFullscreen }
#- { key: Paste, action: Paste }
#- { key: Copy, action: Copy }
#- { key: L, mods: Control, action: ClearLogNotice }
#- { key: L, mods: Control, chars: "\x0c" }
#- { key: PageUp, mods: Shift, action: ScrollPageUp, mode: ~Alt }
#- { key: PageDown, mods: Shift, action: ScrollPageDown, mode: ~Alt }
#- { key: Home, mods: Shift, action: ScrollToTop, mode: ~Alt }
#- { key: End, mods: Shift, action: ScrollToBottom, mode: ~Alt }
#debug:
# Display the time it takes to redraw each frame.
#render_timer: false
# Keep the log file after quitting Alacritty.
#persistent_logging: false
# Log level
#
# Values for `log_level`:
# - None
# - Error
# - Warn
# - Info
# - Debug
# - Trace
#log_level: Warn
# Print all received window events.
#print_events: false