Sometimes I like to use nvim for PKM stuff (sometimes in parallel with Logseq because I think that the vim plugin does what it can, but there’s a lot of features that I just do quicker on nvim. So, I created this alias to open in the terminal the latest .md file in my PKM folder (both pages and journals) pkmu.
I also have another ones like pkm, that opens in nvim today’s journal. and pkmj and pkmp open the directory for PKM journals and pages, if I want to do anything there (maybe a fzf, rename, bat, rm…).
alias pkm='nvim "$HOME/Documentos/PKM/logseq/journals/$(date +%Y_%m_%d).md"'
alias pkmj='cd $HOME/Documentos/PKM/logseq/journals/'
alias pkmp='cd $HOME/Documentos/PKM/logseq/pages/'
alias pkmu='nvim "$(find $HOME/Documentos/PKM/logseq/ -type f -name '\''*.md'\'' -printf '\''%T@ %p\n'\'' | sort -n | tail -1 | cut -d'\'' '\'' -f2-)"'
I just wanted to share this with you, just in case it helps, or gives you any cool idea.
Interesting! I need to dive back into pkm stuff. I got really interested a while back with Obsidian. My frustration is that most of it is just simple markdown with links and even most tools can link to other files with markdown urls, so why can’t I easily make a static site from this? I dove deep on this with GitHub Pages and got it all working. Now I should look back into what settings in Obsidian make it make the most friendly output for Jekyll.
I’m glad you find it interesting! BTW, what do you mean by static site? A defined directory for all your md files?
@Moshpirit Humm, I hadn’t thought of creating aliases for the #Logseq structure and using #emacs (the editor I use on a daily basis) to edit the files.
This gave me the idea of writing an emacs plugin
