Dendron

Is there a reason that so much whitespace is used on the left-hand side of the user interface? It would probably look better if it were centered.

I think the left bar + middle is centered, and then the TOC is hanging off from the side which throws off the centering.

I don't think there's an issue about this, would you mind sending a bug report to fix this? https://github.com/dendronhq/dendron/issues/new/choose

https://github.com/dendronhq/dendron/issues/2420

The bottom of text is being cut off on the right-hand nav. Are you guys seeing this?

Is your browser zoom set to 100% or > 100%?

Increasing it above 100% actually helps to fix the problem. I can also manually edit the `lineHeight` CSS property to help fix it.

If you increase `lineHeight` to `1.3` and change `padding` to `7px 0 4px 16px` it stops cutting off the bottom of the `g` character, while preserving roughly the same look.

Any ideas why Dendron isn't initializing properly?

```
info: {"ctx":"WSUtils.handleServerProcess","msg":"subprocess running","pid":31032}
info: {"ctx":"startServerProcess","msg":"post-start-server","port":22755,"durationStartServer":1039}
info: {"ctx":"dendron.reloadIndex:run","msg":"pre-execute"}
info: {"ctx":"ReloadIndex.execute","msg":"enter"}
info: {"ctx":"ReloadIndex.execute","durationEngineInit":200}
info: {"ctx":"ReloadIndex.execute","msg":"exit"}
info: {"ctx":"dendron.reloadIndex:run","msg":"post-execute"}
info: {"ctx":"reloadWorkspace","msg":"post-ws.reloadWorkspace"}
info: {"ctx":"reloadWorkspace","msg":"exit"}
info: {"ctx":"postReloadWorkspace","msg":"same wsVersion"}
info: {"ctx":"postReloadWorkspace","msg":"exit"}
debug: {"ctx":"TreeView:getChildren"}
info: {"ctx":"TreeView:getChildren","msg":"reconstructing tree: enter"}
info: {"ctx":"setupViews","msg":"init:treeViewV2"}
info: {"ctx":"setupBacklinkTreeView","msg":"init:backlinks"}
info: {"ctx":"TreeView:getChildren","msg":"reconstructing tree: exit"}
info: {"ctx":"activateWorkspace","stage":"prod","msg":"enter"}
info: {"ctx":"togglePluginActiveContext","state":"togglePluginActiveContext: true"}
info: {"ctx":"_activate","msg":"fin startClient","durationReloadWorkspace":1250}
error: {"line":1,"column":0}
error: {"ctx":"showInitProgress","msg":"issue initializing Dendron"}
info: {"ctx":"updateDecorations","payload":{"error":null,"decorationsLength":2,"diagnosticsLength":0}}
debug: {"msg":"Note opened","fname":"kubernetes.pods.md.git"}
debug: {"msg":"Note opened","fname":"settings.json"}
```

Hmmm is this when initializing a new workspace, or when opening an existing workspace where the extension is loading up?

https://github.com/pcgeek86/opensrc-notes

tried cloning in the workspace but it didn't seem to have all the notes that you had in your logs

the problem might be from `kubernetes.pods.md.git` - dendron currently has an issue parsing `.md` (this will be fixed in next weeks release)

Oh I forgot to commit the pending changes

I pushed the pending changes, so you can see that file. I probably created the file manually, rather than using the "correct" method of doing a Dendron lookup. Is there some kind of linting or "health check" command I can run to ensure the files in my "vault" are using the correct syntax? <@!711453238653616139>

dendron should warn you about badly formatted files, the `.md` was an edge case that <@!847806175152177182> fixed and will be landing next week. i'm able to load the workspace now - has this solved your problem?

As an added note about other markdown files in general, outside of the `*.md.*` edgecase:
- `Dendron: Doctor` commands can be helpful if having plain markdown files in your vault that need front matter taken care of, with commands such as `fixFrontmatter`: https://wiki.dendron.so/notes/ZeC74FYVECsf9bpyngVMU/#fixfrontmatter
- If you have many markdown files you'd like to import into your vault, you can also follow the Markdown Import Pod directions: https://wiki.dendron.so/notes/f23a6290-2dec-45dc-b616-c218ee53db6b/

