summaryrefslogtreecommitdiff
path: root/IDEAS.org
diff options
context:
space:
mode:
authorDirk-Jan C. Binnema <djcb@djcbsoftware.nl>2024-03-02 19:30:17 +0200
committerDirk-Jan C. Binnema <djcb@djcbsoftware.nl>2024-03-02 19:31:04 +0200
commit7af9cb205e073e2938cd98d6eec01f42bfb28756 (patch)
tree5f25d2fd5775e302eb3074d5379b876efebb7a2c /IDEAS.org
parent8afe3e11a2ad245db4340271cc02c45da10f56db (diff)
update IDEAS.org
And refer to it in the RFE issue template.
Diffstat (limited to 'IDEAS.org')
-rw-r--r--IDEAS.org19
1 files changed, 19 insertions, 0 deletions
diff --git a/IDEAS.org b/IDEAS.org
index 5bb57ee..60d10d6 100644
--- a/IDEAS.org
+++ b/IDEAS.org
@@ -5,6 +5,11 @@ Ideas for future enhancements. We collect those here so they don't clutter up
the Github issue list, i.e. without any clear plan for adding in the near
future.
+- Ability to _mute_ message threads. This is useful but also requires quite bit of
+ extra infra; we could add some blacklist for "muted" messages, perhaps on the
+ 'mu server' side, but then we'd need some way to manage that (ie., unmute).
+ https://github.com/djcb/mu/issues/636
+
- Support automatic handling for List-Unsubscribe headers
https://github.com/djcb/mu/issues/2623 This seems useful, but probably
requires a lot of testing to get right.
@@ -17,3 +22,17 @@ future.
- Support *creating* calendar invitations.
https://github.com/djcb/mu/issues/2308
Shouldn't be _too_ hard, for someone that uses the functionality.
+
+- Support mu4e-mark-handle-when also for when leaving emacs
+ (kill-emacs-query-functions).
+ https://github.com/djcb/mu/issues/2649
+
+- Make sorting stable if there are multiple messages with the same date. We
+ _could_ do this by adding some random millisecs to each messasge's timestamp; _or_
+ complicating the search (i.e., the message hash?). Maybe leave as is?
+ https://github.com/djcb/mu/issues/2527
+
+- Include "message summary" in message information, for display in the headers
+ buffer: https://github.com/djcb/mu/issues/1821 It's not so easy to get a
+ useful one line description... perhaps the first line after the "Dear x,"?
+ Moreover, this requires new functionality on the headers-view side as well.