Did you reload the index?

Yes

The id of said template is unique? I have found that sometimes that is the issue.

Try chaning it manually.

Changed the first 3 characters manually. Still no luck

Hi folks. Not sure where to ask this, but I'm having a technical issue with Dendron and I am not sure if it's just me. Here is how to reproduce the problem (on my machine at least): 1. Invoke Refactor hierarchy (via Ctrl-Shift-P command palette) 2. Choose match text (i.e., write something or accept the default; confirm using Return key) 3. Choose replace text (same here, confirm using Return key) 4. The Refactor Preview is shown along with the proceed / cancel commands in the command palette, with "proceed" selected. The problem is that the focus is not on the command palette but somewhere else. I can't even tell where the focus is. The result is that I cannot confirm the refactoring by pushing Return; instead I have to click on "proceed" or shift focus back to command palette (Ctrl-Shift-Tab twice does it for me) before pressing Return. This changed recently. Previously the focus remained on the command palette and I could confirm by just pressing Return. Maybe after a Dendron version upgrade, maybe after something else. Can anyone reproduce? Thanks!

@User works fine for me on Dendron 0.15.0 (can press Return to proceed, can select between cancel/proceed with arrows)

@User thanks for checking! I'm also running 0.15.0. So at least this is not a universal problem. I wonder what else could have changed.

my vscode is only 1.49.1 though)

Interesting. I have vscode 1.51.0

Could try to downgrade.

@User i'm not able to re-produce. i'm also on 1.51.1

Dang. Thanks though.

Is it another VS Code extension enabled in your workspace? Maybe try disabling them all (you can do this per-workspace), reload and enable one-by-one until you can reproduce?

can you turn on keyboard diagnostics?

this will show you everything that's happening when you do a keypress

Thanks @User and @User . I will mess around a little and see what I can do. Just started disabling extensions...

Kevin's suggestion is a lot less effort than mine, might be worth doing that first 😅

Yeah, thanks, that was news to me and I'm definitely doing that first.

> Hello guys! Is it possible to put an additional line in the yaml section globally? I mean for all future md-files? @User hmm, that's not an option at the moment. can you describe your use case?

> When creating a note through the lookup, if I use title case for the said note, the title of the note (after the id field) does not respect the title case. that is a feature/bug. we run title's through a capitalize method which capitalizes the first word and lower cases everything else. we should be smarter about that. can you submit a feature request so we can track it in our roadmap? https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=feature_request.md&title=

@User i noticed that your schemas all have

namespace: true

set. this means match everything that is one level underneath. so

id: projects

would match

projects.foo

so your

DIY

schema as it is now would match

projects.{child}.tech.{child}.iot.{child}.diy.{child}

--- generally when it comes to categorical data, I would recommend keeping a short hierarchy and using tags to filter. so

projects.foo

and add a

[[tag.tech]]

in the frontmatter or the body of the content instead.

> @User hmm, that's not an option at the moment. can you describe your use case? @User i use kind of zettlkasten-style for my note-taking. I know, that i can create templates and put my additional yaml string for specific schema, but it is little uncomfortable

> The problem is that the focus is not on the command palette but somewhere else. I can't even tell where the focus is. The result is that I cannot confirm the refactoring by pushing Return; instead I have to click on "proceed" or shift focus back to command palette (Ctrl-Shift-Tab twice does it for me) before pressing Return. > > This changed recently. Previously the focus remained on the command palette and I could confirm by just pressing Return. Maybe after a Dendron version upgrade, maybe after something else. Can anyone reproduce? Thanks! @User So having tried this with keyboard shortcuts debugging on, I unfortunately did not learn much. Pressing Return at stage 4 just says

[2020-11-10 18:01:01.126] [renderer3] [info] [KeybindingService]: | Converted keydown event - modifiers: [], code: Enter, keyCode: 3 ('Enter')
[2020-11-10 18:01:01.126] [renderer3] [info] [KeybindingService]: | Resolving Enter
[2020-11-10 18:01:01.126] [renderer3] [info] [KeybindingService]: \ From 21 keybinding entries, no when clauses matched the context.

which I interpret as "you are focusing something that does not respond to Enter". However, what is possibly a clue is also I am getting a steady stream of

[2020-11-10 18:04:04.204] [renderer3] [error] ENOENT: no such file or directory, open 'rendererLog': Error: ENOENT: no such file or directory, open 'rendererLog'

once every 1.5 seconds. I see this has been discussed in a recent issue https://github.com/dendronhq/dendron/issues/277

The issue #277 could be entirely unrelated of course.

That bug could be caused by any extension that enumerates all editors: https://github.com/microsoft/vscode/issues/36579

@User the

rendererLog

is usually a red herring - it means vscode is trying to open an output window which is not a real file

@kevins8 Yeah, I see, thanks. Seems likely this has to do with some other extension or setting then. I'll keep digging and report back if/when I find the culprit.

👍