I want to share a thought about a thing that I really find annoying using Obsidian. I usually use Callouts to gather parts of my notes, and each time I edit them the layout in Live Preview messes out, showing the code like Source Mode. I thing a Live Preview editing mode would really increase the overall experience using Callouts especially where inside the the are links, attached files or images, or even when multiple callouts are concatenated. I mean it should work like the new table editor or code block, where layout remains during editing.
Use case or problem
Callouts in âedit modeâ shows all the text as in âsource modeâ
Proposed solution
Editing Callouts should maintain the UI as in âLive previewâ
If one wants to only edit the content of the callout, a switch back to the source mode is not necessary. Only use source mode for the most nested callout block the cursor is currently in. Editing âcallout block structureâ could be done similar to lists, via tabbing.
At least making this behaviour optional, would be much appreciated.
Iâm having the same issue right now. Would love to be able to edit callouts like any other text/lists/etc. Thereâs already a âedit this blockâ button on them. I can use that if I want to see the markdown.
Same. I absolutely hate trying to edit a callout because clicking on it suddenly means all the coding expands, all of it is highlight and i have to scroll and click where i wanted the cursor to be again and if i want to put a bunch of code in there like html or am using a plug in to make columns with callouts⌠I have to scroll through it all, and itâs such a pain. It also interferes with certain things like toggles and text box inputs, such as with the meta bind plug in, where I canât click them in editing without it opening the entire callout source. Please just let us be able to edit it like other things and only show the code if we hit the source button.
I would like to propose an enhancement of the existing Table editing feature added with 1.5.3 update.
Use case or problem
At the moment it is not possible to edit table cells of any table nested inside callouts.
Focusing on a table inside a callout while in live preview mode results in the source code of the parent callout to be revealed (see below).
Proposed solution
Allow for tables nested inside callouts to be edited in the same way regular ones are.
Current workaround (optional)
Edit tables from the source code or do not use tables inside callouts.
Ran into this problem a few times. Itâs annoying but I think the fix wonât be trivial, since the callout block is being turned into source as youâre editing it, but the table inside the block is supposed to be previewed (hence the contradiction).
So hereâs my easy workaround: make your table nice and neat outside the block, then simply cut and paste it into the callout block.
That is until the Obsidian team finds a way to resolve that contradiction.
Just have live preview treat admonition boxes the same way it treats quote boxes and render latex in them.
Current workaround (optional)
If the math is sufficiently complicated that I donât want to deal with not being able to see a preview, I sometimes write it first as a quote block and then only add the [!Proof] part when Iâm done.
It renders it fully and correctly in the live preview when your cursor is outside it, but while youâre editing the admonition it displays in live preview basically the same way a quote block does, except for the fact that it doesnât render the latex.
Also, I wrote another plugin that focuses on this specific problem, so I will remove this feature from LaTeX-like Theorem & Equation Referencer in the near future.
As I said here callout doesnât seem to support image when editing. But, the quote block do. Also, as some markdown clutter disappear, it quickly becomes difficult to work with image in a callout.
Proposed solution
Two solution :
Add support of image in callout when editing, maybe impossible because of the way there are embedded.
Keep completely the markdown mark as ![[]] or ![]() and $$.
Current workaround (optional)
I looking for maybe a css snippet that can help me.
