Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.
@ancebfer commented on this pull request.
In data/filedefs/filetypes.asciidoc:
> @@ -1,35 +1,33 @@ # For complete documentation of this file, please see Geany's main documentation [styling] -# no syntax highlighting yet +# Edit these in the colorscheme .conf file instead +default=default +strong=default,bold +emphasis=default,italic +header1=keyword_1 +header2=keyword_1 +header3=keyword_1 +header4=keyword_1 +header5=keyword_1 +header6=keyword_1 +ulist_item=default +olist_item=default +blockquote=default,italic
This is the desired behavior for "ulist_item", "olist_item" and "blockquote" elements. They are assigned to "default" because they are not colored in VScode. And "blockquote" element is shown as italic in VScode.
It's a matter of personal taste. Of course, "ulist_item", "olist_item" and "blockquote" elements can be set to "tag_unknown" to match markdown scheme.
You are right, a global VScode color scheme is the best solution. But, in my personal case, I prefer to stay on default Geany color scheme and only "hack" AsciiDoc colors (in my local configuration) to match VScode because I use both editors and I like to have same appearance on both.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.