This interpretation would be internal to Obsidian, and would not preclude the emitted markdown tables from being valid and properly displayable by other markdown software. This way, Obsidian could begin to render multi-line markdown features such as paragraphs or multi-level lists inside table cells. However, Obsidian could start to treat as \n when interpreting the markdown inside a table cell. Obsidian already supports tags inside tables by rendering them as newlines. And I feel this feature should be be sufficiently “core” to not delegate it to a plug-in.Īs an idea: to make sure that full Markdown compatibility is retained, and the biggest table limitations are lifted, this editing feature could treat the Markdown table contents in a slightly special way. But I see no alternative to implementing a WYSIWY table editing experience, if Obsidian wants to compete with OneNote, Notion etc. Advanced tables are abundant on the Internet, docs, etc, so the inability of Obsidian to take that information in is not good. But another important use case is capturing content from other sources. Keep in mind that creating new tables is only one use case, and a determined individual can tolerate some tinkering in order to make an odd table. So, plugins don’t really solve the problem. But it shares the common flaw with the other plugins: it trips and falls when the table has a or does something slightly funky. The best such plugin that I’ve come across is Table enhancer (which isn’t in the Obsidian plugin store). They inevitably require more steps than just “edit the table”: add a code block with non-markdown (Asciidoc Blocks plugin), or open a separate window (Markdown table editor), or define the table in a separate file (Notion-like tables). However, compared to the table experience of any WYSIWY text editor, they are all clunky. This situation brought about a whole “market” of table-related plugins that try to improve the situation in their own way. This prevents using fully-HTML tables in Obsidian. One can resort to using HTML for formatting, but there’s no replacement for lost internal links or wikilinks. Issue 2: in Obsidian, Markdown ceases to be parsed inside HTML tags. Each table row is represented as a long line of HTML/markdown soup, and requires horizontal scrolling to navigate. Creating or editing tables that contain HTML (or even cells with more than a few words of plain text) is extremely hard. But the usability of this approach goes to zero rapidly as the tables become more involved. This is OK for very simple Markdown tables. Issue 1: editing the table currently involves editing its direct Markdown source.Obsidian’s current implementation exacerbates the limitations of Markdown tables. The workarounds don’t work very well with Obsidian, as I’ll describe below. Since HTML is valid markdown, it’s possible to create fully advanced tables. An even more radical approach is using HTML for the entirety of the table. Drawbacks: only one level of indentation is realistically possible merging cells is still unattainable. Lists can be simulated using ad-hoc bullets.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |