• 2 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle
  • Wezterm is my favourite because it’s really configurable and supports ligatures. Konsole is also quite nice. Generally I’m in favour of using whichever one comes with your DE, or Wezterm if you use a WM.

    Kitty is probably the most popular one, but I don’t like it cause no ligature support no acceleration it claims it has good font management, but fonts never worked properly in my experience.

    Alacritty and Foot are also popular for their performance. Alacritty does have some stability issues though.



  • I’ve used GNOME’s terminal, Konsole, kitty, st, cool-retro-term, Alacritty, foot, and Wezterm.

    The things I want from a terminal emulator are:

    • Ligatures
    • Customisability
    • Icon support / good font management
    • High-ish performance

    Wezterm is afaik the only one with all of those.

    Konsole is actually a pretty good terminal emulator, its big downside is that it looks horribly out-of-place in anything other than Plasma. So as long as you stay on Plasma, Konsole is a good choice. If you ever move to a WM or something, I recommend foot or Wezterm.

    Alacritty has some degree of customisability, Konsole has more, but either way it’s nothing when compared to Wezterm. It is really fast though!

    The thing that skews the duel in favour of Konsole for me is the ligature support. I use neovim for programming and we all know code ligatures are a godsend, so ligature support in the terminal is very much a thing that I want.












  • Finally someone asked about that!

    That’s an alias I made (with some help from the Arch Wiki) that lets me search the AUR for a package using fzf and then install it.

    alias get="paru -Slq | fzf --preview 'paru -Si {}' --layout=reverse --bind 'enter:execute(paru -S {})+accept'"

    (replace paru with your AUR helper of choice if different, requires fzf)

    Also, my neovim config is available in the link!







  • Move all your heavily modified config files into a git repository and host it somewhere. Then symlink all your config files to where they should be with ln -s ~/.config/whatever ~/gitrepo/whatever. That’s how you preserve your important configs.

    You can easily get a list of your installed packages (which you can keep in your repository) with apt list --installed > packages.txt. You can then format that list to one you can install from with sed -e "s-/.*$--" <packages.txt (or something, i don’t have apt, can’t test it fully).

    In fact, if someone here is more familiar with apt, please find a way to filter out packages that were not explicitly installed and reply to this comment with your solution.