Unfortuante that the tab bar is packed with all kinds of preview/bold/formatting options. I wish those could be moved under the tabs so I could fit more than 3 tabs without scrolling/pinning. (i know that it isn't really customizable yet based on having seen the ticket about the two md preview buttons)

my solution for now is to use the open editors tab dragged to the bottom and expanded horizontally

as for the md icons - the builtin preview we can't toggle but the others are part of a bundled extension which you totally can 😅

"markdownShortcuts.icons.bold": false,
  "markdownShortcuts.icons.italic": false,
  "markdownShortcuts.icons.strikethrough": false,
  "markdownShortcuts.icons.bullets": false,

> Unfortuante that the tab bar is packed with all kinds of preview/bold/formatting options. @User This can be customised -- I remove them like so in my workspace config:

json
{
  "settings": {
    "markdownShortcuts.icons.bold": false,
    "markdownShortcuts.icons.italic": false,
    "markdownShortcuts.icons.strikethrough": false,
    "markdownShortcuts.icons.bullets": false
  }
}

Ah, snap @User

haha, we were within seconds of each other 😛

I'd have been quicker if I didn't accidentally close my workspace 🍩

😇

I'm actually using a 5120x1440 ultrawide, so I'm not short on horizontal space - i just don't want those buttons where they're located.

Thanks for the settings tweaks though! I'll probably disable 'em since I don't use 'em anyway 💣

Maybe this feature request is kind of specific, but I would love to use dendron to get order to my R scripts/statistical analysis. I guess this would be possible if dendron would accept

.Rmd

files along with

.md

. But not sure how much the yaml header will infer with it (http://kbroman.org/knitr_knutshell/pages/Rmarkdown.html). The goal would be that the published/generated html files (e.g. via knitr) would include results from the executed code chunks. I guess this would be interesting also to people who are using Jupiter notebooks or python markdown. This will maybe open a new kind of use-case for dendron in the future if this will be supported.

Maybe prefix your suggestion with

!suggest

@User (then we could poll )

@User specific is great. for R files (or more broadly, anything that is not markdown), Dendron's convention is to keep them under an

assets

folder in your vault. for example, images are saved under

assets/images/

and referenced as

/assets/images/*

inside your notes. you could do the same today with scripts (eg.

assets/scripts/

or assets/r/`), navigate to them via regular vscode (cmd|ctrl p), and then include them as code chunks in your markdown. the preview accepts running code chunks. you can see the instructions here: https://shd101wyy.github.io/markdown-preview-enhanced/#/code-chunk vscode is also adding native support for notebooks so as that support becomes more mature, we'll probably look into making this process less kludgy. let me know if this works for your current use case or if there's something more you want to see 🙂

@User great suggestion! we are experimenting with@User so still getting used to all of the turtle's capabilities 😄

@User Thanks, tried it out and it seems that MPE is supporting execution of code chunks : )

@User glad to hear it! i've created a workflow on the docs since this has come up a few times now. if you discover improvements to this, edits are very much welcome 🙂 https://dendron.so/notes/8514245e-6405-4759-8dda-ab77cf173075.html

I finally carved out some time to figure out how pods relate to the publishing workflow and got my notes published via Jekyll -- awesome work @User. Did you have any ideas about how we might make

jekyll serve

an option for local previewing? Right now the pod export behaviour of re-exporting all the files is a little slow (only 123 notes so far). I think I also hit a bug with how it processes template directives in markdown syntax as I get some Liquid warnings about Go template syntax in some of my notes, but I should be able to figure that out 😄

I should clarify -- the slowness is in Jekyll's rendering, the actual pod export finishes in well under a second

awesome!

for jekyll serve, i want to add a

Dendron: Preview Pod

command that runs jekyll serve under the hood

in the meantime, @User has published a nice guide about how to do it manually https://dendron.so/notes/63b184f7-1901-4580-af40-97ef87069a04.html

as for building being slow, this is currently because 1) we rebuild all notes all the time 2) the way we are processing hierarchies in the jekyll template

i've added an

--incremental

build method that you can trigger with the following keybinding. it's not documented yet because it relies on having

rsync

locally and i need to do some work to have a fallback

{
    "command": "dendron.buildPod",
    "key": "cmd+k b",
    "args": {
      "incremental": true,
    }
  },

i also have a todo to change how our jekyll template processes hierarchies since that's very sub-optimal right now

honestly, part of me is thinking that it (publishing) should all be re-written in

go

and use

hugo

for everything. but that might be a little too much to take on at the moment 😅

This is awesome, thanks! FWIW I think you made the right choice to work with what was available off the shelf, because it demonstrates the potential of the idea. I love that you've invested in portability of the data too. Once I've cleaned up my hierarchy a little I'll publish my notes publicly, then I really want to get Draw.io exports working. I'm really keen to contribute

yep, demonstrating the potential of the idea is why dendron is built on top of vscode in the first place 😅 https://dendron.so/notes/683740e3-70ce-4a47-a1f4-1f140e80b558.html#why-is-dendron-built-on-top-of-vscode there's a lot of undifferentiated work when building a note taking editor and there's a lot that's different about dendron that has nothing to do with that. wanted to prove that this hierarchal note taking thing would work for more than just me 🙂 when you do publish, drop me a line and we can feature you on our showcase ;) https://dendron.so/notes/3a82c5ff-7945-46ae-8bf9-3b2275fc6642.html

Yep, VS Code is such a capable editor in its own right, and has such a solid community. I really liked some elements of Obsidian's UI, but switching between two similar but very different tools was really awkward for my muscle memory and I found I was using Code for writing and Obsidian for navigation. I really need to read your notes on the LSP and take a look at the code. It'd be so cool if the Dendron-specific syntax could be separate from the file format, which might allow mixing Markdown/RST, or maybe enable notebook-style formats

I'm not sure how that would work, whether you'd need a format-specific LSP that would proxy to a markdown/rst LSP and a Dendron LSP or whether a single editor buffer can interact with two LSPs? From what I've read there's little guidance on multiple LSPs interacting within a workspace

at this point, i have more notes for lsp than code but that should change by next week 😅 as for supporting rst, i envision a future where you can choose the markup language to use with dendron, either on a vault basis, via the frontmatter, or through a file extension. the lsp would interpret the file accordingly. i personally have a soft spot for asciidoc! that being said, this would be a pretty major change and not one that i could commit to personally this year (though I can give pointers if others want to take it on 🙂 )