← Back to context Comment by IshKebab 1 day ago Presumably that discussion is the reason this was fixed. Very bizarre bug tracking policy IMO. 1 comment IshKebab Reply masklinn 1 day ago No, the reason it was fixed is that somebody managed to reliably reproduce the issue: https://github.com/ghostty-org/ghostty/discussions/10244As you can see, there's no hint or evidence they even are on HN let alone saw that discussion.
masklinn 1 day ago No, the reason it was fixed is that somebody managed to reliably reproduce the issue: https://github.com/ghostty-org/ghostty/discussions/10244As you can see, there's no hint or evidence they even are on HN let alone saw that discussion.
No, the reason it was fixed is that somebody managed to reliably reproduce the issue: https://github.com/ghostty-org/ghostty/discussions/10244
As you can see, there's no hint or evidence they even are on HN let alone saw that discussion.