Nope, I'm still seeing that obscure error.

I tried deleting the `.dendron.cache.json`, and reloading, but that didn't change anything either.

I just disabled a bunch of extensions, and still doing the same thing

I'll test out your repo in about 20min, see if I can notice anything weird

Looks like Dendron might be tripping up on `Cloud Storage.md`. Try:
- Rename `Cloud Storage.md` to `cloud-storage.md`
- Delete `.dendron.cache.json`
- Reload Window (Command Pallet -> `Developer: Reload Window`)

At least, for some reason, that seemed to fix the problem for me with the reload index failures that kept coming up

The same error occurs when I launch VSCode even without opening a workspace <@!336685159648722944>

I can't seem to replicate the error. Questions:
- You said you tried disabling other extensions. If Dendron is disabled, and you Reload Window, does it still appear?
- If it doesn't appear, does it start appearing once Dendron is enabled again, after a Reload Window (by itself as the only extension)?
- If so: what is the VSCode version you are running, and what OS?

```
info: {"ctx":"Logger:configure","msg":"exit","logLevel":"info"}
info: {"ctx":"_activate","stage":"prod","isDebug":false,"logLevel":"info","logPath":"c:\\Users\\TrevorSullivan\\scoop\\apps\\vscode\\1.64.2\\data\\user-data\\logs\\20220215T124139\\exthost4\\dendron.dendron","extensionPath":"c:\\Users\\TrevorSullivan\\scoop\\apps\\vscode\\1.64.2\\data\\extensions\\dendron.dendron-0.82.0","extensionUri":"c:\\Users\\TrevorSullivan\\scoop\\apps\\vscode\\1.64.2\\data\\extensions\\dendron.dendron-0.82.0"}
info: {"ctx":"DendronExtension","msg":"initialized"}
info: {"ctx":"_activate","msg":"initializeWorkspace","wsType":"NONE","currentVersion":"0.82.0","previousWorkspaceVersion":"0.0.0","previousGlobalVersion":"0.80.2","extensionInstallStatus":"UPGRADED"}
info: {"ctx":"_activate","msg":"dendron not active"}
error: {"line":1,"column":0}
```

Error disappears when Dendron extension is disabled. <@!336685159648722944>  Just tested now.

As soon as I re-enabled the extension (without reloading) the error appears.

Let me uninstall it and see if it resets anything

Yeah, I was about to ask about reinstalling the extension, since it seems to be trying to throw an upgraded message

Nope, as soon as I install it, same error

Looks like you're on Windows with latest VS Code, I'll pop open a VM to see if I can get it

I've just tried on a VM, and am unable to replicate your error :\ (I tested via scoop install and also a manual install, with current release of VS Code)
- You get the same log output when opening a directory that isn't related to Dendron?
- And when reinstalling it, is it still attempting to throw upgrade information?

And to add to those questions:
- If other extensions are enabled/active, but not Dendron, is the error also not appearing?

Side note: I asked another Windows user who had difficulty getting up and running initially, and for whatever reason, uninstalling and reinstalling VS Code entirely fixed his problems.

Correct, I re-enabled a bunch of extensions, and disabled Dendron. C#, Gitpod, Jupyter, AWS Toolkit, Code Runner, Kubernetes, Python. The error does not appear when Dendron is disabled.

I don't even need to open a directory. Dendron just throws the error message in an empty VSCode window.

The only thing I can think of as a last check is to have VS Code Insiders or VSCodium installed alongside your current VS Code setup, and then configure the new app with only Dendron. This would isolate configs in a way that would show whether there is any difference (because that error output looks like a config error, like a JSON config problem).

If Dendron is in a fresh install, working, would help in pointing out something weird in configurations somewhere. Have you always been getting the error, since you installed Dendron itself?

Could be an error somewhere in `keybindings.json`, maybe?

I don't have VSCode Insiders or VSCodium installed on my system.

