Could you send an announcement about this? Port scanners can discover open port numbers, so randomization alone is not sufficient.

Sorry if this is noob question, but when I install Dendron extension, click "get started" and it creates Dendron workspace in my user folder in Win 10. Can we choose the folder for Denron? I prefer it in My Documents

Use the Initialize Workspace command and select "Code Workspace". You'll be able to select the folder path next. See https://wiki.dendron.so/notes/lamzybrD6SgQlJ9BpwkQk/ for a video guide of the other type of Dendron workspaces.

Is there a way to include the full name of a note for backlinks when publishing? e.g. cs418.syllabus in my hierarchy instead of just "Syllabus". Right now my backlink sections look like this. I could change the name of every note in the front matter (like I have done with CS257 Syllabus) but I don't really want to do that because the notes are already organized in a hierarchy.

the note name is generated from the

title

in the frontmatter which defaults to the last part of the hierarchy. this is automatic though we've had a few folks who had a similar use case as yours. if you submit a feature, we can track it on the roadmap 🙂 https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=feature_request.md&title=

Thank you! Happy New Tear to all

Is there any way to undo recent *Refactor hierarchy *, After refactoring cp.js to cp.lang.js, The contents of the note cp.js.react were missing in renamed note. I did not find this issue in other similar refactored notes that were committed to git.

If they are in git, you can use git to undo it. If you haven't committed the change yet, you can do

git restore vault/file.before.refactor.md

. If you committed already,

git revert <last-commit-id>

or

git reset --soft HEAD~1

will undo the last commit.

It is concerning that file contents were lost in a refactor though, if it happens again please make a bug report and we'll investigate it.

I haven't staged/committed the file yet. I could see some of the headers in .dendron.cache.json file. But, the file is not available. I tried but could not replicate the behaviour again. I'll make bug report if I get the same behaviour again. Thanks for the reply. 👍

Another quick question. Adding .dendron.cache.* to .gitignore is not ignoring .dendron.cache.json file from git. Am I missing something or is it something not to be ignored?

it should be. if its not ignoring, then it means that it was added sometime before. you can remove the cached version with

git rm --cached {path/to/file}

Is it possible to import regular markdown notes into the Dendron format?

I've noticed there was other importing options like from obsidian etc

So what I probably need to do if its manual is convert the level 1 headings to the title and add the boilerplate code (update and created would be current). I might have seen something about importing regular markdown but can't remember where (or I misremembered)

See the documentation on the Dendron Markdown pod: https://wiki.dendron.so/notes/13c4a608-0a32-4c62-9c7e-2b7f9f2d18bf/ I'm not sure if it will automatically convert level 1 headings to titles (hopefully someone else here will be able to tell you), but it should take care of the frontmatter boilerplate stuff, and should convert documents in a folder hierarchy and wikilinks between them into the Dendron dot-delimited format.

You could also just move the file(s) into the vault and run the Doctor command: https://wiki.dendron.so/notes/ZeC74FYVECsf9bpyngVMU/ It'll add the frontmatter, and it can also convert level 1 headings to titles

@User Is Tasks RFC now intentionally private? Will there be a

tasks.

domain for task notes? If not, what are the ideas about file names for those? I think that writing down some long terms tasks as task notes might be a good idea. Then, they maybe are more like projects with multiple sub-tasks, what is the vision for those? Would be interesting to see how people do this, Denron team and beyond...

It shouldn't be, I think the link is out of date because we split them from the wiki. https://docs.dendron.so/notes/716e2699-42e1-44bd-9b97-124f03173ddc/

Also, on the Wiki, there is a confusion between tasks and todos. It is harder to find the relevant information because of this. The snippet above is the example. I would suggest standardizing this so that it is called one or the other with the synonyms mentioned in the text. If there is a difference, define. At the moment it looks like these words are interchangeable...

Task notes are both for longer tasks (things that take weeks and have many sub-tasks) and smaller tasks (small things that don't take long). There are plans for organizing and managing them, and we're listening to any community feedback right now.

Thanks for that feedback, they were first called Todo notes and we ended up renaming them, but didn't update all documentation. I'll take care of that as well.

Great. Thanks. Will there be a formal way to differentiate? Like a

project: true

in front matter or some such?

Right now I'm just thinking that if a task note has children that are also task notes, it will automatically become a large task where all the children tasks are a part of it. But I'm happy to hear if you have a different use case.

I see, and what about naming? I am thinking that I want one strategic todo note with the index of all tasks, organised by theme (projects, publications, events, etc), where needed, tasks in there can link to task notes and following your suggestion to subnotes (

task.project.project-1.begin

for example, or should task notes be the subnotes of the project:

project.task.task1

?) then some of them will need to appear in the dayly journal notes. maybe in the monthly journal notes? it is hard to understand the possibilities... a bit overwhelming...

Yup, a lot of options! I think these should be some way to link tasks to projects without having to put them under it. At the very least you might have a task that's part of more than 1 project. I think there's also opportunities for this to work well with the queries and note traits RFCs that are also in development, one thing I'm excited about is using queries to create views of tasks that are done, and tasks that are in progress etc.

Yes, indeed. You can do a bit of aggregation with Todo Tree extension and the like but saved queries would be great for those types of things, with set sorting and exportable lists too.

So, what would be the simplest for now to keep it compatible with the emerging future? Maybe just one master file to be split later?

And to confirm, you are saying that there will be no special domain for tasks like there is for tags?

No, there won't be. Feel free to organize them how you like, and we'll make sure whatever we come up with is flexible enough to work for it.