Config per window / panel / path instance, instead of one across all windows #10141
Unanswered
lofimichael
asked this question in
Feature Requests, Ideas
Replies: 2 comments
-
|
Made a PR for this: |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Rather than making Ghostty react to the CWD (which comes with its own suit of problems regarding e.g. local and remote machines) I think a better way of implementing this would be to use something like Direnv to run scripts when the user switches into a specific directory, which can change Ghostty's configs on the fly via #2353. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there!
I'd like for the ability to selectively apply certain configurations (i.e. fonts, shaders, etc.) per window/panel, or per detected directory.
Alongside one global config, having idiosyncratic configs be applied (i.e. if terminal path matches XYZ, apply config-1-path, etc; in this example, by default, all windows use a wildcard path and thus the default config path).
As a Claude Code user, I enjoy having two different projects open at once - one for writing, and another for code implementation; having different font sets, panel borders, aesthetics, etc. for these in the same Ghostty application instance would be delightful.
(I recognize this probably introduces a sort of "shouldUpdate" check on changing directories if enabled, which does have some performance implications, but one I am perfectly fine as a user with configuring/accepting myself)
Beta Was this translation helpful? Give feedback.
All reactions