Why is ```console highlighting shell keywords?

[vermiculus]

From my read of pygments/lexers/shell.py, BashSessionLexer isn't adding keyword information, so I'm not sure how .k is getting applied to in (in foo in bar).

Example:

```console
# After creating your foo in bar, check out baz
$ qux checkout baz
Checking out baz...
Done!
```

is getting processed as

<div class="language-console highlight">
  <pre>
    <span></span>
    <code>
      <span class="gp"># </span>
      After
      <span class="w"> </span>
      creating
      <span class="w"> </span>
      your
      <span class="w"> </span>
      foo
      <span class="w"> </span>
      <span class="k">in</span>      <--- oh no!
      <span class="w"> </span>
      bar,
      <span class="w"> </span>
      check
      <span class="w"> </span>
      out
      <span class="w"> </span>
      baz

I can't find an exact example, but it doesn't appear this should be the behavior (hashicorp docs source, rendered). I would generally expect there to be no further lexing after a $ or # is seen and for the entire remaining text to just show up as a single, simple string.

Is this the fault of _innerLexerCls = BashLexer in BashSessionLexer? Is there a way to get the output I'm expecting (without redefining a BUNCH of classes just for language-console)? Or is this a bug in Pygments that I should report upstream?

Here's my config:

# ...
markdown_extensions:
  - toc:
      permalink: "#"
      permalink_title: "Link to this section"
  - abbr
  - attr_list
  - admonition
  - def_list
  - footnotes
  - smarty
  - pymdownx.details
  - pymdownx.highlight:
      pygments_lang_class: true
  - pymdownx.inlinehilite
  - pymdownx.snippets:
      auto_append:
        - docs/glossary.inc.md
  - pymdownx.tabbed:
      alternate_style: true
  - pymdownx.emoji:
      emoji_index: !!python/name:materialx.emoji.twemoji
      emoji_generator: !!python/name:materialx.emoji.to_svg
  - pymdownx.superfences:
      custom_fences:
        - name: mermaid
          class: mermaid
          format: !!python/name:pymdownx.superfences.fence_code_format

[facelessuser]

I think generally this would be a question for Pygments, not Material.

[vermiculus]

I might've forgotten the punchline in my original post – is there anything in Material that could be post-processing the output from Pygments that could feasibly be having this effect? Anywhere I can continue my own investigation?

[facelessuser]

No, it is just Pygments. I assume comments aren't really considered in the console output as people don't comment command line inputs: Check out how Pygments process it:

https://pygments.org/demo/?lexer=console&style=bw&formatter=html&code=%23+After+creating+your+foo+in+bar%2C+check+out+baz%0A%24+qux+checkout+baz%0AChecking+out+baz...%0ADone%21

Notice the bold in:

[vermiculus]

people don't comment command line inputs

They do…, but that gave me a thought… In a real session, you still get $ as your prompt. BashSessionLexer is almost certainly treating # as the 'root' prompt (as opposed to $ being the normal user prompt). Putting a $ in front (as would be seen in a real session) gives the desired output:

Also, TIL about pygments.org/demo! I never thought to look for such a thing. Certainly very helpful in determining that it's a pure Pygments 'issue' – though in my case it looks like it was good old user error 😄 Thanks!

[facelessuser]

Oh, that makes sense.