Thanks for the suggestion. I myself also find it a little bit annoying but it disappears fast enough that I never thought of it as an issue. I personally completely agree with making it configurable.

At the moment user can completely turn off all notifications (even the very useful ones):

If there is an option to disable it, I suggest disabling the "screenshot aborted" notification by default, since it seems unlikely to me that someone might need to see such a notification.

Well, this is the part that I disagree for tow reasons:

1. the notification can help the new user to understand the dynamic of the tool. This is extra important when something cancels Flameshot automatically.
2. disabling it by default also means that the current default behavior of Flameshot would change. And we all know how certain people react when something visual changes.

I think it should be Enabled by default, at least for the next few versions, and then we can ask the community how they feel about it. This way the backlash would be minimal.

My use case for aborting a screenshot is usually that the moment I see in the still frame is not the moment desired, and I'd like to quickly abort and capture the right moment instead, without having to await the disappearance of a notification. I can imagine anyone using Flameshot to capture screenshots from a game, or in my case yesterday, a graph in a performance monitoring tool, would prefer to avoid this particular waiting process.

That being said, as long as there is an option, its default value doesn't matter and it works well for my use case.

I just think that if user adoption is a priority, it is more likely for most users to want it disabled by default, especially since a large portion of users who might want to install Flameshot are likely to be gamers. I don't feel too strongly about this though.

Thank you for accepting the feature request, and your plan to ask the community is a level-headed approach.

How do you abort? I have never seen it.

How do you abort? I have never seen it.

This is how:

hm, I tried Esc, no notification. Other notifications appear fine, e.g. after saving.

KDE, Arch Linux.

OK well, I just tried it and there was a notification with the latest Flameshot built from git commit 0bbb952, which is the latest as of writing this comment. You have encountered a bug in your DE which is not caused by this feature request. I also inspected the options and found no option to disable this abort notification, and I can currently still see the notification as usual.

I guess your DE's notifications are bugged somehow or someone else implemented this feature request externally in KDE.

@AlexP11223 there should be a notification but it is possible that:

1. You have turn off notifications in Flameshot
2. In KDE Plasma you have somehow muted notifications (all together or only from Flameshot)

Try removing you Flameshot config (or rename it)