i used the global command

dendron: create global snippet

which i think I need to change anyways because that doesn't transfer with git sync

did you highlight all the lines that you wanted to create a snippet from?

hmm, i didn't have a pre-written snippet selected to make it from, i typed it after the "body" section in the markdown.json file that opened up after naming the snippet

so i never highlighted anything

{
  "table": {
    "prefix": "table",
    "body": [
      "heading1|heading2|heading3
      ---|---|---
      data1|data2|data3"
    ],
    "description": ""
  }
}

is what i'm trying to get

but it only prints the heading line like that, so i made it a single line as a work around

can you try this?

{
  "table": {
    "prefix": "table",
    "body": [
      "heading1|heading2|heading3",
      "---|---|---",
      "data1|data2|data3"
    ],
    "description": ""
  }
}

that does it, thanks @User & @User, i will use the multi quote syntax for other snippets

👍

bonus question: would git-syncable snippets require editing the dendron.code-snippets file?

I believe vscode Settings Sync will let you sync user defined snippets across multiple machines

ah ok, the beta flag on that was scaring me off lol

if it helps, i've been using it for a few months now without any issues 🙂

def, i mean, it's a bit silly that it did in the first place considering my willingness for other "unready" features or programs but yeah, this one got me

we all pick our battles 😅

(eg. i've given up on running arch linux - its endlessly fascinating but just want my drivers to work without thinking about things)

same.. same..

you can also save your snippet definitions in

.vscode

as

*.code-snippets

and use git to keep track of it instead of keeping it in a global snippet.

which is what dendron.code-snippets is basically.

would that be

dendron.code-snippets

or

vault.code-snippets

or something else so that it gets correctly referenced?

I am not sure if the name matters. as long as it is in that directory vscode will recognize it as a workspace level snippet I think

gotcha, sweet

you will have to specify the scope on each snippet here though. AFAIK global snippets are already scope per file but otherwise you need something like

"scope": "markdown,yaml",

in the snippet definition itself.

if i play around with it, the way I understand the best approach would be to copy the dendron.code-snippet file contents and then change all the commands/functions so that they don't have overlap, and use that as training wheels

here are some more info on snippets. The tabstops and placeholders are very useful : https://code.visualstudio.com/docs/editor/userdefinedsnippets

yup. that would work

now, i believe that i can "insert" a template to an existing file, is that correct, or would that be more of a snippet task and the whole note would follow a template?