I added my full log to the existing bug report on renaming: https://github.com/dendronhq/dendron/issues/385#issuecomment-735645252

this has been fixed in the 0.18 release 🙂

Twitter bio is currently: > The official page for Dendron - a better way to know I think it could be a littler more explanatory. Maybe just use

About

from the Github project: > The personal knowledge management (PKM) tool that grows as you do!

I am having difficulty with some of the keyboard shortcuts in Dendron clashing with my muscle memory on MacOS. The one that keeps tripping me up is

shift+cmd+right/left

and which I use all the time for selecting lines of text, but Dendron maps to

Go to next/previous Sibling

. I worked out how to remap these shortcuts in vsCode, so not a problem now. Wondering if this might be a barrier to other newbies…

i think this hasn't been updated since i created the twitter account 😅 will add some details today 🙂 just added! jest learned you can add emojis to the twitter bio 😅

this has come up a bunch. my plan is to remove those shortcuts with another default. will go out in this week's release!

i find

ctrl+cmd+[

to be useful

speaking of the go to previous sibling cmd, it seems going back to the last day of last month from today (the 1st) is broken. Is anyone else seeing: "One is the loneliest number. This node has no siblings 😦"?

Maybe initzalize could start with questions about keyboard shortcuts so each user can costumize them. And set them to their prefernce if they are not already set in the vscode user config.

this is because sibling nav goes through all notes in a given level of hiearchy. so

11.*

is one level and

12.*

is a different level.

@User had a great suggestion back in the day of asking users what tool they were coming from so we can customize shortcuts that mapped to said tool. @User mind creating a feature request for better keyboard shortcuts so we can plan for it in the roadmap? (https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=feature_request.md&title=)

The Markdown Links view is so weird to me. The nodes are titled by the heading the backlink is in, not the note's title. EDIT: additional testing shows that Markdown Links only cares about

# H1 headings

as well. Interesting! EDIT: nodes wont show up at all if you don't have an

# H1 heading

in the file. EDIT: starting to believe this view is mostly just eye-candy (though perhaps with the right upgrades it could be somewhat useful for visualizing connections) EDIT: this plugin is also just ... not Dendron-optimized. For example,

[[foo.bar]]

references show up as whatever the `[[foo]]`'s

# H1 heading

is (NOT `[[foo.bar]]`'s) ... and, i mean, when you think about it -- we want to use the Frontmatter title, not the

# H1 heading

anyway probably.

yeah, there's a lot of room for improvement. the graph view is really just a hack right now to have some sort of visualization 😅

for dendron's structure, using the hierarchal mindmap that @User suggested makes a lot more sense graphs would still be useful for exploring links between nodes (eg. backlinks, tags, etc)

Figured this was the case. Early days 🐣

@User here is how Tinderbox uses its syntax to extend markdowns [[linksSyntax]] they call it ziplinks. It massively lets you stay in the flow while you write...for example [[]] iow, this allows you to very simply create a new note with anchor text to view in display mode with some text automatically attached. It is a real time saver but more importantly, it allows you to stay in the flow of the current note without having to jump to another note and finish/start your thought. Lastly: [[< >]] syntax create a bidirectional link, [[ ]] syntax is unidirectional. Pretty Sweet. Here is the link: https://www.acrobatfaq.com/atbref8/index/MiscUserInterfaceAspects/Ziplinks.html

i haven't forgotten about https://github.com/dendronhq/dendron/issues/220 yet 🙂

every time i do an onboarding with a new user, i get reminded both of the wealth of features that dendron already has and also how much more there still is to build :) there's a loooooooooooooooooooooooooot 🚀 🌱

🙂 @User One day at a time.... each tool has its strengths. In my world, gone are the days where one has all. Its all about how they play in the my app ecosystem workflow. Extending the markdown syntax and being able to have powerful visualization tools for my notes is key. I keep using Dendron because of its heirarchy uniqueness not only in schema but to me, the heirarchy in graphs Dendron uses is really unique and a game changer. It allows me to keep making sense of my notes. Hopefully, we could get rules that could filter AND rules based colors to really visualize clusters and subsets of notes. That would be cool its here too. https://github.com/dendronhq/dendron/issues/261Many thanks to you @User you showed me the importance of bringing back structure to my notes. Nice work my friend.

thanks @User also know that i'm tracking and appreciate all your suggestions and feature requests. we have a ton of amazing features in the pipeline, many of them user feature requests, and it kills me that we can't do it all right now good problem to have but a problem nevertheless 😅

Keep moving forward. You are really onto something with this product. Everyone thrives in different kinds of environments - some people need RIGID structure, some people need absolutely NO structure - and products exist that satisfy both of those concepts. Some people, like me, need a mixture of the two - I need some structure and some flexibility to do things my way. I think you will find that once people learn to use Dendron they will appreciate what you have created. Thank you!

thanks @User 🙂

Has a "template refactoring" command been suggested before? I tend to iterate on mine over time, would love if I could keep them all tidy and match-y.

you mean schema templates? if so, no, it has not

✨ https://github.com/dendronhq/dendron/issues/390

trying a new thing where i'm doing a followup with folks after a release. tagged a few folks here that brought up issues/requests. let me know if the latest release (0.19) addresses your original requests 🙂 @User: image preview is here @User : we fixed the completion issue as well as the tree view issues! @User : fixed the journal note and the local vault issue

How exactly image preview should work? Still asks for CMD+click for me

you can trigger the preview my hovering over a md image link: https://www.loom.com/share/82119bc9ee184e3ca8e619c3d7e48209

Thank you, @User for quick answer. This is exactly what I was doing. I went through many images I have referenced and discovered that some of them are previewed and most not. There might be some limits for image size/dimensions maybe?

hmmm, are you able to share one of the images that doesn’t preview as well as the raw markdown for referring to the image?