yup, as far as I know this only works in the editor for now but you can definitely submit it as a feature request here: https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=feature_request.md&title=

Good todo, thanks for the tip @johndendron29

legacy-site-build-issues

Pretty sure I screwed something up but I keep getting this when trying to search (cmd|ctrl+l)

make sure your in a dendron workspace (you have to open dendron.code-workspace file)

I am. lookupNote and schema all work, just that one doesn't

lookup used to be one command that had different modifiers for

note

and

schema

. This has been removed and separated. So The command key

dendron.lookup

doesn't exist any more and should be

dendron.lookupNote

and

dendron.lookupSchema

respectively.

I am confused by so many lookupnote am using 0.65.1

The second and third are keybindings for looking up journal notes and scratch notes. It's displayed in the keybinding UI like that because under the hood both are just lookup with specific modifiers. I think this could be resolved if we register them as a different key to avoid confusion. I'll look into this tonight.

Maybe change the name?

That's the plan 🙂

Create generic note under current note?

I'm at this note. i want to create a new note that's

pro.learn-orgmode.i.<something>

Is there a command for this?

Go to lookup (CTRL+L) and then write the

<something>

and Enter. Does that help?

There should be only two tho 👀

no

Which Doctor fixes are absolutely necessary to run after letting an external tool add a note to a vault? fixFrontmatter only?

when lookup is triggered within a note, that note's name will be pre-populated and pre-selected in the lookup bar. If you just type in

<something>

, it will create a note

<something>.md

. You need to type it after the pre-populated note name like so

pro.learn-orgmode.i.<something>

. Alternatively, you could do the following. 1. In the note

pro.learn-orgmode.i

, write

<something>

2. Select the text

<something>

3. Trigger note lookup (ctrl/cmd + L) 4. Enable

selection2link

modifier by clicking on the chain icon on the top right corner of the lookup bar (more about this here: https://wiki.dendron.so/notes/ad270a7d-2aed-4273-8319-eb6536e38b29/#selection2link) 5. Hit enter At this point, a note

pro.learn-orgmode.i.<something>

would be created and opened. Also, in

pro.learn-orgmode.i

, the text you have selected in step 2 will be converted into a wikilink to the new note. Also note that

selection2link

can be set to be the default behavior or lookup by setting it in `dendron.yml`: https://wiki.dendron.so/notes/F9LWJEjscrGkxnYi2JNby/#note Or you could add a separate keybinding for lookup with this modifier enabled:

json
{
    "key": "{desired keybinding}",
    "command": "dendron.lookupNote",
    "args": {
        "selectionType": "selection2link"
    }
}

yes, that will create the frontmatter that Dendron needs to read in order to index it as a note

Very precise thank you will try this

Regarding NEXTjs publishing using Github Actions: How can I change the favicon of the published site?

Hi! I did a quick search an didn't see anything posted earlier so I thought I'd ask a couple questions: (1) The default preview is really -- ugly (sorry :(), is there anyway to change its style? In particular it tries to deduce the "title" of the document by the last node (not sure if right terminology) of the document name. In one particular case, this is "6" for me, which is slightly ugly. Maybe I could rename the last node to something more logical. But mainly, it's that the background is this odd gray color. I'd prefer the preview background to be white whilst the rest of VS Codium is using the Visual Studio dark theme. (2) Whenever I'm typing notes in a markdown file that is open, the scroll position jumps up and down. Is anyone else experiencing this? In other words, it's like someone is moving the scroll bar of the window up and down as I type. It's really distracting. Thanks!

The default preview

A nice looking preview, courtesy of a github-styled preview plugin (what I'm actively using).

1: You can disable this title by setting

useFMTitle: false

in your

dendron.yml

(see https://wiki.dendron.so/notes/f83c1d87-eac0-48f3-a5cf-8a69989d8ec1/#usefmtitle). For the colors, we're working on allowing custom themes for the preview. 2: That shouldn't be happening, could it be another extension doing this?

Thanks! Hmm, for (2), I wonder if it's the vim plugin. I just did a fresh install of VS Codium and I believe it's the only plugin I have installed aside from Dendron. I'll do some testing and report back.

Hmm, yeah, disabling the VSCodeVim vim plugin doesn't fix the problem.

1 - for styling, we do plan on adding support for this, we just are lacking bandwidth at the moment. if this is important for you, please add a 👍 and add relevant details to this ticket -> https://github.com/dendronhq/dendron/issues/1171 part of the way we prioritize tasks is based on user feedback to open issues 2 - can you do the following to see if its a dendron issue vs an extension issue? - do a clean install of a VSCode flavor you do not currently have (eg. VSCodium if you have VSCode or vice versa) - install only the Dendron extension - see if your issue reproduces

Hi, I just discovered Dendron because I was looking for a notion alternative and so far I'm really impressed. 👍 I have two questions at the moment: 1. Is Dendrop intended to also save files (that are not md or images). For example I have drawio files or some files in a proprietary format I'd like to tie to my notes permanently (no hard coded path on one system). How would I do this? The function "paste file" just lets me enter a path. And if such a function exists would it help me with duplicate file names? (because I probably won't have an overview if I already attached example.xfc to a note already) 2. I noticed that it's easy to add code snippets with

python
print("python")

where does Dendron pull the syntax highlight information? Is there a list of supported languages somewhere? Thanks for all your work.

I had to reinstall my OS and backed my old vault up