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
Here's an example on Linux of the current behavior. Run ockam project ticket --help. It produces the following output in the Examples section. Note that it does not have any syntax highlighting.
Desired behavior
With syntax highlighting via syntect crate, it should be whatever syntect produces for sh syntax set.
Here are some places to get started in the code.
process_terminal_docs() - This function is responsible for taking the CLAP help text output and formatting it just before displaying it to stdout.
nazmulidris
changed the title
[public-pending] Syntax highlighting for fenced code blocks, in command help output, on Linux works
yntax highlighting for fenced code blocks, in command help output, on Linux works
Jan 27, 2024
nazmulidris
changed the title
yntax highlighting for fenced code blocks, in command help output, on Linux works
Syntax highlighting for fenced code blocks, in command help output, on Linux works
Jan 27, 2024
Current behavior
Currently, for Ockam Command CLI help output, the syntax highlighting for fenced code blocks has been disabled. It didn't work properly on Linux.
Here's an example on Linux of the current behavior. Run
ockam project ticket --help
. It produces the following output in the Examples section. Note that it does not have any syntax highlighting.Desired behavior
With syntax highlighting via syntect crate, it should be whatever syntect produces for
sh
syntax set.Here are some places to get started in the code.
process_terminal_docs()
- This function is responsible for taking the CLAP help text output and formatting it just before displaying it to stdout.FencedCodeBlockHighlighter::process_line()
- This is the function that is generating the unexpected and undefined color spans and newlines in the output.The text was updated successfully, but these errors were encountered: