Treat signature as markdown, but process w/ nl2br extension#9
Open
nottwo wants to merge 1 commit intoRoguelazer:masterfrom
Open
Treat signature as markdown, but process w/ nl2br extension#9nottwo wants to merge 1 commit intoRoguelazer:masterfrom
nottwo wants to merge 1 commit intoRoguelazer:masterfrom
Conversation
Owner
|
want to write up a test for this? |
This file contains hidden or 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
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.
Hi,
I guess the template idea from #2 wasn't too popular. How about just allowing the signature be .md?
My workplace has standardized on a rich signature that I have complied with by treating the sig as markdown and then adding appropriate styles:
Rather than splitting the signature by newlines & joining with <br>s, I process the signature with the nl2br extension so that text/plain format=flowed & md->HTML versions of the email are presented properly.