VSCode sometimes automatically suggests autocomplete based on words it has seen before, it could be that. Glad to see people using the feature!

Something is wrong with the # type tags. How does this source become this in preview?

what preview are you using? v1, v2 or built-in?

V1 and 2, both Dendron

The image is from 2

hmm, having trouble reproducing. can you paste the raw text as well as two lines above and below for context?

Has to be tomorrow, not at a computer

This is a known problem that's fixed in the next version. Sorry for the trouble, thanks for reporting it though! 🙂

I haven't popped in here for a while, and as a result, I realized I hadn't looked at some of the release notes lately. I just wanted to say that I love the v2 preview vs. the older extension!

In Preview v2, I think the rendering of italics needs to be consistent. It is especially inconvenient if an academic reference is in the block quote where the requirement is to emphasize the title (typically with italics)

glad to hear it. the plan is to use it as the default going forward, probably next wee

thanks for the feedback. we will add it to our work items

Hello @here! It's CROP time 🙂 Please vote for your favored crop 👨‍🌾👩‍🌾 1. [Rename Header command](https://github.com/dendronhq/dendron/issues/370) 2. [Create Index Note](https://github.com/dendronhq/dendron/issues/603) 3. [Lookup Vault Filter](https://github.com/dendronhq/dendron/issues/1031) 4. None of these (if there's an issue you'd like to add to rotation, please reply with a github issue) To vote, respond with a 1️⃣ 2️⃣ 3️⃣ or 4️⃣ to this message. voting closes tomorrow

https://github.com/dendronhq/dendron/issues/667 - Right-hand navigation menu: Local table of contents / TOC of a note in Dendron 11ty theme

@User - you can uninstall markdown preview now 🙂

You have impressive memory @User 😛

rather i have a tool that lets me look stuff up 😅

which tools? I'm curious 😄 currently i'm using fibery to hook things up

It's truly amazing how fast the tool evolves! And with the new preview and without markdown preview startup and reload are waaay faster.

Once more thanks for creating such an amazing tool. I start to feel like my use of Emacs: there is always so much more than I'm comfortable using or even k ow about

i have vscode open at all times so i use dendron. you can see my setup here -> https://www.kevinslin.com/notes/7f197479-279e-4b1e-9edd-21bf2da423b0.html#dendron-setup

that's a high honor coming from an emacs user. thank you 🙂

on footnotes. in Preview v2 in v52 the superscript numbers and and the numbers in footnotes render correctly. however, in embedded/referenced notes the footnotes are now outside of the embedded box as it used to be in Preview v1. still needs fixing, please. Also, a minor issue, can the return link be rendered in a less prominent way? a pale arrow on white before was better, it is not an important piece of information and is distracting. i duplicated this comment here https://github.com/dendronhq/dendron/issues/1001

thanks for the feedback. we'll be working on cleaning up preview v2 features for this week and next

Tags docs say (https://wiki.dendron.so/notes/8bc9b3f1-8508-4d3a-a2de-be9f12ef1821.html#autocomplete-intellisense): > To create a tag note,

Ctrl+click

on a tag, or select the tag and use "Dendron: Goto Note" command. Ctrl-clicking a tag that doesn't exist yet doesn't create it,

Ctrl+Enter

works though.

If creating missing tags works the same way as creating missing linked pages, I guess it's related to https://github.com/dendronhq/dendron/issues/1014, but since it's not implemented yet, maybe it shouldn't be in the docs yet.

SVG images are now displaying in V2, but still no grid lines for tables

V2 is still using microsoft's web rendering engine, (like Markdown Preview Enhanced does), I assume - correct? The only way that V2 differs is that the HTML that the web renderer is feed is being generated in a way that is consistent with the way each note is translated in to html for a static web site, (using 11ty currently, but in the future, nextjs)?

yep, table lines is a known issue

as for the rendering, this is actually using nextjs. we export a static react template and hydrate it during the preview phase