Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

windows: consider config file under %APPDATA% #622

Closed
SuperSandro2000 opened this issue Apr 3, 2021 · 4 comments
Closed

windows: consider config file under %APPDATA% #622

SuperSandro2000 opened this issue Apr 3, 2021 · 4 comments
Labels
enhancement New feature or request

Comments

@SuperSandro2000
Copy link
Contributor

Is your feature request related to a problem? Please describe.

If wezterm is installed into the global program directory users cannot change the config easily.

Describe the solution you'd like

wezterm should look at config files under %APPDATA%/wzterm/wzterm.lua

Describe alternatives you've considered

Putting the config file under C:\Programs.

@SuperSandro2000 SuperSandro2000 added the enhancement New feature or request label Apr 3, 2021
@wez
Copy link
Owner

wez commented Apr 3, 2021

Both %HOME%/.config/wezterm/wezterm.lua and %HOME%/.wezterm.lua are possible locations for the config file on windows; are those not sufficient? Or perhaps https://wezfurlong.org/wezterm/config/files.html makes it sound like we only look in the executable directory on windows?

@wez
Copy link
Owner

wez commented Apr 3, 2021

(%HOME% isn't literally used, but rather, the home directory for the user)

@SuperSandro2000
Copy link
Contributor Author

Both %HOME%/.config/wezterm/wezterm.lua and %HOME%/.wezterm.lua are possible locations for the config file on windows; are those not sufficient?

I didn't know they work under windows because the doc didn't tell it to me and it isn't obvious that those pats work on windows.

I searched the code quickly for APPDATA but it didn't return any results so I thought it isn't supported.

I think if you clarify the docs this issue can be closed.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 4, 2023

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 4, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants