:sanitize command #58

Open
The-Compiler opened this Issue Oct 1, 2014 · 3 comments

Comments

Projects
None yet
2 participants
Collaborator

The-Compiler commented Oct 1, 2014

There should be a :sanitize command optionally taking a list of things and a time range, which cleans up things then.

"things" mean:

  • cookies
  • cache
  • icons
  • HTML5 stuff
  • history

@The-Compiler The-Compiler self-assigned this Oct 1, 2014

The-Compiler added a commit that referenced this issue Jun 29, 2015

tox: Update pytest-qt to 1.5.0.
Upstream changelog:

* Fixed log line number in messages, and provide better contextual information
  in Qt5 (#55, thanks @The-Compiler);
* Fixed issue where exceptions inside a `waitSignals` or `waitSignal`
  with-statement block would be swallowed and a `SignalTimeoutError` would be
  raised instead. (#59, thanks @The-Compiler for bringing up the issue and
  providing a test case);
* Fixed issue where the first usage of `qapp` fixture would return `None`.
  Thanks to @gqmelo for noticing and providing a PR;
* New `qtlog` now sports a context manager method, `disabled` (#58). Thanks
  @The-Compiler for the idea and testing;

This comment has been minimized.

Show comment Hide comment
@The-Compiler

The-Compiler Sep 10, 2015

Collaborator

There also should be a setting to auto-sanitize on shutdown.

Collaborator

The-Compiler commented Sep 10, 2015

There also should be a setting to auto-sanitize on shutdown.

@The-Compiler The-Compiler removed their assignment Oct 1, 2015

This comment has been minimized.

Show comment Hide comment
@Earnestly

Earnestly Oct 23, 2015

A command like :sanitize and time ranges are too corse and almost never the intention. E.g. who remembers a specific time range for potential content to delete? Moreover what if the content is mixed and some wants to be kept and some removed?

This consideration probably ties in with The-Compiler#1051

I think the way firefox handles this is going to be ultimately more appropriate than time range, i.e. you can choose to completely forget a specific website.

A command like :sanitize and time ranges are too corse and almost never the intention. E.g. who remembers a specific time range for potential content to delete? Moreover what if the content is mixed and some wants to be kept and some removed?

This consideration probably ties in with The-Compiler#1051

I think the way firefox handles this is going to be ultimately more appropriate than time range, i.e. you can choose to completely forget a specific website.

EliteTK added a commit to EliteTK/qutebrowser that referenced this issue Jan 23, 2016

history: Add clear() method and history-clear command
WebHistory now has a clear() method which is also a command
(history-clear) which clears the qutebrowser history using the new
lineparser clear() method and emits a cleared signal.

The completion model urlmodel connects to the WebHistory.cleared signal
and clears its history category completion list.

I am adding this as a temporary fix before #58 or #1051 get implemented.

@The-Compiler The-Compiler added the easy label Jan 8, 2018

This comment has been minimized.

Show comment Hide comment
@The-Compiler

The-Compiler Jan 8, 2018

Collaborator

Marking this as "easy" as at least a way to delete all cookies and a setting for things to delete on shutdown shouldn't be too hard.

Collaborator

The-Compiler commented Jan 8, 2018

Marking this as "easy" as at least a way to delete all cookies and a setting for things to delete on shutdown shouldn't be too hard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment