Off topic question: how do you folks keep VSCode's

settings.json

file organized? I ended now with a long list of non-sorted entries which makes it almost impossible to compare settings between installations. My current issue are differences in behaviour between a Dendron installation on a mac and on a windows system

do you keep settings per project or a global settings file? I use comments >

// ==

to separate my settings. this makes it possible to use search editor to search for

==

to sort by categories

json
5 results - 1 file

~/Library/Application Support/Code - Insiders/User/settings.json:
   1  {
   2:   // == Workbench
   3    // adds a blue underline to tabs, makes them easier to distinguish

   7    },
   8:   // == Editor
   9    "editor.lineNumbers": "relative",

  12    "editor.unusualLineTerminators": "off",
  13:   // == Unsorted
  14    "workbench.editor.enablePreview": false,

  30    "debug.onTaskErrors": "debugAnyway",
  31:   // === Language Specific
  32    "[typescript]": {
  60    },
  61:   // === Extensions
  62    "markdownSnippets.markdownFolder": "/Users/kevinlin/workspaces/kevin-garden/templates",

interesting thing i noticed today, i think i prefer not using conventional commits. i've always used them as it made sense, but i genuinely like the simplicity and readability of committing like: [scope] description of change it looks nice in the gitlog, because the scope is always lined up, whereas the difference in character length w

feat

fix

etc unaligns the scope in other cases. also it should be easy to generate a changelog from this. however this does nothing in terms of the semantic versioning, which is a bit of a tradeoff. i was also always annoyed by the usage of two redundant verbs, like

chore: fix up the blah

, like is it a chore or a fix. anyways. thats my rant

hey guys

i have a question

dendron uses auto save or can we use manual save

no built in auto save as far as i know. there is local save (manual), there is also dendron sync which will do a push pull update to github repo

if you use dendron with a workspace, it should autosave whenever you switch windows

“You can’t be dendron pilled and not love schemas” - me, earlier today

there seems to be a lot of functionality here that I don't need. I'm a pretty novice developer and was wondering where there's anything simpler that would be compatible with Dendron. I'm having difficulty getting reveal working.

Hello guys

Is it possible to add a better file tree UI in dendron?

Something like in Obsidian

In the Dendron section on VS code, check the “Tree View” section

VSCode minimap users, help get this regression sussed out:

+

Hello, I just installed dendron and I would like to know if I should use vs code built in markdown preview or the extension named Dendron markdown preview. The extension does not open sometimes and does not have the feature showed in the docs it links to while the vs code built in preview does not display math blocks for example

Dendron now comes with a built-in preview the extension is outdated afaik. The built-in markdown preview doesn't understand the dendron-specific parts. Hence I'd use the Dendron preview

apologies if this is in the wrong spot, but i'd love to hear the reasoning behind gpl style license over mit style license. i've been thinking about licenses lately for open source projects i pursue, in general. a part of me wants to go the MIT license because it's so permissive / easy for others to use. on the other hand, i want to contribute to the free software movement, and like the gpl style licenses for that even though they are a bit less simple and cause some more difficulty to use. does anyone have thoughts / reasonings behind this? would love to hear about it. cc @kevins8

Dendron went with the AGPLV3 license. This is to satisfy the following requirements: - we wanted to keep our product open source and available for others to build on top of - we wanted to build a sustainable business on top of Dendron (this would be harder to do if someone just made a proprietary fork of Dendron) It was because of the latter that we did not go with MIT or Apache Version 2. That being said, we did implement an End User License Agreement for all pull requests which lets us relicense when necessary. This gives us room to accommodate individuals and organizations that absolutely cannot work with the AGPLV3 license

Yeah it’s interesting, I think I really like GPL-style because it encourages virtues that a lot of open source people care about, continuing to keep the software free. The tradeoff is it’s a bit trickier to work w when u fork it. I want to go MIT route but I’d add to your second point that I like how GPL somewhat mandates transparency. Someone could create a proprietary fork for a project, maybe, and create a more enticing business model for end users, but we don’t know how and we can’t see the code. So people could adopt a non-transparent project, which would kind of suck.

That’s what scares me about MIT a bit, I guess.

Just curious, has the user portal been put on hold?

i think anyway you go, there are tradeoffs. there are plenty of companies that have successful mit/apache licenses, there are also those that do it with agplv3 or open-ish licenses like server side and elastic. figure out what tradeoffs make sense for you and go with it. one thing I will add is that it is easier to go from a more restrictive license to a less restrictive license vs the other way around

yes - been bad about communicating this. the internal performance work is taking a little longer than expected and we want to focus on that right now since its more central to the core dendron experrience

What makes it harder to go from MIT to AGPLV3

the main one is that gpl v3 forces anything that uses your code to also be gpl v3

Oh wow, moving that plus icon in the tree view, from the left of the title, to the right makes so much sense. Thank you. Keep up the good work 👏 Bravo

I came to Dendron via Obsidian. Trying to figure out what it is all about. It seems to be written in a foreign language. I'm not a coder.

hey! the best way to figure it out might be through the official tutorial. the getting started guide is here: https://wiki.dendron.so/notes/678c77d9-ef2c-4537-97b5-64556d6337f1/ but basically it would be: 1. Install Visual Studio Code (this along with the extension is essentially the way most use Dendron, just like you have the Obsidian app on your computer) 2. Install the Dendron extension in Visual Studio Code