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

How to Clear History and Cookies After the Browser Closes? #702

Open
ghost opened this issue Jan 15, 2022 · 4 comments
Open

How to Clear History and Cookies After the Browser Closes? #702

ghost opened this issue Jan 15, 2022 · 4 comments
Labels

Comments

@ghost
Copy link

ghost commented Jan 15, 2022

I want vimb to clear all history, logins, cookies and stuff like that when all vimb windows have been closed.

@fanglingsu
Copy link
Owner

@amarakon You can use the :cleardata or :cl to clear all memory-cache, disk-cache, offline-cache, session-storage, local-storage, indexeddb-databases, plugin-data, cookies and hsts-cache.
Note that this affects all running instances of vimb. But there is at the time no logic to do something in vimb which is only executed if all windows are closed. The instances of vimb run as separate processes and do nto know anything about each other. So if you want to do this only if all windows are closed you have to do this outside of vimb. But in this case you have to launch vimb to run the :cleardata command. Not tested, but this might be possible with vimb -C 'cleardata' -C 'quit' which runs the command an quits vimb right after.

@ghost
Copy link
Author

ghost commented Jan 21, 2022

Yep it works. But the only thing it didn't clear was the sites I've visited, and I want it to clear that too.

@fanglingsu
Copy link
Owner

@amarakon You mean the entries added in .local/share/vimb/history. You could delete this file by yourself. And to be save you should also delete the .local/share/vimb/closed which stores the last closed-max-items closed urls. Or you could :set closed-max-items=0 so that there is no url written to the file when vimb is closed.

@stale
Copy link

stale bot commented Apr 16, 2022

This issue has been automatically marked as stale because it has not had activity within the last 60 days.

@stale stale bot added the stale label Apr 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant