Thanks. Any ETA on a new release that would include this and other pending fixes?
Randomly showing "Action could not be completed" precisely is the problem. This can sometimes be mitigated by doing ctrl-Z a few times and shift-ctrl-Z onself back to the desired result, but not always, and it really disrupts one's editing session.
Version 3.12.4 still has this problem.
$ lintian-explain-tags privacy-breach-generic
N:
W: privacy-breach-generic
N:
N: This package creates a potential privacy breach by fetching data from an external website at runtime. Please remove these scripts or external HTML resources.
N:
N: Please replace any scripts, images, or other remote resources with non-remote resources. It is preferable to replace them with text and links but local copies of the remote
N: resources are also acceptable as long as they don't also make calls to remote services. Please ensure that the remote resources are suitable for Debian main before making local
N: copies of them.
N:
N: Visibility: warning
N: Show-Always: no
N: Check: files/privacy-breach
N:
As per enclosed patch, the URL to Creative commons is removedprivacy-breach-C-legal.patch
3.12.2 was released over a year ago. It's high time to produce the next release.
Publishing a new release very much is an actionable point. Thank you for your understanding.
3.12.2 was released over a year ago. It's high time to produce the next release.
Just reported the same. This used to work correctly. Nowadays, for some reason, the date format seems hardcoded and it disregards customization. This messes up my workflow severely enough that I had to revert to an earlier release (3.11.2 which is what Debian/stable has) just to have usable renaming.
It should also be noted that %F used to mean "filename without the extension" which is why my recipe had %E as well. Now it seems to mean "whole original filename WITH extension" instead.
@hadess, Telling people to go and start coding plugins if they need speeds other than those you decided to include is extremely inconsiderate. Speeds like 0.5 and 2.0 are obvious needs from a user's perspective. Please think before you write this sort of replies to feature requests.
The slowest speed there is 75%. That's not too useful. 25% and 50% would be more useful.
Reopening. The "fix" doesn't memorize the file renaming recipe.
I've configured a customized file renaming recipe. Every now and then, gThumb forgets it and seemingly reverts to its default.