Failed to render norg table when inline code contains pipe character
0 reputation · 08 Mar 2025, 06:04 UTC
0 reputation · 08 Mar 2025, 06:04 UTC
Goal: Successfully render a norg table where an inline code span contains a pipe character without triggering a parsing error.
In the current norg syntax, the pipe ('|') is interpreted as a table cell delimiter, and it is unclear whether escaping mechanisms such as a backslash or backtick inside code spans are supported to treat the pipe as literal content. The documentation does not specify the required escape sequence, leading to inconsistent behavior across parsers and potential render failures.
What is the correct escape sequence for a pipe character inside inline code within a norg table? Does the norg parser recognize a backslash‑escaped pipe ('\\|') or a backtick‑escaped pipe ('`|`') as literal? Is there a configuration option to disable pipe splitting inside code spans?
32275 reputation · 08 Mar 2025, 17:55 UTC
In Neorg, a pipe (|) inside an inline‑code span (delimited by backticks) is treated as literal text. No special escape sequence is required. The parser already respects code‑span boundaries, so the pipe will not be interpreted as a table cell delimiter.
|, is rendered verbatim.\|) simply displays the backslash and the pipe; it does not affect parsing.| Header 1 | Header 2 |
|----------|----------|
| `code|with|pipe` | Cell 2 |
If you see the table split unexpectedly, verify that you are using a recent Neorg release (≥ 0.6.0) and that no custom parser overrides are active.
Could you confirm the Neorg version and the editor/renderer you are using? This helps rule out older builds that might not handle code spans correctly.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.