Add advice to correctly handle FCC with notmuch #64
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Just switching this to a draft for now. Running into a few issues |
Something that was read-only was prohibiting it from working. This solution is a bit hacky, but I was unable to find the exact location of the error
|
It seems to be working with the fix in 828e7c2 |
|
Closed 1a56754 and fix in #58 (comment) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes how FCC headers are handled with notmuch as described in #58 (similar to the snippet in #58 (comment))
I'm not familiar with mu4e or gnus so not too sure how to address those.
Please let me know if any improvements can be made