Closed ajtruckle closed 4 years ago
does the global linenumber setting work ? if not please check the sourcecode - in case ol
wrapper is used your theme is overriding the line number styles
I don't quite understand this. When I view the page source with IE, there is this first sectionL
Then, there is a second element with the ol
elements you referred too:
And the code also appears again inside that second block as a lump.
So I don't know how to proceed.
If I use this styling:
list-style-position: inside;
Then it seems to work::
I stumbled on that from this StackOverflow question. So is there a place in your plugin that I can add this custom styling, or must we put something into my child theme Additional CSS area?
Could it just be the width of the ol li
objects or something? For example if I change it to Godzilla:
When I use inside
it looks like your samples:
If I use this additional CSS it will work:
#bbpress-forums div.bbp-reply-content ol li
{
list-style-position: inside;
}
But my concern is that the above will affect standard ol li
objects and not limit it to just the EnlighterJS
elements.
I used this:
#bbpress-forums div.bbp-reply-content ol li.odd,
#bbpress-forums div.bbp-reply-content ol li.even
{
list-style-position: inside;
}
Please tell me if it was wrong. It seems the bbpress-forums
styling is overriding the .EnlighterJS
styling in the CSS hierarchy. The above would fail with the .bbp-topic-content
elements too.
This must have come up before for bbPress users. What is the safest way to get this styling correct just for the .EnlighterJS ol li elements?
ol.EnlighterJS > li, ul.EnlighterJS > li{
list-style-position: inside !important;
}
Thank you. That looks like it is working for me and line numbers are showing.
I am using the
[generic]
code formatting option because the code I am showing is a custom language. It looks quite nice "as is":But I wanted to try and display line numbers. So I adjusted the shortcode like this:
[generic linenumbers="true"]
But I could not get it to work. I thought I had followed the documentation right?