Mark Barton <mbarto...@gmail.com> writes: >> Not so easy for src block and other verbatim text - there is simply no >> way to escape "|" in tables. > > ... > In your example of the src block, I don't normally make those headers, but > could the pipe char be replaced only in the clock table? If clock table links > are turned on then the header link should point to the header and just the > description changes.
That's one option. Another observation is that Org parser does not even allow inline src blocks inside table cells. So, it might make more sense to remove all the inline src blocks before creating the table cell. Although, unlike inline src blocks, verbatim/code markup is allowed. And something like =this|is|verbatim= is problematic - similar to inline src blocks, altering the "|" inside may change the meaning. To be clear, it is quite easy to write some kind of `org-table-cell-escape' that will make sure that text inserted into a table cell will not cause problems with table formatting. However, I'd prefer to solve this problem in a more generic way, alongside with similar problem of escaping "=" inside verbatim markup, edge cases with link paths like =should not be verbatim [[https:/example.com/?foo=?]], yet it is and other edge cases. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
