SetEnv TERM=xterm-256color
mentioned in the end of your link. I’ll put it next to the line where I set RemoteCommand and include a comment for myself that this SetEnv is for being able to still use RemoteCommand tmux thing even when using Ghostty. missing or unsuitable terminal: xterm-ghostty
Connection to xxx.xxx.xxx.xxx closed.
(IP address removed by me.) Host server3000
IdentityFile ~/.ssh/host_specific/foo/bar/server3000/id_ed25519_baz
RequestTTY yes
RemoteCommand /usr/bin/env tmux new-session -A -s '%L'
Whereas if I outcomment the RemoteCommand setting in my ~/.ssh/config of the laptop I'm connecting form, I can connect fine even using Ghostty as my terminal and from env | grep ^TERM=
I get output TERM=xterm-256color
in the initial normal shell. env | grep ^TERM=
I get output TERM=tmux-256color
So there seems to be some termcap stuff I'd have to figure out if I want to use Ghostty and still be able to run tmux automatically in the way I'm currently doing without problem when using the Terminal that ships with macOS and ssh'ing into my servers. date +%s
I use zsh but I don’t have any addons installed or anything. So for me it is less work to call date +%s instead
I tried to run some of the differently sized DeepSeek R1 locally when those had recently come out, but couldn’t manage at the time to run any of them. And I had to download a lot of data to try those. So if you know a specific size of DeepSeek R1 that will work on 64GB RAM on MacBook Pro M2 Max, or another great local LLM for coding on that, that would be super appreciated