| :80 { | |
| root /serve | |
| } |
| # A minimal configuration for Neomutt/Mutt and Gmail/G Suite | |
| # For more information, see: | |
| # https://heilala.medium.com/command-line-email-with-neomutt-and-gmail-d558864ac3c8?source=friends_link&sk=4dbd90b6b7aebca3bce8d94c9a053168 | |
| # Decrypts passwords quietly | |
| # see: https://wiki.archlinux.org/index.php/Mutt#Passwords_management | |
| source "gpg -dq $HOME/.my-pwds.gpg |" | |
| # Username and password for your Gmail/G Suite account | |
| set imap_user = "[email protected]" |
| <#assign newList = [] /> | |
| <#list response.data.items as originalList> | |
| <#if ! newList?seq_contains(originalList.xValue)> | |
| <#assign newList = newList + [originalList.xValue] /> | |
| </#if> | |
| </#list> |
UPDATE (March 2020, thanks @ic): I don't know the exact AMI version but yum install docker now works on the latest Amazon Linux 2. The instructions below may still be relevant depending on the vintage AMI you are using.
Amazon changed the install in Linux 2. One no-longer using 'yum' See: https://aws.amazon.com/amazon-linux-2/release-notes/
sudo amazon-linux-extras install docker
sudo service docker start
There are numerous reasons you may need to use multiple SSH keys for accessing GitHub and BitBucket
You may use the same computer for work and personal development and need to separate your work.
When acting as a consultant, it is common to have multiple GitHub and/or BitBucket accounts depending on which client you may be working for.
You may have different projects you're working on where you would like to segregate your access.
| # Add RVM to PATH for scripting. Make sure this is the last PATH variable change. | |
| export PATH="$PATH:$HOME/.rvm/bin" | |
| # Load Nerd Fonts with Powerlevel9k theme for Zsh | |
| POWERLEVEL9K_MODE='nerdfont-complete' | |
| source ~/powerlevel9k/powerlevel9k.zsh-theme | |
| # Customise the Powerlevel9k prompts | |
| POWERLEVEL9K_LEFT_PROMPT_ELEMENTS=(ssh dir vcs newline status) | |
| POWERLEVEL9K_RIGHT_PROMPT_ELEMENTS=() |
This should make True Color (24-bit) and italics work in your tmux session and vim/neovim when using Alacritty (and should be compatible with any other terminal emulator, including Kitty).
Running this script should look the same in tmux as without.
curl -s https://gist.githubusercontent.com/lifepillar/09a44b8cf0f9397465614e622979107f/raw/24-bit-color.sh >24-bit-color.sh
This gist will show the support of font shaping support in the terminal emulators and console programs.
| local wezterm = require 'wezterm'; | |
| return { | |
| default_prog = {"/usr/bin/zsh", "-l"}, | |
| font = wezterm.font_with_fallback({"Iosevka Term SS09 Light"},{foreground="#b0b0b0"}), | |
| font_size = 12.0, | |
| dpi = 96.0, | |
| font_dirs = {"/usr/share/fonts/iosevka-term"}, | |
| font_rules = { | |
| { | |
| italic = true, |
Wayland breaks everything! It is binary incompatible, provides no clear transition path with 1:1 replacements for everything in X11, and is even philosophically incompatible with X11. Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better off avoiding Wayland.
Wayland solves no issues I have but breaks almost everything I need. Even the most basic, most simple things (like xkill) - in this case with no obvious replacement. And usually it stays broken, because the Wayland folks mostly seem to care about Automotive, Gnome, maybe KDE - and alienating everyone else (e.g., people using just an X11 window manager or something like GNUstep) in the process.