@dennisfaucher@infosec.exchangeSo, since I found a bug in #logseq where pasting formatted notes from MS Teams causes logseq to use incorrect bold markdown syntax ([space]** at the end of a phrase instead of just **), I wrote this sed script to fix the logseq markdown files after I paste content in:
$ cat fix_logseg_bold_journals.sh
#!/bin/bash
cd /Users/faucherd/Documents//Logseq/journals
sed -i '…
@groberschnitzer@graz.socialHab ein paar richtig coole #Logseq Templates von @… gefunden:
https://github.com/wieerwill/logseq_t…
@dennisfaucher@infosec.exchangeI finally found a way to print #logseq queries. There is no native way and every plugin also just prints the query and not the query output.
https://github.com/cldwalker/logseq-query
Th…
@ellie@ellieayla.netLogseq (the Electron app on MacOS) uses the dugite library to interact with git, which ships its own copy of git, but doesn't include a git-credential-osxkeychain. And my normal auth to GitHub uses credential.helper=osxkeychain. Sigh.
export PATH GIT_EXEC_PATH ...
@iam_jfnklstrm@social.linux.pizzaQuestion! I want to use Logseq for notes - between mashines. On one I cannot install software. So my obstacles are the following:
1. Sync files between them (tried github bur it doesn't work out for me).
2. Accessing the files from the browser ( it sufficient to be able to read and write markup files).
I have a home server if necessary
@iam_jfnklstrm@social.linux.pizzaNext project - Logseq in docker to have self hosted notes in a system close to Obsidian.md
