-
Notifications
You must be signed in to change notification settings - Fork 264
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
Option to disable automatic "mark as seen" #10367
Comments
Dear @Talkabout, |
For me a checkbox is fine, no time needed, not sure about other people :) Thanks guys! Looking forward to this feature! |
Thanks for clarifying @Talkabout. I've set the feature request to |
Hi @ChristophWurst , I am a developer, yes, and I am also tempted to contribute to this great project. As I am completely new to this it would be great to get some pointers. Unfortunately I cannot say when I will have time to dig into that topic, but having a start point just in case sounds great. Thanks! |
Awesome! See https://nextcloud.com/developer/ for guides and tutorials for a development environment. The logic of "mark seen" can be found at mail/src/components/ThreadEnvelope.vue Lines 635 to 641 in a276629
|
Is your feature request related to a problem? Please describe.
I am using my mailbox as a "task list" and here it is crucial to not auto-mark mals as "seen". Most mail application have an option to disable this and it would be really great to see it here too! I have noticed a closed issue where this topic was mentioned by the only thing that was changed was a delay of 2 seconds beeing added before the "seen" flag is set. That is unfortunately not enought for me.
I really like this app and would love to use it, but without that option it is not possible for me.
Describe the solution you'd like
A very simple solution: add an option "do not mark as seen automatically" that is "false" by default but can be activated in global options.
Describe alternatives you've considered
No real alternatives for me here.
Additional context
No response
The text was updated successfully, but these errors were encountered: