*how

@User, you can edit your message just by pressing the up key. No need to add an extra line for that. #suggestion

Ok cool

> @User Not sure, but it got changed when I tried to change theme in 'Preferences: color theme' in VSCode. It did not affect the website but it got changed @BSPrick I think this is standard vscode functionality the current theme is stored in the workspace file (you could have different ones for different workspaces). So updating the theme changes the workspace file

Thanks but how can I change the color of the background and links? Any clue?

in website?

maybe using some css

I'm not sure though

Ok. But there are no css files where I can modify, I will try to check though

Inline CSS did not work in markdown files. Thank you for suggesting it though

With this issue as context: https://github.com/dendronhq/dendron/issues/210 What is your opinion on a structure with directories compared to todays solution?

I personally would love this, as it would solve my use case of viewing notes on mobile via "nextcloud notes"

Looking at stubs and not really getting them, from the doc: Stubs - Stubs are notes that don’t exist but will show up in lookup results. There are two reasons why these notes might show up: - they are the parent of a note deeper in the hierarchy (eg. foo.bar might be a stub for foo.bar.foobar) - they are possible notes according to the schema ------------------------------------------------------------------ then what is the significance of "stub" in the frontmatter? that at the time of creation (from the lookup bar?) it didn't exist?

@tfer Stubs = Notes that don't exist but that you might want to create. Either it will be something defined in the schema for a note (ie you might have a schema that says your note

project

can have the children

tasks

,

resources

and

personnel

and you might only have created

project.tasks

and

project.resources

thus far - In which case the lookup will suggest the stub

project.personnel

- Or - you might have created a note like

resources.people.fred

without first having created

resources.people

, in which case lookup will suggest that you might want to create

resources.people

.

Thxs, that explains the first point better, I had a grasp of the second

Re: Stubs in metadata https://discord.com/channels/717965437182410783/735365126227493004/754917834848600084

So just for dendron to understand the hierarchy I guess...That's a good question though, as to why it can't figure out that it is not a stub by virtue of it existing.

I'm guess it provides history as to how the note came to be created, if that is so this might be better named as "stubbed", or "stubbed-out", or "from-a-stub"

@User I'm not really sure how this is still Dendron. For instance, the point "familiarity - dendron file structure looks like any other part of the file system. Less to learn, faster to adopt" - The filename structure is literally how you access any given note in the lookup, so this doesn't seem like something you could avoid learning in order to use Dendron. What exactly would Dendron do using this structure that you couldn't get from just storing markdown files and associated files in folders and accessing them through the file system/vscode?

@User Just to be clear, i didn't write that issue or the design arguments linked in the issue, but i stumbled upon it here the other day. I also understand that the structure in dendron as per today is vital and central in it's presentation with for example the lookup (which i have been using a lot lately, so this is purely curiosity and not an attempt at criticism). With that being said, i am curious in the name of compatibility with other applications. For instance, if i try to read my notes with any other combination of application/OS (nextcloud, dropbox, file explorer) i have a single folder with x notes, and the hierarchy is only present in the filename (compared to directories).

Stubs = Notes that don't exist but that you might want to create. Either it will be something defined in the schema for a note (ie you might have a schema that says your note

project

can have the children

tasks

,

resources

and

personnel

and you might only have created

project.tasks

and

project.resources

thus far - In which case the lookup will suggest the stub

project.personnel

- Or - you might have created a note like

resources.people.fred

without first having created

resources.people

, in which case lookup will suggest that you might want to create

resources.people

. @User Created a couple of PR's on the doc based on our conversation

@User Ah sorry, I didn't realise you weren't the person who posted that. I am also curious about the idea of using folders for structure fwiw, just couldn't understand the reasoning from that issue. But after looking at the discussion from a month or so ago in the #748936364283920495 channel and thinking about it some more I am beginning to grasp how it could be useful (for some people file storage is going to be the extremely important) - It looks like it will be implemented in such a way so that you can toggle it on and off. Personally I hadn't really considered how I might use Dendron for keeping track of my files but it is definitely an intriguing prospect. Could I use it to store/keep track of all my files I wonder?

> Hi, is

dendron.code-workspace

rewritten during upgrades? @User from time to time, dendron will upgrade settings and defaults during the upgrade process. this should only add NEW settings but not override existing options (if it does the latter, let me know)

