blob: 51fbb7dfe889af36fc8a5b6435e05986817ba672 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
|
# be careful not to put this under `HOST xxx`, else only when ssh to that host will add keys to agent
# another approach is to put it under `HOST *`
# https://unix.stackexchange.com/a/577490/459013
AddKeysToAgent yes
# If use alacritty, need send COLORTERM env to remote server to let remote server ls show color,
# more see alacritty.toml config
SendEnv COLORTERM
Host pp
Hostname xyzpp
User xyz
Host hpc
Hostname coe-hpc1.sjsu.edu
User 012404405
# I could not get this HPC to install alacritty terminfo to ~/.terminfo by `infocmp | ssh studio 'tic -x /dev/stdin'`.
# And the HPC does not have alacritty terminfo in /usr/share/terminfo/a.
# And it has issues when me using alacritty as TERM env. And manual copy terminfo to ~/.terminfo does not fix the issues.
# Issues are `htop` and `vim` errors.
# I still want to use alacritty as TERM env on my laptop, so I choose to set TERM env here. xterm-256color and st-256color both works,
# but I want to use alacritty colorscheme. It seems if I set st or xterm as TERM env, alacritty colorscheme is used,
# maybe because those TERM env means truecolor?
# https://wiki.archlinux.org/title/Alacritty#Terminal_functionality_unavailable_in_remote_shells
# https://github.com/alacritty/alacritty/issues/3901
SetEnv TERM=st
Host ca
Hostname ca.flylightning.xyz
User xyz
Host aa
Hostname aawg
User xyz
Host ib
Hostname ib.flylightning.xyz
User xyz
|
