-
Notifications
You must be signed in to change notification settings - Fork 285
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
Use of appdirs yields worse behavior on osx #346
Comments
@carlwgeorge @kitdarko Does any of you have an idea how to fix it? |
What you've described sounds like the exact intention of appdirs: use the platform-appropriate directory. While ptpython could choose to allow overriding this behavior by honoring |
I agree, there's an ongoing (slow) conversation in appdirs, but it has seemed so far, like the maintainer doesn't seem particularly amenable to the change. I primarily raised the issue here because the choice to use today's appdirs regresses usability (imo) of ptpython specifically. I'd be happy to submit a PR on either project if I expected anyone to merge it. |
ActiveState/appdirs#78 being the aforementioned issue. The final comment indicating that appdirs appears to be unmaintained (ActiveState/appdirs#79) I'll also say that the readme is currently incorrect:
so it's not obvious where i should symlink my config to, as is. |
Personally I think the README should be fixed, but do not agree that prompt-toolkit should treat macos like Linux, since the entire point of appdirs is that well, technically, it's correct for these to go in That doesn't mean everyone likes that, or that it's universal to do so. But yeah ptpython should not make that choice. Instead I think the right solution is ptpython (and any application) should have its own envvar, and that takes precedence over appdirs when set. This way, users like @DanCardin (and indeed myself!) who wish to make macOS match Linux can do so by setting |
Really this needs to go in Library/ApplicationSupport, so dot will need modifying, but hopefully prompt-toolkit/ptpython#346 gives me an envvar to use instead.
In particular allows macOS users to follow the Linux convention instead of the macOS one, of putting config back in ~/.config. Closes: prompt-toolkit#346
PR in #399 for the latter way, comments of course welcome. |
I mean, I think that any user who is setting But i'll take what i can get. Any way to opt into a specific location is a win in my book. |
In particular allows macOS users to follow the Linux convention instead of the macOS one, of putting config back in ~/.config. Closes: #346
Showing my support here for using Something feels weird about
Isn't that odd - what is the significance of Adding an environment variable is a small cost, and I appreciate that the addition has been made to allow for setting a config dir, but it does indeed feel dirty. Using
Is this something the maintainers would be interested in considering? |
Really this needs to go in Library/ApplicationSupport, so dot will need modifying, but hopefully prompt-toolkit/ptpython#346 gives me an envvar to use instead.
appdirs
ignores XDG_CONFIG_HOME on macos and unconditionally wants to put the config in a macos-specific folder location.Annoyingly there's an appdirs issue which raises this and they just suggest that you artificially set the OS to be linux instead of darwin if you want linux behavior.
I'm going to also comment on their appdirs, but since this affects the behavior of ptpython specifically, i guess for now it'd be ideal for me if ptpython were do something like
The text was updated successfully, but these errors were encountered: