it works both with

wl-paste

installed, and without (in that the error handler displays the proper wayland-specific error message about needing

wl-paste

)

merged and published. you should get it when you reload your workspace

as far as merging upstream, that would be great! we don't have any changes from the original - the only reason we forked is because it wasn't available for vscodium

also, this now makes you a @User 🥳 https://wiki.dendron.so/notes/7c00d606-7b75-4d28-b563-d75f33f8e0d7.html#horticulturalist

Oh good to know! I happen to be using vscodium myself, in case it matters for anything in the future 🙂

next!

NextjS Preview Items

thanks for the comment. @User - is this covered by the hover message fixes you're implementing?

Yes, the message is confusing, so I'll be fixing that this week.

@User Following up from discussion at office hours, updated our docs with resources to relevant frameworks and tutorials necessary to work on the Dendron frontend stack: https://wiki.dendron.so/notes/PZhEkONwVTKRcXPepinBy.html @User @User @User @User if you were looking for a good first task, i would recommend the sitemap task 🙂 https://wiki.dendron.so/notes/wnjZiTP1UEW9e0aGz1HT0.html#^cf6Jxkyn3rku

@User let me know if you have any suggestions to add to the list of good frontend tutorials 👆 . the idea is to provide enough context so that a non-web developer can feel comfortable taking on

#size.small

web development task

checking out what's being worked on in the August release of VSCode. Found something interesting: https://github.com/microsoft/vscode/issues/88716 looks like the quickpick items will now be able to have buttons themselves

and drag & drop for contributed tree views: https://github.com/microsoft/vscode/issues/32592

good frontend tutorials

How to trigger a build when developing? I am able to Run Dendron using

Run Extension: Local (plugin-core)

(within VSCode-InsidersEdition) which looks closest to the suggested https://wiki.dendron.so/notes/64f0e2d5-2c83-43df-9144-40f2c68935aa.html#run Run

Extension (plugin-core)

However, the typescript changes are not reflected in the run (if I modify the out '.js' files then changes are reflected in the run) If I build the plugin-core in command and re-run the

Run Extension: Local (plugin-core)

the changes do appear, is there an integrated IDE way of doing this though?

Can you make sure you are compiling the code --> bootstrap/scripts/watch.sh should be running in the background

That works, still requires to rerun

Run Extension: Local (plugin-core)

though, but does work to have the changes show up with rerun of

Run Extension: Local (plugin-core)

Thank you

can you add a PR to our docs to update that?

NOTE: to have changes built in real time, you need to run...

Will do

Hey, I'm working on an RFC to add query support to Dendron. I'm split between allowing users to write queries in JavaScript, and creating a custom query language. I wrote the proposal with examples demonstrating both, I'm curious what others think. JS: https://github.com/dendronhq/dendron-site/pull/165/files custom: https://github.com/dendronhq/dendron-site/pull/166/files

I was originally leaning towards a custom language, but I'm starting to realize it will be a huge undertaking to make it as powerful as the JS version can be.

Great. I’m using dataview plugin in obsidian for queries. They also make custom query language that looks like SQL, which is familiar to people nowadays. Hope their approach can give you some insight Plugin: https://blacksmithgu.github.io/obsidian-dataview/ Custom query language: https://blacksmithgu.github.io/obsidian-dataview/query/queries/

I noticed that several versions ago, for those links doesn't have a note behind it, for example

[[foo.bar]]

, I could create a new note from it by ctrl + left click (or

gd

in Vim mode). Will Dendron keep this feature after the fix? It's very convenient! 👀

I think you can re-enable that by setting

noAutoCreateOnDefinition: false

in your

dendron.yml

. However doing that means a note will be created if you hover over a missing link too.

@User heads up that instructions for testing a single integration test are here -> https://wiki.dendron.so/notes/cb22bd36-d45a-4ffd-a31e-96c4b39cb7fb.html#run-a-specific-test-for-dendron-plugin

Thanks will try it out.

@User @User Still iterating on this but took some time to split out some of the main architectural components of Dendron. Posting here for interested bystanders Current docs here: https://wiki.dendron.so/notes/ENeBSPWAtTlQclXYWNm6c.html The way we organize packages in Dendron is according to the

module

schema which is described [here](https://wiki.dendron.so/notes/yz7BaxKE7IssV5Go.html)

@User @User I have opened a PR for an RFC for improving Dendron configurations. You can find the PR here: https://github.com/dendronhq/dendron-site/pull/175 You can find the Github discussion thread here: https://github.com/dendronhq/dendron/discussions/1260 Posting here so that I could get some feedback before I start working on the implementation. If you have any opinion about how config consolidation should be done, how configs should be presented to the end users, or how it should be implemented internally, please leave a comment here or in the discussion thread. I am planning to start working on this next week. Thank you 🙏

@User A new blog post has sprouted! 🌱 🔖 Dendron runs inside VSCode and VSCode-compatible editors (ex. VSCodium), so we always keep a close eye on updates. Our takeaways from the VSCode v1.59 include terminal magic tricks, shared view states, and other notables that Dendronites may find interesting. https://blog.dendron.so/notes/JzH76BDLaFwJloUFzkGGg.html