Expel any ZenHub gripes 😂

> I haven't put in an issue on it, but since the

stub

metadata in the frontmatter is no longer needed, could you knock them out of all the notes? Lead me to figure it at and writ a couple of no longer needed changes to the doc

> Expel any ZenHub gripes 😂 @britt i’ll have a bunch of those!

@tfer yeah, we can build it into the doctor command to clean up frontmatter

I'm sure vim could handle it, I seem to have gotten the impression you use vim, do you use an vscode vim extemsion?

yep

@User As do I 😊

Can I ask which one? And given the conflicts with some of the keybindings, have you mapped some of the dendron commands to the local leader?

@User i use https://marketplace.visualstudio.com/items?itemName=vscodevim.vim

@User Make sure you disable the Crtl + L keybinding from vim extension if you want to use it, if not lookup through Ctrl + L would not work

👆 yup. (one of a billion issues with the vim extension, though, careful when you're typing unsaved notes... very easy for the extension to ruin a ton of work very easily)

I've been trying the Awesome Emacs Keymap[1] lately because I figured Emacs keybindings were the default in terminals. I'm not sure that assumption was right, but they're pretty good [1]: https://marketplace.visualstudio.com/items?itemName=tuttieee.emacs-mcx

(I have never used Emacs before, other than to gawk at how badly it handled DPI scaling under Linux/Wayland)

@User, fwiw I mapped undo-redo keybindings to VSCode's native undo-redo stack rather than either the vim plugin or neovim.

There's a very very old issue filed about maintaining one undo stack (well, tree), but it was dependent on APIs being written in core and I think it's slowly happening ... perhaps next year?

Can anyone confirm that toggling a journal note and then hitting

enter

is broken before I dive into code?

> @User yeah, we can build it into the doctor command to clean up frontmatter @User Reading about

doctor

on Dendron.so, I see it goes through all the notes, not just the note you are looking for, so that should work. I guess all the files in docs/notes will get updated the next time you publish.

> I've been trying the Awesome Emacs Keymap[1] lately because I figured Emacs keybindings were the default in terminals. I'm not sure that assumption was right, but they're pretty good > > [1]: https://marketplace.visualstudio.com/items?itemName=tuttieee.emacs-mcx @User Thanks for this, I pushed for the Leo Editor to have the option of Vim bindings, which were added on, even though the project's originator is an Emacs guy. Since someone is working on a port to VSCode, this is a plus.

I've only seen screenshots of Leo, LeoVue looks pretty cool. I love that current editors are flexible enough to allow reasonable emulation of older ones

That's a new one... 😅

It's not so much an emulation as using vscode as a front end client for all the python code providing a backend, using leoIntegationBridge via websockets.

> Webview can't handle .svg images either. Converted to .png 's but still no joy, white version with an alpha channel is invisible, gray version the same for some reason. Might want to have MPE default to a .png version of any .svg for rendering @User turns out this is inaccurate, Webview can handle svg rendering, I was using a white Markdown "icon" witth an alpha channel, so I couldn't see it! Providing "mouse-hoover-text" mades this clear

@User interesting. you wouldn't happen to have repro steps, would you? 😅

You'll be the first to know if I figure those out 🙈

I have some notes on this destined for the docs, been working on setting up fork of dendron to generate a PR request with them losing y monitor has left me with various repo on different machine, (and differing states of the notes evolution), since your interested, I'll use what I ran into explicitly in the note.

> https://github.com/dendronhq/dendron/blob/master/packages/engine-server/src/config.ts#L14:L14 @User is there a clever way I'm supposed to import

DConfig

from

engine-server

into

dendron-next-server

? It's using private class properties, so just doing an import of the file means I'd have to modify the next server's babel config, I think. Figured I'd check before mucking around too much, as I see there's things like

@dendronhq/common-all

and such.

opps, did I not document how to add dependencies? 😅

run that anywhere inside the dendron repo

this will symlink engine-server to the next-server so any updates in one will automatically show up in the other