the typical lifecycle is someone posts a question in the discord and we triage and figure out if its a dup or a new issue

great job @User 👍 I like how it's going.

Thanks 🙏 @hikchoi let me know if you think of more improvements to make.

have you guys looked into the github discussions feature?

we started using it at work and it's a nice place to start a thread for not-quite-actionable-yet sorta things

discussions in discord are nice because of the spontaneity but it's hard to track it down once another discussion pops up.

something like this I think fits nicely in the discussion tab : https://github.com/dendronhq/dendron/issues/481

Not yet will check it out. Totally agree, moving convos out of discord around a particular feature will be useful so we don't lose track.

it is yet another place that will eventually need triaging, but I think it'll help clean up the issues a bit

I've just been spelunking through the dendron wiki and I quite like this rfc: https://wiki.dendron.so/notes/21b2e152-95f7-4904-8a8e-8d4d0b8c950c.html

This blogpost really resonates with me on the oncoming abundance of tools for productivity and it was written in 2014, and after several years it still applies so well today.

my go to quote is still vannevar bush which was written in 1945 > "We are overwhelmed with information and we don't have the tools to properly index and filter through it. [The development of these tools, which] will give society access to and command over the inherited knowledge of the ages [should] be the first objective of our scientist" - Vannevar Bush, 1945 https://wiki.dendron.so/notes/b0fe6ef7-1553-4280-bc45-a71824c2ce36.html#motivation

> I want different ways to think about work so I can get more done. It’s a nuanced difference, but I think it is an important one. 💯 👍 > If you are interested in improving how people work, you should devise methods for work, manners of behavior, and methods of decision making. Document your ideology and apply it with existing tools, so nearly anyone can follow along. This is exactly how I felt when I discovered Dendron. Not so much the tool but the concept of hierarchies was a watershed moment for me. Since we are sharing quotes, here is one of my favorites: > "Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." Antoine de Saint-Exupery How can we do more with less? Even if it means thinking about a problem differently and re-assessing what really matters.

I love this so much

AH CRAP sorry for the late reply

Hi All, I have been using dendron for some time and have a question. Not sure if this is the right place for it.

Cntrl+L

is not able to search the notes that are deep in the hierarchy example :

learn.linux.commands.find.mtime.1minute

I cannot search with

1minute

. Is there a limit or configuration that can be changed?

Might be better to ask that in the questions chat

right above this one, because you're more likely to be seen and receive an answer

Hi all, I have just started using dendron and I'm struck with an issue

I have setup a schema and have set namespace = false but still I can create random entries

For testing I have copied sample schema from here https://gist.github.com/kevinslin/5ca7a6f25a239add5ea374f329e6a19e

could someone please help me out here

A schema doesn't prevent you from creating random entrues it just makes it easier to create correct ones and notifies you of 'broken' ones

Thanks @User Can I raise this as an enhancement request? Is this something planned or in roadmap?

Of course feel free to add this as a feature request so it can be tracked on the road map. Looking at the docs https://wiki.dendron.so/notes/c5e5adde-5459-409b-b34d-a0d75cbb1052.html however leads me to believe the current functionality is deliberate. Schemas are an optional type systems and it even states "schemas are meant to be broken" 😊. May I ask what your use case is to enforce a schema?

strict hierarchy is required for me as I'm planning to share the notes and multiple people would be contributing. Without hierarchies I may have to spend additional time to manually correct the notes and refile them to maintain consistency

Since lookup already knows which notes do not belong conform to a schema, I can imagine we can take that functionality and maybe wrap it up in a cli tool. that way it could be run as git hooks or actions whenever new notes are pushed to a repository. (hierarchy linting? 😄) I don't have any use for strict hierarchies as I tend to let my note more free-flow-y, but I can see how enforcing it could be useful for some cases.

looks like it's planned though. Quoting the FAQ page. emphasis mine : > If you're familiar with typescript - Dendron schemas are similar to the types offered by typescript. You can compile your typescript code into javascript even if the types don't match (subject to your tsconfig). Types help make your projects maintainable, especially as they grow. > > Currently, Dendron will do is show you an indicator if your schema doesn't match. In the future, we'll have a strict mode where we will actually prevent you from creating notes that don't match your schema.