> Personally I hadn't really considered how I might use Dendron for keeping track of my files but it is definitely an intriguing prospect. Could I use it to store/keep track of all my files I wonder? @LLV that's something I look at right now as one more thing to "port" from my org mode Emacs usage. Org has a cool feature org-attach that let's you attach files to a given heading. Someone on reddit described how that allowed to abstract away the file system and just use search in Emacs as a abstract kind of file system with context and metadata in each note. My main obstacle atm is that vscode insists to open files even if it really cannot such as office documents

> I'm guess it provides history as to how the note came to be created, if that is so this might be better named as "stubbed", or "stubbed-out", or "from-a-stub" @User @User in the newest version of dendron, the

stub: false

metadata isn't being written out any more since we assume

undefined

as no stub. so you shouldn't see it anymore going forward in the fm. the reason it shows up is because every node has a

stub

property and when we create it, dendron populates the frontmatter with some metadata that needs to be persisted (eg. id, creation date). stub shouldn't be one of those fields and has been removed in the latest release

Hi @User and all. First of all, thanks for making Dendron. I think this project is off to a great start and I am ready to accept quite a lot of churn and bugs at the moment, because so many things are just right about Dendron. Keep up the great work! 👍 Now, to my question. When refactoring the hierarchy, I would like to be able to use regex groups in the replacement string. Am I right in my understanding that this is currently not possible? I dug into the source a little and ended up here: https://github.com/dendronhq/dendron/blob/2dbcba77b07d26a1bf0d86a4d5d2cf5df8da2c64/packages/plugin-core/src/commands/RefactorHierarchy.ts#L125 (My use case for today is to rename existing journal and scratch notes, where starting with v0.13.5 dates are formatted with periods yyyy.mm.dd instead of dashes yyyy-mm-dd. Renaming all the existing scratch and journal entries would be a breeze if I could replace

daily\.journal\.(\d{4})-(\d{2})-(\d{2})

by

daily.journal.$1.$2.$3

.)

@User @User regarding the files/folder issue, this has been a requested in the past for multiple reasons, two primary ones being: 1) flat folders can be offputting to many new comers, this doesn't break their mental model 2) folders work well with most existing tools (eg. git, gitbook, mobile apps, etc) don't remember if this was in the issue but here's a link to more detail about tradeoffs: https://dendron.so/notes/da241d31-8a05-429c-a041-02ac6170bf20.html tldr: there's no technical reason we can't support folders, it's just not currently on the roadmap because other items are higher priority

@bass > @User that's something I look at right now as one more thing to "port" from my org mode Emacs usage. Org has a cool feature org-attach that let's you attach files to a given heading. Someone on reddit described how that allowed to abstract away the file system and just use search in Emacs as a abstract kind of file system with context and metadata in each note. My main obstacle atm is that vscode insists to open files even if it really cannot such as office documents @User have you tried the

Dendron: Open Link

command ? https://dendron.so/notes/3472226a-ff3c-432d-bf5d-10926f39f6c2.html#other-links

> Hi @User and all. First of all, thanks for making Dendron. I think this project is off to a great start and I am ready to accept quite a lot of churn and bugs at the moment, because so many things are just right about Dendron. Keep up the great work! 👍 > > Now, to my question. When refactoring the hierarchy, I would like to be able to use regex groups in the replacement string. Am I right in my understanding that this is currently not possible? I dug into the source a little and ended up here: https://github.com/dendronhq/dendron/blob/2dbcba77b07d26a1bf0d86a4d5d2cf5df8da2c64/packages/plugin-core/src/commands/RefactorHierarchy.ts#L125 > > (My use case for today is to rename existing journal and scratch notes, where starting with v0.13.5 dates are formatted with periods yyyy.mm.dd instead of dashes yyyy-mm-dd. Renaming all the existing scratch and journal entries would be a breeze if I could replace

daily\.journal\.(\d{4})-(\d{2})-(\d{2})

by

daily.journal.$1.$2.$3

.) @User hey, thanks for the compliments. we try to keep bugs and churn to a minimum though they do happen 😅 for refactoring groups, you're right, we don't currently support it. it would not be a hard feature to add though. kudos for finding the source code 👍 if you submit a feature request, i'll work on prioritizing the feature: https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=feature_request.md&title=

@User Thanks! I will submit a feature request. Then will go back to renaming my past scratch and journal notes individually 🙂