Oh, but you're suggesting trying it out. I see 🙂

I didn't get it initially when I first learned about and installed the Dendron extension. The extension used to initialize properly, when I first installed it and created a vault. 

I took a look at my VSCode key bindings, and don't see any problems with it. In fact, the file is empty. 🙂

I just wiped out my VSCode Settings JSON file and reloaded the window. The error from the Dendron extension changed very slightly. See screenshot.

what happens when you add `{}` to your keybindings file?

Is there any way to enable debug logging on the extension to see where the error is occurring? <@!336685159648722944>

you can set `dendron.loglevel`. see https://wiki.dendron.so/notes/19a0ea9d-7292-4a68-bc6f-ffd462a54bc5.html#dendronloglevel

That didn't provide any additional detail beyond the logs I already sent.

yes please. apologies, haven’t had much time to look into this this week so will set aside some time tomorrow. in the ticket, can you paste the output of diagnostics report?

hey <@!782062916329013268> , instead of `{}` can you add `[]` to your `keybindings.json`?

Want to hop in the General voice chat <@!711453238653616139> ?

for bystanders - this issue is fixed in the latest 0.83 version of dendron that will be coming out later today

Quick question - I know that some of the other markdown extensions for Dendron interfere with wha Dendron does.

I’m trying to make it so that when I’m typing a list in markdown hitting return continues that list

usually, markdown all in one does this but its also fairly aggressive at overwriting built-in keyboard shortcuts and snippets (aka it conflicts with both dendron and built-in vscode primitives)

Right that’s what I’m trying to avoid

Is there a Dendron-friendly setting for this?

Not a huge deal, but it does feel great if I’m creating a numbered list if I don’t have tow rite out all the numbers

got it. if you submit a feature, we can track it on the roadmap 🙂 https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=feature_request.md&title=

how to have a well organised footnote ? I am used using `^[ blah blah ]` whats the alternative

like i don't remember  which footnote number was what

Is there a way of having a kanban in dendron?

https://github.com/dendronhq/dendron/issues/2428

There are a few VSCode extensions people have used for Kanban boards. I think this one is mentioned most often: https://marketplace.visualstudio.com/items?itemName=coddx.coddx-alpha

Inside Dendron, we also use Airtable for task management. This is thru Airtable Export Pod. This means that you can visualize your task notes in a Kanban.

You might want to check this link: https://wiki.dendron.so/notes/y84kARyQhdUcyRG33pT2i/

This is when working to export with Airtable?

That may be a version of the troubleshooting issue seen here: https://wiki.dendron.so/notes/oTW7BFzKIlOd6iQnnNulg/#troubleshooting

Though, we should improve the error message output 😅

I read that part but the error I Am getting is not the same

https://bin.disroot.org/?22446c41666ee019#3CuVmJdPtDw578Rt8fMMqtDaSphC6q1oUkWZaHEpbzrm

