will bring this up during out weekly team meeting and see how folks feel about the name

copy-note-link-behavior

I'm having some trouble getting a schema template to work on a child. Here's `cli.schema.yml`:

version: 1
schemas:
# this will match "cli.*" notes
- id: cli 
  # human readable description of hierarchy
  desc: command line interface reference
  # add this to the domain of your schema hierarchy
  parent: root
  # when a schema is a namespace, it can have arbitrary children. equivalent to cli.* glob pattern
  namespace: true 
  children:
    - cmd
    - env
# will match cli.*.env
- id: env
  desc: cli specific env variables
# will match cli.*.cmd.*
- id: cmd
  desc: subcommands 
  namespace: true
  template:
    id: cli.template
    type: note

And here's `cli.template.md`:

---
id: NHl62Y6Qv5LScgWfV0DFv
title: Template
desc: ''
updated: 1633904323320
created: 1633904323320
---

# Heading 1

## Heading 2

When I enter

Ctrl+L

, I create a new note called

cli.cmd.cp

. The new note is created, but the template isn't applied. Is this a bug, or am I doing something wrong?

BTW, if I move the

template

key from the child to the parent and create a note called

cli.foo

, the template is applied.

Try removing

namespace: true

from

cli

and see if that works. Namespace means you will be creating new notes as a child of this, so the schema is expecting

cli.foo

or

cli.foo.cmd.bar

I think.

I'm assuming you want

cli.cmd.foo

I'll try that. I'm using the sample schema that is in the docs and trying to better understand the interaction with templates.

@User That didn't work. I both tried setting

namespace

to

false

and removing it altogether. I'm going to experiment some more.

I created two templates:

cli.template.md

and

cli.cmd.template.md

. Here's my schema:

version: 1
schemas:
- id: cli 
  desc: command line interface reference
  parent: root
  children:
    - cmd
  template:
    id: cli.template
    type: note
- id: cmd
  desc: subcommands 
  template:
    id: cli.cmd.template
    type: note

I tried to boil it down to the essentials. The template doesn't get applied when creating the note

cli.foo

or

cli.cmd.foo

. I would have expected

cli.template

to be used on the first and

cli.cmd.template

to be used on the second.

Slightly more info. I added

namespace: true

back to both the

cli

and

cmd

IDs. I think I was misunderstanding what the namespace key was for. I think I still am, to be fair. I tried creating

cli.foo.cmd

and that pulled in the

cli.cmd.template

template. It's not what I was expecting to happen, however. I would have expected

cli.cmd.foo

to get the template applied. Creating a

cli.foo

file still didn't pull in the template. I must be missing something.

Hi, while publishing can we change the size of the images?

I actually want to include few images in my notes but it covers a large space.

I looked around for a while but couldn't find @User's shortcuts / settings, referenced from some of the videos on youtube. Does anyone have a handy link for those?

image size

Will dendron works with GitLab instead of GitHub?

You mean for sync? Any git service/server would work. You can also publish anywhere that supports static websites, Dendron puts no limits on that.

For the "time" part of date formatting in markdown, what is typically recognized? Is there any kind of standard on this kind of thing - if not, will there be for Dendron? Example:

YYYY-MM-DD HH:mm

format giving

[2021-10-11 20:33]

date time format example

Dendron uses Luxon to format the strings if I'm not mistaken, so any symbols here should work: https://moment.github.io/luxon/#/formatting?id=table-of-tokens

You can also add non-symbol characters which should appear in the output, like the dashes

Hello folks. Is the snapshot feature broken in the current release? When I try to run it, I get "data must have required property 'dest'". Not sure if it is my configuration or something else. 🤔

you're right, it is broken. could you submit a bug report [here](https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=bug_report.md&title=) so we can add it to our roadmap?

Done: https://github.com/dendronhq/dendron/issues/1500 Thanks for the fast reply.

Hi, I'm having a super odd issue. Just cloned my repo on a newly installed Linux distro and when opening the workspace I get this

I think it's something to do with Dendron not having enough permissions to create folder and files. I just tried to

init

a new Dendron workspace and I get

error running comman: EACCES: permission denied mkdir /mydirectory

Sorted. had to change the owner of my repo folder from root to my user

yeah, that would do it. glad you got it worked out

Just curious, if Preview V2 (https://wiki.dendron.so/notes/Lnp1URddmWEWweyf.html) still says "**dev**.enablePreviewV2" because the scroll and export to pdf functions still don't work, then why does Preview (https://wiki.dendron.so/notes/8de4209d-84d3-45f8-96a4-34282e34507d.html) say it is now deprecated and everyone should use Preview V2 instead?