From 9f39d78a71e302f99b4b4db1224cfef6f584a6fd Mon Sep 17 00:00:00 2001
From: "Dirk-Jan C. Binnema" <djcb@djcbsoftware.nl>
Date: Wed, 1 Nov 2023 19:33:33 +0200
Subject: [PATCH] mu4e-compose: use decoded message for replying

Or From: etc. would use some undecoded version with some
=?iso-8859-1?Q?.... blobs.
---
 mu4e/mu4e-compose.el | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/mu4e/mu4e-compose.el b/mu4e/mu4e-compose.el
index 10feb456..8f1a568b 100644
--- a/mu4e/mu4e-compose.el
+++ b/mu4e/mu4e-compose.el
@@ -28,13 +28,13 @@
 ;; in the mu4e context.
 
 
+;; Code
 (require 'message)
 (require 'mu4e-obsolete)
 (require 'mu4e-server)
-(require 'mu4e-actions)
 (require 'mu4e-message)
 (require 'mu4e-context)
-(require 'mu4e-window)
+(require 'mu4e-folders)
 
 
 ;;; User configuration for compose-mode
@@ -677,7 +677,7 @@ PARENT is the \"parent\" message; nil
                       gnus-message-replyencrypt nil
                       gnus-message-replysignencrypted nil)
           (when parent
-            (insert-file-contents (plist-get parent :path)))
+            (insert (mu4e-view-message-text parent)))
           (goto-char (point-min))
           ;; annoyingly, various message- functions call `message-pop-to-buffer`
           ;; (showing the message. But we're not ready for that yet. So