this config key is not yet documented because it's a beta feature we are trying out and is confusing to use at the moment 😅

I use a portable installation too and I don't think I've ran into a problem so far. (though my main usage is much frequent in a non-portable insider build)

okay, then it's definitely a PEBKAC kinda issue 🤣

(Problem Exists Between Keyboard And Chair)

Dendron has a lot of features 🙂 We are constantly finding ways to improve the usability. Don't hesitate to ask and give feedback here.

i did wonder if there's a way to point dendron at my portable install of git

or if i need to configure a .bat file to launch it with some environment variables

worst comes to worst i can use the git features only when i'm at home and have a global git installation

Thank you to those of you who contributed to my earlier question about using an index of a book to structure notes in a digital zettelkasten. As I explore a practical and useful way (for me at least), I share the following example of a way to co-mingle notes from various sources in one hierarchal "digital slip box - folder). Note titles would take this syntax: Index header.subheader.book (source) title.page reference. The note itself would contain the contents and the noted tagged as being fleeting, literature, reference, bibliography, or permanent(evergreen) note. Is this an appropriate (practical) use of Dendron? - Hunter-gatherer.abscence from archeological record.Against the Grain.page-13 - Hunter-gatherer.acidic fruits.Catching Fire.page-66 - Hunter-gatherer.fertility rates linked to.Against the Grain.page-83 - Hunter-gatherer.leisure.The Dawn of Everything.page-136 - Hunter-gatherer.sexual division of labor.Catching Fire.page-7

Is there any way to use wikilinks in the frontmatter, so that they are also included in the backlinks?

looks fine, you'll have a lotttttaaaaa notes, but as i was re-assured, Dendron can scale to a whoooollllleeeeeeee lotta notes

Not right now, but there's a feature request for this that you can upvote: https://github.com/dendronhq/dendron/issues/1531

ok thx

This is more of "wouldn't that be cool?" than a question, but I was just looking at the nested tags in the editor's Tree View and realized I'd love to have colors that indicate the indentation / nesting levels. No clue how feasible this is or what degree of customization we greedy users might begin asking for, but it strikes me as a really nice "quality of life" possibility.

We already have a color setting for notes (which only works for tags). We could reuse it for this, would be pretty cool

Nice feature request. I want this for VSCode file system too

The way you structured the title would work. I would personally: 1. avoid using whitespaces in the title (for compatibility in various environments, Dendron defaults to `sweker-case`ing file names) 2. have less metadata exposed through the title (can use tag notes in body or frontmatter of note: https://wiki.dendron.so/notes/8bc9b3f1-8508-4d3a-a2de-be9f12ef1821/) 3. start with having the subdivision of pages under markdown headers in the book source note instead of a separate page. Later refactor the notes to have separate pages (or maybe chapters first) when the amount of content becomes unwieldy. (following the amoeba pattern of structuring notes: https://wiki.dendron.so/notes/e780000d-c784-4945-8e42-35218a3ecf10/) Unlike other tools, we put a lot of effort into making it easy to refactor notes. 1. commands like

Rename Note

,

Move Note

,

Refactor Hierarchy

,

Move Header

,

Rename Header

, all help you easily change the title / break down existing content of your note into smaller chunks: https://wiki.dendron.so/notes/srajljj10V2dl19nCSFiC/ 2. using modifiers in lookup will let you select some text and extract it into another note. Or use that selection as a note title to create a new note and convert your selection into a link at the same time: https://wiki.dendron.so/notes/ad270a7d-2aed-4273-8319-eb6536e38b29/#selectiontype This means you can iterate on the structure of the notes as you go forward and not worry too much about it at the beginning. I've spent a lot of time trying to make my note structure perfect and end up changing them half way through. But this is all my personal preference. If a note structure works for you I can tell you that it would be the right one. You mentioned that you haven't started using Dendron yet, so this may be a lot of information. These are briefly introduced during our initial user guide that you can go through when you first install Dendron as well, so I encourage you to try it out.

in which view do i get to see colors for tags?! i know they have little boxes by them in the preview.

NGL the intro to dendron was one of the best "short-n-sweet" tool introductions that i've ever delt with. most of my "wtf" moments came from the little bug i ended up filing a report on and not me making mistakes 😅

oh i meannnnntttt to ask, is there a way to "activate" dendron from a session of vscode without opening a dendron code workspace?

this shouldn't be an issue going forward since i've got my "digital garden" going, but i might want to use native repos in some spots in the future.

If you use initialize workspace in the repo you want to use Dendron, you can make that a native workspace: https://wiki.dendron.so/notes/lamzybrD6SgQlJ9BpwkQk/

ohhhh it's working now....

i tried the other day to get the dendron commands in the palette and they weren't popping until after i opened a dendron workspace

hi, i'm slay, and murphy's law targets me

@User are you from the team? I'm trying to make a PR but don't know where to start.. and the test page here(https://wiki.dendron.so/notes/81da87be-2d4e-47b5-a1d6-c0d647e1ab00/) is set to private some how

ah, that note should be updated. sorry about that. all dev related docs are migrated to a new subdomain. https://docs.dendron.so/notes/3489b652-cd0e-4ac8-a734-08094dc043eb/

yes, and in this domain the "Contributing" is also set to private

note: all notes in

docs.dendron.so

and

wiki.dendron.so

comes with our monorepo (it's a native dendron workspace), and you can use lookup to access all the relevant docs.

WAITASECOND