You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Unable to override default delimiter processors #386
Is your feature request related to a problem? Please describe.
I wish to override the default delimiter processors the sake of better supporting Discord's markdown quirks. However, I am left unable to override the default options without an exception being thrown due to conflicting characters.
Describe the solution you'd like
I would like to be able to override the two default delimiter processors with my own implementations of the two somehow within the Parser builder.
Describe alternatives you've considered
The current solution for this is to copy the InlineParserImpl class and make your modifications to it, which is definitely not ideal.
I also noticed the same issue, in the InlineParserImpl class the AsteriskDelimiterProcessor and UnderscoreDelimiterProcessor are added by default in calculateDelimiterProcessors.
In my case I need to change the default behaviour, so text surrounded by * is bold, and by _ is italic, but as far as I can see this is not possible without redefining the whole inline parser. I can't add a new delimiter processor because I get an exception: "Cannot add two delimiter processors for char '_' and minimum length 1"
Activity
ChrysanthCow commentedon Jun 30, 2025
As it turns out, I would've needed my own inline parser anyway to handle what I wish to do, but the feature request is still up.
miryam123327 commentedon Mar 27, 2026
Enhance
Charchad commentedon Apr 1, 2026
I also noticed the same issue, in the
InlineParserImplclass the AsteriskDelimiterProcessor and UnderscoreDelimiterProcessor are added by default incalculateDelimiterProcessors.In my case I need to change the default behaviour, so text surrounded by * is bold, and by _ is italic, but as far as I can see this is not possible without redefining the whole inline parser. I can't add a new delimiter processor because I get an exception: "Cannot add two delimiter processors for char '_' and minimum length 1"
rdestefa commentedon May 2, 2026
I made a very rough attempt at this: #432