Make sure all code listings have references #374

New Issue

GiteaMirror · 2026-03-22T15:38:08-05:00

GiteaMirror commented

2026-03-22 15:38:08 -05:00

Originally created by @profvjreddi on GitHub (Apr 20, 2025).

Originally assigned to: @hzeljko on GitHub.

I noticed that I did not actually end up linking code references with cross-references. Instead, I just say the below code or the code above. However, we should actually be referring to them specifically using references and cross-references.

Originally created by @profvjreddi on GitHub (Apr 20, 2025). Originally assigned to: @hzeljko on GitHub. I noticed that I did not actually end up linking code references with cross-references. Instead, I just say the below code or the code above. However, we should actually be referring to them specifically using references and cross-references.

GiteaMirror added the area: book type: improvement labels 2026-03-22 15:38:08 -05:00

GiteaMirror closed this issue

2026-03-22 15:38:08 -05:00

GiteaMirror referenced this issue

2026-04-11 07:46:57 -05:00

[GH-ISSUE #374] CO2 (2 as a subscript) #1393

GiteaMirror referenced this issue

2026-04-19 12:03:38 -05:00

[GH-ISSUE #374] CO2 (2 as a subscript) #4013

GiteaMirror referenced this issue

2026-04-21 21:20:20 -05:00

[GH-ISSUE #374] CO2 (2 as a subscript) #5355