and this is my [svcconfig](https://bin.disroot.org/?21108455a7205d61#CPG7p6MpPPR2NzPi2DfFYPgJ9T7L1DGBAcvuowRogvQW)

Ah, we have an PR in the works right now to help with this message output: https://github.com/dendronhq/dendron/pull/2426

This likely has to do with some kind of tag mismatch with your local notes and field values inside of Airtable. I'd have to see an example note you are trying to export to Airtable.

What does your `sourceFieldMapping` look like in your `config.personal.tasks` file?
Example:
```yaml
sourceFieldMapping: {
  DendronId: id, 
  Name: title,
  Description: desc,
  Notes: {to: body, type: string},
  Owner: owner,
  Type: {type: "singleSelect", filter: "tags.type.*", to: "tags"},
  Status: status,
  Due: due,
  Priority: priority,
}
```
And:
- In Airtable, what are the field types for:
  - status
  - priority
  - owner
- Are they `singleSelect` in Airtable, or are they `Single line text`?

Also note: In `sourceFieldMapping`, the `key: value` is a reflection of `AirtableField: DendronFrontmatterKey`

It looks like your error is being caused by one of your task note frontmatter fields not mapping properly

```
sourceFieldMapping: {
  DendronId: id, 
  Name: title,
  Description: desc,
  # Special type here refers to body of your note, the markdown
  Notes: {to: body, type: string},
  Owner: owner,
  # singleSelect type, targeting tag using `#type.*` format
  Type: {type: "singleSelect", filter: "tags.type.*", to: "tags"},
  Status: status,
  # use yyyy-mm-dd format (ISO) for this example
  Due: due,
  Priority: priority,
}
```

Ah, okay, it looks like Airtable fields won't expect empty fields unless you specifically add empty field options in `single select` configs. To do this:
- For status field in Airtable
  - Customize field type
  - Add a new option that has an empty value
- Repeat for Priority
- Repeat for Owner
- Repeat for Type

See if that allows you to then export

I did it like this and still getting the same error

When it fails to export, can you run the `Dendron:Dev: Open Logs` and look for lines like:
```
Finished Airtable Export. 0 records created; 0 records updated. Error encountered...
```
I'd like to know what these lines include, since that should show us why it is failing

`{"level":50,"time":1645316367145,"pid":23067,"hostname":"fiona","name":"dendron","msg":"Finished Airtable Export. 0 records created; 0 records updated. Error encountered: {\"payload\":[{\"message\":\"Error during Airtable Export. undefined\",\"name\":\"DendronError\",\"status\":\"unknown\",\"payload\":\"[{\\\"fields\\\":{\\\"DendronId\\\":\\\"uLQiGcJzOPi29hWai1a8w\\\",\\\"Name\\\":\\\"Cut\\\",\\\"Description\\\":\\\"\\\",\\\"Notes\\\":\\\"\\\\n## Summary\\\\n\\\\nWhoa! This is a test!\\\\n\\\\n## Details\\\\n\\\\nThe Sun is hungry. Planet-eating hungry.\\\\n\\\",\\\"Owner\\\":\\\"Ivan\\\",\\\"Status\\\":\\\"\\\",\\\"Due\\\":\\\"2022-02-17\\\",\\\"Priority\\\":\\\"\\\"}}]\",\"innerError\":{\"error\":\"UNKNOWN_FIELD_NAME\",\"message\":\"Unknown field name: \\\"DendronId\\\"\",\"statusCode\":422}}],\"errors\":[{\"name\":\"DendronError\",\"status\":\"unknown\",\"payload\":\"[{\\\"fields\\\":{\\\"DendronId\\\":\\\"uLQiGcJzOPi29hWai1a8w\\\",\\\"Name\\\":\\\"Cut\\\",\\\"Description\\\":\\\"\\\",\\\"Notes\\\":\\\"\\\\n## Summary\\\\n\\\\nWhoa! This is a test!\\\\n\\\\n## Details\\\\n\\\\nThe Sun is hungry. Planet-eating hungry.\\\\n\\\",\\\"Owner\\\":\\\"Ivan\\\",\\\"Status\\\":\\\"\\\",\\\"Due\\\":\\\"2022-02-17\\\",\\\"Priority\\\":\\\"\\\"}}]\",\"innerError\":{\"error\":\"UNKNOWN_FIELD_NAME\",\"message\":\"Unknown field name: \\\"DendronId\\\"\",\"statusCode\":422}}],\"message\":\"Error during Airtable Export. undefined\"}"}`

Hey <@!364291864557256704> , Do you have a field name `DendronId` in your Airtable?

I was able to repro this error only if the table in Airtable does not have a field name `DendronId`(case-sensitive).

thanks for the support <@!847806175152177182> <@!336685159648722944>

Can Someone help me understand block reference w/ some example

Like those it men that we can specify o single line. which has the anchor `^` next to it?

I believe it works with contiguous lines as well, as long as they're not separated by newlines

so  with a block like
```markdown
1 ^anchor
2 here's a line
3 here's another one
4 and here's another one
5
6 there's been a break
```

a reference to `anchor` (i.e. `![[note.example#^anchor]]`) will embed lines 1 - 4