You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add the option to use a wildcard character (like "*") for specifying file paths in the inclusion list and the exclusion list.
Example:
Case 1: "/home/user/.cache/Theme.v1.2.3"
Case 2: "/home/user/.cache/Theme.v*"
Case 2 would include any file or directory paths whose string matches the part before the "*" operator.
This would be very useful in cases where a filename is versioned and thus changes often with updates.
For example, if you want to empty the .cache folder, but exclude certain theme cache files (which are versioned) in order to avoid the desktop crashing on cleanup, you currently have to manually re-add the file after every update because the name changed.
This wildcard operator lets you target the part of the file/directory path that stays the same between updates, removing the need to manually re-add the affected files every time a part of their name changes.
Even without the option to enter file paths directly as text in the GUI, it could be used when editing the config file directly.
The text was updated successfully, but these errors were encountered:
Add the option to use a wildcard character (like "*") for specifying file paths in the inclusion list and the exclusion list.
Example:
Case 1: "/home/user/.cache/Theme.v1.2.3"
Case 2: "/home/user/.cache/Theme.v*"
Case 2 would include any file or directory paths whose string matches the part before the "*" operator.
This would be very useful in cases where a filename is versioned and thus changes often with updates.
For example, if you want to empty the .cache folder, but exclude certain theme cache files (which are versioned) in order to avoid the desktop crashing on cleanup, you currently have to manually re-add the file after every update because the name changed.
This wildcard operator lets you target the part of the file/directory path that stays the same between updates, removing the need to manually re-add the affected files every time a part of their name changes.
Even without the option to enter file paths directly as text in the GUI, it could be used when editing the config file directly.
The text was updated successfully, but these errors were encountered: