https://www.dendron.so/ logo
Powered by
# questions
  • u
    😄 Yep, I hope so too haha
  • g
    Yes, that's it.
  • r
    Hi folks, previously I created custom block and inline delimiters for markdown enhanced preview to avoid conflicts that were occuring if I tried to type "I wish I had $10 instead of $5". Markdown enhanced preview gets confused occasionally, not recognizing the block delimiters, the inline ones always seem to work. More troubling is when I do a Site:preview, the preview does not recognize the custom delimiters at all. What is the best way to make this all work nicely together?
  • f
    So First of all the in editor preview will be changed to the same engine as the Site:preview in the future. More on that here -> https://dendron.so/notes/17c61d62-f92e-4002-b8fe-9c05686e4bf9.html The question is what do your custom blocks and inline delimiters do? Depending on what their could be a config option in the future.
  • k
    added an additional features section to 
    dendron-next
    with folding as an item 🙂 @User https://dendron.so/notes/17c61d62-f92e-4002-b8fe-9c05686e4bf9.html#additional-features
  • k
    anything within a code fence should be ignored. you can do 
    I wish I had $10 instead of $5
  • u
    Cheers! look forward to seeing this!
  • r
    @kevins8 so is your suggestion to revert back to the defaults and deal with the situation above using a code fence? Would that fix the publishing issue?
  • k
    yeah, the inline $ delimeters shouldn't activate inside a code block
  • r
    Hi folks, ok I reverted the math delimiters back but continued problems with complex mathematics.
  • t
    Hi folks! Is there a way to remove the "From ..." html markup from the references?
  • f
  • t
    thanks for the link! I've tried changing the markdown-preview-enhanced.renderRefWithOutline setting to false, but the outline still appears. Am I missing something?
  • f
    Sorry no Idea, something could have changed, but I'm not sure.
  • t
    Thanks anyway, ideally I think this should work as parameter when referencing notes, maybe could go as a feature request.
  • f
    feel free to open one up in GitHub.
  • k
    can you paste the raw text? easier to reproduce with text 😅
  • k
    you found a regression. will update the markdown preview to accept the pretty config. as for general parameters, that's coming. i'm currently exploring using nunjucks to make dendron links more flexible. for example, you should be able to do the following to update refs on a per link basis. rfc coming soon!
    Copy code
    {{ ![[foo]] | config(prettyRef = false) }}
  • o
    Is it still possible to submit documentation issues? I don't see the edit on GitHub option anymore on Dendron.so
  • r
    Hi - thanks for the reply. All is well now, below the problem I had some rogue "old" delimiters which must have been confusing things.
  • k
    yes it is. just re-enabled the github edit option
  • m
    If I have multiple vaults and use CTL-L to add a new note, how can I tell what vault that note will go into? It seems like the “Create New” should give some indication of what vault it will create in.
  • b
    You need to set 
    lookupConfirmVaultOnCreate
    if you want to choose the vault a new note goes into see https://dendron.so/notes/eea2b078-1acc-4071-a14e-18299fc28f48.html. Otherwise it will go into the vault the currently active note is in
  • m
    Awesome. Thanks.
  • g
    Has anybody got trouble publishing with the classical v2 lately ? Here is the output of the buildpod action
  • g
    Copy code
    Run npm run dendron-cli -- buildSiteV2 --wsRoot .  --stage prod
  npm run dendron-cli -- buildSiteV2 --wsRoot .  --stage prod
  shell: /bin/bash -e {0}

> dendron@1.0.0 dendron-cli /home/runner/work/dendron/dendron
> dendron-cli "buildSiteV2" "--wsRoot" "." "--stage" "prod"

dendron-cli buildSiteV2

build notes for publication using 11ty


DendronError: error connecting
    at EngineConnector.init (/home/runner/work/dendron/dendron/node_modules/@dendronhq/engine-server/lib/topics/connector.js:45:23)
    at async getEngine (/home/runner/work/dendron/dendron/node_modules/@dendronhq/dendron-11ty/libs/utils.js:41:5)
    at async getNotes (/home/runner/work/dendron/dendron/node_modules/@dendronhq/dendron-11ty/_data/notes.js:22:18)
    at async TemplateData.getDataValue (/home/runner/work/dendron/dendron/node_modules/@11ty/eleventy/src/TemplateData.js:385:23)
    at async TemplateData.getAllGlobalData (/home/runner/work/dendron/dendron/node_modules/@11ty/eleventy/src/TemplateData.js:228:18)
    at async TemplateData.getData (/home/runner/work/dendron/dendron/node_modules/@11ty/eleventy/src/TemplateData.js:255:24)
    at async compile (/home/runner/work/dendron/dendron/node_modules/@dendronhq/dendron-11ty/index.js:32:3)
    at async BuildSiteV2CLICommand.execute (/home/runner/work/dendron/dendron/node_modules/@dendronhq/dendron-cli/lib/src/commands/build-site-v2.js:77:9) {
  status: 'unknown',
  msg: 'error connecting',
  friendly: undefined,
  payload: '{}',
  code: undefined
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! dendron@1.0.0 dendron-cli: `dendron-cli "buildSiteV2" "--wsRoot" "." "--stage" "prod"`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the dendron@1.0.0 dendron-cli script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/runner/.npm/_logs/2021-02-22T12_03_30_234Z-debug.log
Error: Process completed with exit code 1.
  • g
    Here is what the install npm dep says
  • g
    Copy code
    Run npm install
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated core-js@2.6.12: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142

> core-js@2.6.12 postinstall /home/runner/work/dendron/dendron/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"


> ejs@2.7.4 postinstall /home/runner/work/dendron/dendron/node_modules/ejs
> node ./postinstall.js


> nodemon@2.0.7 postinstall /home/runner/work/dendron/dendron/node_modules/nodemon
> node bin/postinstall || exit 0

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.1 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 1003 packages from 1149 contributors and audited 1004 packages in 38.153s

135 packages are looking for funding
  run `npm fund` for details

found 54 low severity vulnerabilities
  run `npm audit fix` to fix them, or `npm audit` for details
  • g
    Not sure to get were is the problem exactly
  • g
    My dendron-action.yml is like this
1...220221222...757Latest