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
How does mutt generate the reply message body? #3488
Comments
The |
That part I understand. I probably wasn't clear enough in my question, but what I'm asking is in two parts:
The only way that occured to me feels very hacky and might not work depending on the answers to the above, but I thought that a Would this work? Is there another way? |
Oh, I got the question now. Perhaps we could look into using the Probably, setting mailcap on send-hook is how I'd work around it. |
I'd find this useful! I find myself often wanting to reply to HTML emails for work and would like to retain the original HTML in the reply body. In this case, I'd probably change my reply format to be more like Outlook's where there's a horizontal rule and then the header information for attribution, the original message HTML (without I've tried a |
Apologies if this has been covered, but I haven't been able to find an answer/solution to what I'm trying to achieve in the documentation or elsewhere in theg github issues.
I want to run a separate command on the original message body when viewing in the pager, and different command on the same message body when replying, to format the quoted body in the editor. This is because I'm converting some attachment types to text to preview in the pager, but I don't want these automatically included in the quoted message body when replying.
The only promising thing I could find about this is setting
edit=<command>
andcompose=<command>
in the mailcap entry for plain/text (in this case), but it seems to have no effect -- editing or composing a message always uses the editor as set in the neomutt configuration.What am I missing?
The text was updated successfully, but these errors were encountered: