mirror of
https://github.com/ghostty-org/ghostty.git
synced 2025-07-18 09:46:07 +03:00
6373399e59
When one develops Ghostty while using Ghostty it could lead to an interesting conundrum: the freshly built Ghostty would use the parent Ghostty's resources, which would be stale and not reflect any new changes to resources. This is especially bad for translators, since their translations would not be reflected in the newly built Ghostty if they happen to run it under older Ghostty, which is not only counterintuitive and also painful in terms of workflow. Now, on debug builds we always try to use the terminfo detection method first in order to locate the zig-out/share/ghostty folder, and only fall back to GHOSTTY_RESOURCES_DIR if the executable is for some reason no longer in zig-out. You can test this behavior by manually moving the Ghostty executable out of zig-out, and then launching it with and without Ghostty.