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
Is your feature request related to a problem? Please describe.
In rare cases, the line numbers on enhanced code blocks can be confusing. From the EECS 485 P5 spec, there's an example where the output of a code block is a number, which is easily confused with the line number.
Describe the solution you'd like
An option to disable line numbers on an enhanced code block would be nice.
Describe alternatives you've considered
I used {: data-variant="legacy" }, but the downside is an inconsistent look and feel next to the other code blocks.
The text was updated successfully, but these errors were encountered:
Thanks for reporting! I think it's quite reasonable to want to turn line-numbers off. I think I can provide an option to simply not display line numbers, maybe an option like data-variant="no-line-numbers". Or maybe a new option like data-line-numbers="false" or something like that.
Do you need this for this semester? If it can wait for next semester, I'd prefer to address it in a couple of weeks once my personal life settles down a bit :)
Reminder that #165 will be included in the SP/SU 22 release (currently aiming for April 30). I'm going to keep this issue open for now, and will close it after v1.7.0 has been published.
Is your feature request related to a problem? Please describe.
In rare cases, the line numbers on enhanced code blocks can be confusing. From the EECS 485 P5 spec, there's an example where the output of a code block is a number, which is easily confused with the line number.
Describe the solution you'd like
An option to disable line numbers on an enhanced code block would be nice.
Describe alternatives you've considered
I used
{: data-variant="legacy" }
, but the downside is an inconsistent look and feel next to the other code blocks.The text was updated successfully, but these errors were encountered: