Follow the XDG base directory specification
See original GitHub issueInstead of using config at $HOME/.httpie
, the default should be ${XDG_CONFIG_HOME:-$HOME/.config}/httpie
for unix-based operating systems according to the XDG Base Directory Specification.
As well as keeping the home directory clean, the semantic separation of config, runtime data, cache data and user-local software by the spec is helpful to users and other tools (e.g. backup software).
In terms of migration, I would suggest using the xdg-compilant config location if it exists and falling back to the current default location. This would also negate the need for the $HTTPIE_CONFIG_DIR
variable, so it could be removed/de-emphasised from the documentation but still checked for at least a few versions for compatibility.
Issue Analytics
- State:
- Created 10 years ago
- Reactions:24
- Comments:9
Top Results From Across the Web
XDG Base Directory - ArchWiki
Application Legacy Path Supported Since
ALSA ~/.asoundrc 577df36 · 1.2.3
Android Studio ~/.AndroidStudioX.X Android Studio 4.1
Anki ~/Anki , ~/Documents/Anki
Read more >XDG Base Directory Specification
The XDG Base Directory Specification is based on the following concepts: ... All paths set in these environment variables must be absolute. If...
Read more >Is the XDG base directory specification something to care ...
It follows from /usr/share and /usr/local/share , where /usr/share can be shared between multiple machines, for example from NFS mount, and /usr ...
Read more >XDG Base Directory Specification #338 - rackspace/rack
Please consider following the XDG Base Directory Specification. This means that the default configuration directory would change from ...
Read more >The XDG base directory specification and Rust
The XDG base directory specification exists to address the problem of where programs should look for various kinds of files on a Unix...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
There is already a pull request for this. Any reason against this change?
I just ran into this myself – are there any plans to change the default behaviour here?