https://www.dendron.so/ logo
Powered by
# questions
  • k
    got it. if you ran the CLI while vscode is running, it will write its own .dendron.port file and advertise a false port
  • k
    if you run 
    open logs
    , you should see the following line near the beginning 
    {"level":30,"time":1618725970350,"pid":12531,"hostname":"kevins-mbp.lan","name":"dendron","ctx":"_activate","msg":"post-start-server","port":49204}
  • k
    you can manually pass in the port number instead of the 
    cat
    cmd
  • p
    Yep I can confirm what I see in the logs is different from 
    .dendron.port
  • p
    Copy code
    {
  "level": 30,
  "time": 1618755678658,
  "pid": 2396224,
  "hostname": "manjaro",
  "name": "dendron",
  "ctx": "_activate",
  "msg": "post-start-server",
  "port": 35553
}
  • p
    Where as 
    .dendron.port
    is 
    38595
  • p
    The CLI overwrote the correct port when I ran it earlier ?
  • k
    yeah. the CLI uses 
    launchEngineServer
    command in the background which sets the 
    .dendron.port
    . need to add a flag to disable that behavior (by default)
  • p
    Gotcha, I ran 
    Developer: Reload Window
    and retried, works fine now
  • p
    Final question, is it possible to pass some content to the note created by the CLI ?
  • k
    yeah, the reason the 
    --enginePort
    option isn't as widely documented is because I'm still working on the UX 😅
  • k
    not right now but the CLI was just launched so actively adding features. feel free to send a feature request 🙂
  • p
    No worries, the price to pay for being on the cutting edge I guess haha
  • k
    currently, you can just append to it using 
    echo
    since lookup generates the frontmatter
  • p
    Yeah, you're right. I already have the filename, so I'll append what I need directly
  • p
    Thanks for the help Kevin, much appreciated ❤️
  • k
    👍
  • p
    I came across something earlier, not sure if a bug or not. Lookup seems to only show 28 entries/notes, and if I enable the 
    directChildFilter
    filter, it doesn't actually pull up all the sub hierarchies
  • k
    hmm, so we paginate by default on 50 entries. the directChildFilter limits the results to only the immediate children of the current note
  • p
    Tree view vs Lookup with directChildFilter filter
  • p
    Not sure if this is the expected behavior ?
  • k
    hmm, so if i understand, the tree view shows all the results but lookup does not if you enable directChildFilter?
  • p
    Correct, from the tree view you can see all the direct children, but the lookup doesn't pull them up when directChildFilter is enabled. And even when it's disabled, I don't get 50 results
  • p
    So not sure what could be the problem here ?
  • k
    hmm, i'll look into it. can you put the details in a bug report?
  • m
    The problem of launching the site preview: Following the tutuorial , after inputting "dendren.sitePreview", the error occurred...and I've no idea of solving it. Asking for the help, thks a lot.
  • k
    hmm, usually this means that the node dependencies didn't install correctly. can you go into your workspace root, remove package.json and run site preview again?
  • j
    @User @User 👋 I hit this problem due to my port 8080 being occupied. Sometimes you may get a helpful error msg if you open up VS Code Dev Tools (In VS Code Ctrl+Shift+P; Then 'Developer: Toggle Developer Tools') Then rerun the Site Preview command. Do you see any red error messages in the console?
  • p
    Just had to confirm real quick
  • p
    There should be 37 results, where as the lookup only yields 28 results
1...285286287...757Latest