Angad BehlIf I were to use #Emacs or #Vim / #Neovim for #notetaking, is there any way to access #notes from the #browser? Perhaps through a #pwa?
Is there anything like #cloudmacs for (neo)vim?
Dusty Pomerleau@slashtechno If your notes are in a git repo, why not just push them to Github? You then have desktop and mobile access (browser or app). If the notes are Markdown, and you care more about having access than specifically using the browser for access, you might like Obsidian better - I use Obsidian's iCloud sync, but there are other options. I often edit my Obsidian vault in Neovim, rather than using Obsidian's client.
@dpom Whilst it's possible to edit files in Git through Github, I find the process rather cumbersome and don't think that would be a great solution.
I love how Logseq works. It's similar to Obsidian in a sense, but open source. Either way, isn't using something like Neovim for editing files created by a outliner files challenging? I know at least for Logseq, even though everything is stored in Markdown, Logseq adds other data to the Markdown file which is then rendered.
@slashtechno Obsidian mostly just uses plain Markdown, and tolerates editing in Neovim without any issues. In fact, you can edit the file in Neovim while it is open in Obsidian, and it will update without a reload. The only thing you miss with Neovim are smart features that Obsidian offers, like inserting templates, or automatically opening today’s daily note, etc.
@dpom Ah, okay. I just want to have my editor understand outliner-specific syntax and directory structure.
Currently watching the following video on remotely accessing Obsidian/Logseq:
https://www.youtube.com/watch?v=CaqhIoj8MWk
Currently watching the following video on remotely accessing Obsidian/Logseq:
https://www.youtube.com/watch?v=CaqhIoj8MWk
івась тарасикGive Up GitHub: The Time Has Come!
Those who forget history often inadvertently repeat it. Some of us recall that twenty-one years ago, the most popular code hosting site, a fully Free and Open Source (FOSS) site called SourceForge, proprietarized all their code — never to make it FOSS again. Major FOSS projects slowly left SourceForge since it was now, itself, a proprietary system, and antithetical to FOSS. FOSS communities learned that it was a mistake to allow a for-profit, proprietary software company to become the dominant FOSS collaborative development site. SourceForge slowly collapsed after the DotCom crash, and today, SourceForge still refuses to solve these problems0. We learned a valuable lesson that was a bit too easy to forget — especially when corporate involvement manipulates FOSS communities to its own ends. We now must learn the SourceForge lesson again with Microsoft's GitHub.
El Presidente Poole@slashtechno Closest thing you'll get with Vim is SSHing into a remote server. Trying to find feature parity going from Emacs to Vim is a uphill battle.
@elpresidente Fair point, however, #code-server with Vim keybindings could be viable.