-
Notifications
You must be signed in to change notification settings - Fork 100
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
Cache/data files in $XDG_CONFIG_HOME
#582
Comments
@thunktone You are right. |
A related suggestion: I think it would be very useful to add options for specifying the paths and filenames for all files individually, either just via the command line when calling vimb (analogously to '--config') or optimally as settings, so that the files can be changed dynamically. This would in particular be very nice for the style.css and script.js files, which could then be changed via auto-commands, depending on the URI. |
This issue has been automatically marked as stale because it has not had activity within the last 60 days. It will be closed after 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity since it was marked as stale. Thank you for your contributions. |
I think that issue should be reopened (it is not really stale, just not worked on). |
I'm not sure which files belong to config, data or to cache directory. I see the files as configuration that I inspect and edit with editor - except of the cookies.db. |
IMHO:
|
Do not store all files in XDG_CONFIG_HOME.
Do not store all files in XDG_CONFIG_HOME.
Like @iamleot suggested the config, script.js and style.css are kept in
|
Thank you @fanglingsu! |
I just found my browsing history, cookies etc in
~/.config/vimb
. They really belong in$XDG_CACHE_HOME
or possibly$XDG_DATA_HOME
. Fortunately I spotted this before commiting the files to my config git repository. Please change this before someone accidentaly publishes their browsing history on github or something. See freedesktop basedir spec.The text was updated successfully, but these errors were encountered: