What happens if I use Import Pod and import the same folder twice?

for imports, your new imports would overwrite your old imports

if you're just starting out, you could just initialize a new workspace

i version my notes using git so before i make a change, i make sure to commit my current notes

this way i can always do a

git clean --force

if something goes wrong 😅

also curious, how did you get the autocomplete working?

I think I was asking too much of my computer when I imported everything. Now I am doing in a controlled way - today I imported every book and I think I won't import all of my uni material (at least not yet - somewhen I might want to link something inside the notes)

So... It started working after I reset my workspace like 4 times, hahaha!

got it. i think you're using the vscode built in auto completion. it can get process intensive depending on how many files you have. sounds like you have a number of them 🙂

@User Thanks Kevin. ks were fine, problem fixed, language was set to plain text instead of Markdown. Grateful

This is my schema, but the template won't work

@User I just realised that every time I re import the books, the .md files get over written but it does not check if there was already a book with that name inside assets. I know their tail gets generated so no file would be destroyed, but would it be better to just check if there's an occurrence in there? I don't know if it would be a good idea not to overwrite them - but I wanted to suggest it

@User just to make sure i understand, you're referring to asset files beings generated every time? if so, good timing because i was thinking of adding an option there. instead of generating an uuid to each asset file, we would import the asset file as is and overwrite any existing files with the same name. does that cover your use case?

@kevins8 - have you seen https://innovationdilation.com/ before? Some neat features, how much of it is possible with dendron?

i’m aware of it but haven’t tried it out yet. have you? what are your favorite parts?

May I ask is there a way to auto generate frontmatter for the imported set of markdown notes? @User

I don't know if I understand it right. I just import pods, and type in the note directory I want to import in. Right?

@kevins8 only available for windows so I can't try it out. I just watched the video.

> @User only available for windows so I can't try it out. I just watched the video. @User - the ability to open an item (and all sub-items) in another pane - does that exist in dendron?

> May I ask is there a way to auto generate frontmatter for the imported set of markdown notes? @User @User you can

dendron: doctor

to auto generate the frontmatter

> I don't know if I understand it right. I just import pods, and type in the note directory I want to import in. Right? @User you run import pod from the workspace where you want to import to. the note directory is where you are getting your notes from

> @User - the ability to open an item (and all sub-items) in another pane - does that exist in dendron? @User yep, see this https://github.com/dendronhq/dendron-template/blob/master/vault/dendron.topic.workbench.md#working-with-multiple-columns

took a look at the video too. i like the plaintext philosophy as well as the workflowy like outline mode

Multiple columns somewhat mess with markdown preview) But it's neat if you're comfortable with raw markdown.

yeah, it definitely cuts down on your screen real estate 😅

You can use the

toggleEditorWidth

command with a hotkey to quickly expand the current editor.

json
{
    "command": "workbench.action.toggleEditorWidths",
    "key": "ctrl+cmd+m"
}

partially alleviates the problem

Nice, didn't know about that one, thanks!

(and here I thought cmd and ctrl never appear on the same keyboard...)

> @User just to make sure i understand, you're referring to asset files beings generated every time? if so, good timing because i was thinking of adding an option there. instead of generating an uuid to each asset file, we would import the asset file as is and overwrite any existing files with the same name. does that cover your use case? @User Exactly! I think the uuid is important - what if you were highlighting a pdf text that is inside the assets folder? However - every time I import the assets, it creates a new file with a new uuid. I think it could work best not by eliminating uuid or overwriting the files, but by checking if there's anything with the same name the (if the file name matched the first part of the assets name, which doesn't have the uuid)