idk if that screenshot helps, but i added the task frontmatter on the t.app note (just to see if that works) even though i don't really want that note to be a task.

if there is no airtable frontmatter in the note, it just doesn't populate the fields on the right

yeah. sorry idk what the exact issue was, but it's one or multiple of the following: - threw out all the old tasks and started a new hierarchy - deleted all tasks from airtable - reloaded indexes - reloaded the window - fixed

t.schema.yml

so it wouldn't yell at me when reloading the indexes

i'm trash at troubleshooting cause i just wanna try stuff until it works, then forget about it.

It's still trying to add the note i select in the "Select hierarchy for export" prompt, though. t.app isn't a task note and shouldn't be added as a task, but I have to select it to export t.app.* I can remove the task from airtable manually after it's made, but dendron spits an error on every export cause the airtableid isn't in the airtable table anymore.

not sure I can use it, but is there a way to get the index? i tried to parse

.dendron.cache.json

but failed miserably 😵‍💫

hey, so is the problem now that you want everything under

t.app

to export, but you don't want

t.app

itself to export?

Yeah pretty much. i don't know why you would want the root of the tasks notes hierarchy to be a task itself

Especially since ive got like 8 diff task project hierarchies.

T.app, t.sys, t.den, etc...

Am i just using this wrong

The way hierarchy selection works right now is that if your patter is

foo

, it's inclusive of

foo

+ everything under it. Unfortunately there isn't a way to modify this behavior right now, apart from not having the root note at all to prevent the export. Would you mind opening a feature request for this? There are a couple of ways we can implement this: - probably the easiest way is that we support regex in the hierarchy selector so you can do something like

^foo.+

- we've also thought about having export integrate with the Notes Trait system such that you can restrict export to just a certain 'type' of note, for example in this case, just export notes under this hierarchy of type 'task'. We're quite far from this capability at the moment though

Yeah i can make the feature request.

I'll have more to say as i use the system. Still working thru how i want my work to flow in dendron.

Hi @User - what did you mean by 'get the index'? What are you trying to do with that info?

For now. I want to fill a treeView

As in the tree view isn't showing you the correct information about your notes?

No I'm fiddling with

What does the

title

property do within an inline schema definition? I'm looking to make my schema graph more readable as a lot of the nodes are glob patterns

It shows up in the lookup bar if you have it set, instead of just showing the pattern. In this screenshot, you can see it says

> RFCs...

because I have the title set:

I think I'm also interested in what Saine is asking about here - the way I interpret the question is something like: if I wanted to display a tree view of my note hierarchy in vim, or another non-vscode context, what would be the best way to get that information from a Dendron workspace?

Thanks! Does it also apply within the schema graph view?

yes

Seeing inconsistent behaviour based on if the schema has the parent of

root

Will have a look to see if an issue already exists / create one

Quick question: is it possible to export a single note, say, as a markdown file? So far, I've used the export pod command, but that exports all notes.

You are looking for the "Publish Pod", which only exports a single note!

Hi all, I apologise if this is a bad place to start, but I'm trying to find someone to talk with about switching my note taking from my current hodgepodge of local markdown and ikiwiki-based journals, to Dendron, but I'm struggling with the mechanisms of multi-vault, particularly when it comes to managing publishing because I have four distinct security domains which I need to consider, but I really like the idea of having dendron able to link between them (assuming I'm sensible and only link from more-constrained to less-constrained)

The four domains I have are: "work private" "work published" "personal private" and "personal published". both private domains should not be websited, and have private git repos in relevant places. work-published has a git repo my colleagues can see and is published to (gitlab) pages. personal-published would be (github) pages. At home I'd only want the personal repos, but at work I'd want all four to be available to me. Currently this is done with a combination of gitlab wiki and gitlab repo for work stuff (we have a work gitlab instance) and then I have private git repos for my personal stuff, and I publish an ikiwiki site (to myself) for the personal published stuff.

The "dream" would be to have a dendron workspace at home with the two personal vaults, and a workspace at work with all four vaults, and to be able to publish appropriately from either place.

@User In one of the videos I watched (and sadly I can't recall which because I was binge-watching them at midnight) I recall you using a number of different symbols in your journalling

- [>] foobar

and the like - Is there some config for turning on support for rendering those specially, because when I try it just ends up showing as

[>]

in the preview.