summaryrefslogtreecommitdiff
path: root/home/xyz/.config/alacritty/alacritty.toml
diff options
context:
space:
mode:
Diffstat (limited to 'home/xyz/.config/alacritty/alacritty.toml')
-rw-r--r--home/xyz/.config/alacritty/alacritty.toml20
1 files changed, 18 insertions, 2 deletions
diff --git a/home/xyz/.config/alacritty/alacritty.toml b/home/xyz/.config/alacritty/alacritty.toml
index cb7582f3..c6544a8f 100644
--- a/home/xyz/.config/alacritty/alacritty.toml
+++ b/home/xyz/.config/alacritty/alacritty.toml
@@ -5,8 +5,24 @@ vi_mode_style = "Block"
# 1. when set TERM use alacritty on windows, syntax is very bad
# 2. need to set xterm-256color if want ls show color when use ssh
-[env]
-TERM = "xterm-256color"
+# But this is actually a wrong/bad workaround and not real fix for issue 2 above. I should not do this.
+# The correct way is to the patch to add `TERM alacritty` in coreutils git repo src/dircolors.hin
+# But the patch does not go through
+# related coreutils ls issues mailing list:
+# https://lists.gnu.org/archive/html/bug-coreutils/2024-04/msg00022.html
+# https://lists.gnu.org/archive/html/bug-coreutils/2024-04/msg00020.html
+# https://lists.gnu.org/archive/html/coreutils/2021-10/msg00007.html
+# related alacritty issues:
+# https://github.com/alacritty/alacritty/issues/3901
+# https://github.com/alacritty/alacritty/issues/3606
+# https://github.com/alacritty/alacritty/issues/2210
+# https://github.com/alacritty/alacritty/issues/3705
+# https://github.com/alacritty/alacritty/issues/4710
+# I choose a more correct workaround to pass COLORTERM to ssh
+# If some remote server doesn't work well e.g.: can't install alacritty,
+# I then choose to set TERM to st in ssh config for that server
+#[env]
+#TERM = "xterm-256color"
[font]
size = 8.0