feat(org-msg-css-to-file): save current css to file #199
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.
Thank you for sharing this package! As mentioned elsewhere in the repo issues, it brought me back to emailing with emacs.
I wanted to make style changes similar to #116 (edit: also #196) -- border around code blocks. And a bit like #174, I'm looking for an easy way to add my own styling. But was pretty intimidated by starting a file from scratch.
It looks like
org-msg-props-to-style
doesn't need much more to be able to write out a complete file based on the default style. I did that withorg-msg-css-to-string
and added as an interactive interfaceorg-msg-css-to-file
Now I call
org-msg-css-to-file
, make small edits to the file, and setorg-msg-enforce-css
to the new file with my modifications.I also added a test to confirm prop list -> file -> prop list is all consistent. To get that to work a small change to
org-msg-css-to-list
was needed: the property list for an empty css rule has 2 elements instead of 3 (originally the 3rd was null).