I've been using this extension for a few days now ...
# questions
l
I've been using this extension for a few days now https://github.com/patleeman/VSNotes with this extension, I setup a "notes" directory in ~/notes/ and the extension uses this directory regardless of my current workspace no matter what workspace I'm using, that VSNotes extension provides access to the same directory filled with md files it's nice... but it's also a dead project and under-developed and Dendron clearly has waaay more functionality šŸ™‚ for context, I use ~20 workspaces and maybe ~40 git repos for my work I'd like to add Dendron based documentation to some of these repos but I'd also like to have my personal notes (e.g. ~/notes/) always available regardless of which workspace/repos I'm currently working in these would be segregated from anything backed by a git repo so I would specifically want to avoid linking these together does this make any sense? šŸ˜„
f
Hi again Lodra. I think that makes sense! I expect other folks will have different approaches to this, especially now that it's possible to blend Dendron notes into other repos (what Dendron calls "native workspaces", https://wiki.dendron.so/notes/lamzybrD6SgQlJ9BpwkQk/ ). I personally have 4 Dendron "vaults" (each a different folder or repo). I sync them with Dropbox, not git, but I can still choose which of them to share with other devices or people. As for the specifics of setting up workspaces the way you'd like, I'm probably not as able to give suggestions as people like @ScriptAutomate , @Joshi , @kevins8 , or @hikchoi would be. I switched to using VS Code primarily for Dendron notes, and don't really use workspace features for the few static sites I maintain though git repos.
k
you can use [Local Config Override](https://wiki.dendron.so/notes/7tlxi5ejnnb8idhc1943zmp) to do this. create the file
$HOME/dendronrc.yml
and add the following
Copy code
yml
workspace:
    vaults:
        -
            fsPath: $FULL_PATH_TO_YOUR_NOTES_VAULT
            selfContained: true
            name: $NAME_OF_YOUR_NOTES_VAULT
dendron will then know to reference that vault in every workspace
l
well that's super cool I'm off to go try it out thanks!!
k
let us know how it goes (note: it's still experimental so there may be edges šŸ˜… )
l
I got a chance to test it out some tonight and I think I've got it working! there was definitely a bunch of trial and error but I'm learning Dendron for the first time and apparently in a non-standard way šŸ™‚ There's a couple of quirks for getting it setup and one real functional problem that limits use how much feedback would you like?
k
as much as you'd like to share šŸ™‚
as mentioned, the local config override is still considered alpha
l
The setup is a bit tricky because you need to start with Dendron initialized in the active workspace I'm not sure what the right config is for me yet but for tonight's test, I initialized a Dendron workspace in "~\test\" and I wanted a vault in "~\Personal Notes\" without a workspace initialized When running the "Add Vault" command, you cannot specify the path to create a local vault in just a name as shown in the screenshot so after creating a new vault, I had to copy the files to "~\Personal Notes\" manually and cleanup references to it from "~\test\dendron.code-workspace" and "~\test\dendron.yml" as well Nothing crazy here but a better workflow is certainly possible or I'm just doing it wrong šŸ™‚ Then I setup the dendronrc.yml file as you described this pretty much works as advertised nice!
After doing this, I can use multiple vaults and choose where notes are created there are 2 problems that probably need some code changes to resolve
First is a bug This is triggered by the "Vault Add" and "Vault Remove" commands at least The contents on my dendronrc.yml file are merged into the workspace's dendron.yml file thus producing a name conflict I can correct this manually by removing the duplicate from dendron.yml and reloading
if you aren't messing with vaults frequently, this isn't a big deal but again, complicates the setup process a bit
The second problem is a bit more general Dendron requires that the active workspace is initialized for Dendron i.e. it needs a dendron.yml, the "dendron.rootDir" setting, etc. (Note that I'm guessing on the details) so when I switch to a different workspace which is not configured for Dendron, then Dendron is simply inactive This is despite the vault being configured in my dendronrc.yml file Maybe this is by design? Maybe this can be solved by adding more config into my dendronrc.yml file?
k
thanks for the feedback. 1 will be fixed. for 2, that is currently by design but we are looking to enable a global vault since there have been a number of people bringing it up
would you mind creating an issue for 1 and optional a feature request for 2?
l
Sure. I’m off to sleep for the night but I can create those tomorrow
4 Views