https://www.dendron.so/ logo
Powered by
# questions
  • k
    i think your running into last week's breaking change with date formats: https://dendron.so/notes/d508e0f9-8bbe-43b4-83c1-0ff022b1d4fb.html#breaking-changes
  • k
    we don't currently support MDX though its something we're looking into with transitioning the preview to nextjs (https://dendron.so/notes/17c61d62-f92e-4002-b8fe-9c05686e4bf9.html)
  • h
    that will be interesting. mdx was what led me to look more into markdown based knowledge management, and that's how I found Dendron 😄
  • k
    i'm seeing it too. i think this is due to an experimental markdown-it feature we're testing out that doesn't seem quite it. just released 0.25.1 which fixes the outline stuff
  • h
    @User I found an extension error like "ctx d:run xxx no such file or directory" as seen in github issues: https://github.com/dendronhq/dendron/issues/457. I cleared the local cache and reinstalled vscode and dendron and the issue was not solved.
  • k
    hey, thanks for bringing this up. i did some digging and this is a bug on our side when initializing the extension for the first time. pushed out the fix in 0.25.2 which should be live in a few minutes
  • c
    I spotted a possible publishing bug in `0.25.0`: when I rearranged my 
    dendon.yml
    to change which hierarchies get published by default, and set 
    root.md
    as the 
    siteindex
    , a few surprising things happened, so for now I'll roll back my published site to v.24 - the navbar contains the names of the two hierarchies that I did not include in the 
    sitehierarchies
    array - the generated links (in nav bar and in the root page) are relative to 
    localhost:8080
    instead of relative to the site root (preview link: https://60066e33de9cce0007f20169--quizzical-golick-2079e7.netlify.app/ ), can share dendon.yml config file in DM if needed.
  • c
    (Something that might help would be an example of how to use the 
    siteindex
    key correctly - I wonder if the issue could be that I set this equal to 
    root.md
    , but didn't include 
    root
    in my list of 
    siteHierarchies
    because I didn't want everything to be show up twice in the navbar + this would defeat the point of only publishing some sections.
  • h
    I upgraded to 25.2 and "publishing" command will still lead to similar error. 😂 {"level":50,"time":1611035939186,"pid":69628,"name":"dendron","ctx":"c:run","err":{"type":"r","message":"","stack":"Error: \n\tat c.run (.vscode/extensions/dendron.dendron-0.25.2/dist/extension.js:9:103042)\n\tat runMicrotasks ()\n\tat processTicksAndRejections (internal/process/task_queues.js:94:5)\n\tat async .vscode/extensions/dendron.dendron-0.25.2/dist/extension.js:9:78105","status":"unknown","msg":"","payload":"{\"msg\":\"no repo found\",\"stack\":\"Error: no repo found\\n\\tat l.sanity (.vscode/extensions/dendron.dendron-0.25.2/dist/extension.js:637:24183)\\n\\tat runMicrotasks ()\\n\\tat processTicksAndRejections (internal/process/task_queues.js:94:5)\\n\\tat async l.execute (.vscode/extensions/dendron.dendron-0.25.2/dist/extension.js:637:24398)\"}"}}
  • h
    I updated the log in the github issues.
  • k
    that looks like a different error 🙂 the publish command requires that you have a git repo setup. if you are attempting to publish for the first time, I would recommend following the publishingv2 quickstart here: https://dendron.so/notes/861e4e48-dcc5-4813-a695-8940ba6e64d3.html
  • h
    Oh sorry about that. I didn't read through the guide coz I previously used publishv1
  • k
    your right, examples would help 🙂 will add some before this weeks is out. as for 
    root
    , its interesting - if 
    root
    isn't include in 
    siteHiearchies
    then you should not be able to set 
    root
    as 
    siteIndex
    either. the way 
    siteHiearchies
    works: if you publish everything, then set it to root, if you are selective, whitelist the hiearchies you want to publish
  • k
    instead of publishing 
    root
    since its a special case, i will publish 
    home
    which is a single note hiearchy that just represents my home page
  • c
    Thanks for the detailed explanation, this improved my understanding of what dendron is doing :)! Will update my config and republish in the am, this is just me misunderstanding the config file options, and isn’t related to 0.25 specifically.
  • k
    here's an example for 
    https://www.kevinslin.com/
  • k
    Copy code
    yml
site:
    siteHierarchies:
        - home
        - blog
        - books
        - readings
        - cli
        - pr
        - spec
        - day
        - meet
    siteRootDir: docs
    config:
        learn:
            publishByDefault: true
        readings:
            publishByDefault: true
        pr:
            publishByDefault: true
            noindexByDefault: true
        books:
            publishByDefault: false
        cli:
            publishByDefault:
                dev: true
                notes: false
        spec:
            publishByDefault: true
        aws:
            publishByDefault:
                aws: true
                notes: false
        meet:
            publishByDefault:
                public: true
    usePrettyRefs: true
    copyAssets: true
    logo: notes/assets/images/bio-photo.jpg
    title: Kevin's Page
    siteUrl: 'https://www.kevinslin.com'
    description: Kevin is working on creating better tools for thought
    twitter: kevins8
    author: Kevin S Lin
    duplicateNoteBehavior:
        action: useVault
        payload:
            vault:
                fsPath: notes
vaults:
    -
        fsPath: vaults/public-vault
        name: public
    -
        fsPath: vaults/business-vault
        name: business
    -
        fsPath: vaults/people-vault
        name: people
    -
        fsPath: vaults/dendron-vault
        name: dendron
    -
        fsPath: vaults/dev-vault
        name: dev
    -
        fsPath: vaults/aws-vault
        name: aws
    -
        fsPath: notes
version: 1
useFMTitle: true
  • k
    this might be a little overkill for most people 😅
  • k
    note that i don't explicitly set a 
    siteIndex
    . by default, its the root of the first hiearchy
  • c
    Do you still need to have a root.md in your repo even though you don’t publish it?
  • k
    today that’s a requirement but i’m thinking of removing it in the future
  • h
    forgot about that feature request 😅
  • c
    (I saw the discussion in https://discord.com/channels/717965437182410783/735365126227493004/800515718415122434 so I think that’s why I was confused about whether to keep root in my hierarchies after setting the custom list)
  • c
    Ok cool, so I’ll take the contents of my root.md, move them to home.md, and have an empty root.md file to keep the schema system happy.
  • b
    I checked and I had removed the data formatting entries from my settings. It looks like daily entries created via 
    Crtl+Shift+i
    behave differently from journal entries created from 
    Crtl+Shift+j
    . Also for scratch notes not the complete date is used in the front matter.
  • k
    for scratch notes, the default format is different (https://dendron.so/notes/eea2b078-1acc-4071-a14e-18299fc28f48.html#dendrondefaultscratchdateformat). the workflow is to add a human friendly moniker at the end (eg. scratch.....foo) for daily entries, the only difference should be the 
    defaultJournalDomain
    (https://dendron.so/notes/eea2b078-1acc-4071-a14e-18299fc28f48.html#dendrondailyjournaldomain) they both share the same date formatting and if not, then thats a bug 😅
  • i
    when using the look up, is there a way to tab complete the hierarchy so i dont have to type the whole thing?
  • i
    (tab doesn't work :P)
  • k
    unfortunately, thats a limitation of the vscode input component. another reason we're looking at nextjs
  • k
    which btw, have you had a chance to look at the doc? https://dendron.so/notes/17c61d62-f92e-4002-b8fe-9c05686e4bf9.html
1...191192193...757Latest