Had major issues with #ClaudeCode for weeks, with mouse positions not registering correctly, semi-auto scrolling, weird selecting etc.

Turns out it was #Ghostty. No issues in either Terminal or #iTerm2.

Back to iTerm2, then.

Why I finally traded iTerm2’s features for Ghostty’s GPU renderer

After years of loyalty to iTerm2, the AI revolution forced me to rethink my terminal. Here's how I migrated to Ghostty — and why I'm never going back.

TechLife
I just discovered that you can drag n drop images rendered in #iTerm2 using #sixel. If you drag the image out of the terminal you get a file. If you then cat the file ... well, I was expecting an image, because sixel, but apparently not. How odd.
@gregoa_ Oh thank!💡I just checked that with my emulator #iTerm2 and with a modifier key I can also click links. Amazing! Except that I cannot handle those massive multi-line links (that the university IT creates running the embedded links through some kind of anti-phishing checker *sigh*). Because of the hard line breaks instead of soft wrapping in mutt, the links terminate after the first line.
#iTerm2 / #fish shell users, what is this awful iTerm2 feature and how do I kill it with fire? I just upgraded my fish shell and now I get this junk in iterm2 and I don't know even what the popup feature is _called_ much less how to kill it.
I've been using MacOS since 2015. Before that I was a serious Linux user. Server, destop, everything. One thing I liked on Linux was xterm. It was really really fast and I could configure it and I was happy. Then I moved to MacOS and my friend @wolf advised me to use #iTerm2. That seems good. Plenty fast. Although my opinion is that it suffers from feature creep. But it held up well. Recently I started noticing it felt sluggish. I do a lot of my work on remote servers (still Linux) over SSH so I was assuming that the sluggishness was a problem with the Internet connection (good ole Xfinity). But then I noticed that it was sluggish even locally. I tried Alacritty and it was fast both locally and for remote connections. So something was up with iTerm2. I googled and found lots of people complaining about it being slow. I found a suggestion that said I should go into iTerm2 settings and disable ‘GPU Rendering’. Well guess what... That solved the problem! iTerm2 is once again fast. I don’t know exactly when it started feeling slow, but it kinda of seems like it was around the time I upgraded to MacOS Tahoe. Maybe that’s the problem, or maybe the iTerm2 guys did something. I really don’t know. But I'm happy now. At least with iTerm2. The rest of Tahoe is kind of a steamy pile of doo-doo. I'm really hoping the next version of Tahoe is something like Snow-Tahoe or something (a nod to Snow Leopard being an update to Leopard focused on performance and stability)
Anyway, I'm posting this so that if you are having an issue with iTerm2 feeling sluggish, maybe you can fix it by going to iTerm2 settings in the General tab and the Magic sub-tab. Look for ‘GPU Renderer' and un-check the box. The setting takes effect immediately.

Rick Dronkers (@RickDronkers)

작성자가 Claude Code용 tmux 패널 기반 노트/세션 모니터를 직접 개발해 공유함. 현재 버그가 있지만 동작하며 hooks와 iTerm2의 deeplink를 활용한 구현을 설명. 작성자는 해당 기능을 Claude 팀(@trq212, @bcherny)이 공식 동반 앱으로 제공하면 좋겠다고 제안함.

https://x.com/RickDronkers/status/2011809087432835238

#claude #tmux #devtools #iterm2 #companionapp

Rick Dronkers (@RickDronkers) on X

Hey @trq212 @bcherny I vibe coded up a tmux pane notes / session monitor for claude code, buggy as fuck but works for now. (leverages hooks and deeplinks into iTerm2 somehow) - but you guys should offer this as a companion app

X (formerly Twitter)
GitHub - hpjansson/chafa: 📺🗿 Terminal graphics for the 21st century.

📺🗿 Terminal graphics for the 21st century. Contribute to hpjansson/chafa development by creating an account on GitHub.

GitHub

Ran into a weird issue with macOS and iTerm 2 while experimenting with #talos over the weekend.

Short version: I had to quit iTerm, reset the local network security permission for it and restart it before I could run talosctl from my a session in iTerm. Maddeningly it was working from a session in Terminal.app

The long version is at https://unixorn.github.io/post/homelab/weird-shit-is-afoot-with-macos-and-iterm/

#homelab #iterm2

Weird shit is afoot with macOS and iTerm

So here’s a fun macOS weirdness I ran into this weekend where I couldn’t connect to a port on another machine from a shell session inside of iTerm, even though I was able to ssh to other hosts.

unixorn.github.io
It was quite annoying I couldn’t use `set-mark` and delete with Backspace in #iterm2, just like I do in #emacs. Normally with #zsh you can only copy the selection. I’ve just found about ZLS widgets, with which apparently I can achieve this functionality and be consistent with my Emacs editing workflow. I’ve made a public gist with the code you need to add to .zshrc, if you, like me, are using backspace to delete selections. https://gist.github.com/varna9000/528829e1bbaccf4745e80f24be145837