Yes, I agree. Ghostty et al don't open-on-click, but on hover they'll show you the URL and there's a keyboard shortcut + click to open. This is much better UX than disabling OSC8.

▲

tjoff 2 hours ago | parent [-]

Yeah, because more complexity where you don't expect it doesn't cost anything?

Up until 5 hours ago this fix was not present:

> The displayed target is sanitized so invisible and line-breaking characters cannot conceal the effective destination.

https://github.com/ghostty-org/ghostty/security/advisories/G...

The sensible default is to have it turned off. And by the looks of it Ghostty versions before this you couldn't even turn it off.

▲

reissbaker an hour ago | parent [-]

"One implementation of a feature had a bug, therefore this feature should be turned off on all implementations by default" is probably not going to convince people who think the feature is good.

If you don't want to be able to have clickable hyperlinks, by all means use Konsole — no one is forcing you to use Ghostty. But if you want to know why people like Ghostty's approach vs Konsole's, it's because Ghostty pushes terminal emulator features forward and is low latency. Konsole is low latency and adopts some but not all features that other people invent. It's a noticeable difference and so people who like the feature part of the former like Ghostty/WezTerm/Kitty more than Konsole. If you don't care or dislike that part, and want a more conservative terminal (that is also low latency), Konsole and many others further on the conservative spectrum exist.

	▲	hnlmorg 23 minutes ago \| parent [-]
		It’s not just one implementation. Browsers have been struggling to get this right for decades and now we are destined to repeat all the same problems all over again with an entirely new syntax of inlined markup.