VimWiki is my preferred notetaking solution because it's intentionally minimal.

When I want to take notes, I want to take notes, not see a mind map or extra visualizations or photos to distract me. I'm old school! (Or just old.)

In today's video, I'll show you how to install VimWiki for yourself, as well as configure it to use Markdown (my preferred text formatting), and update the file path for VimWiki files so that it's easy to sync with third party solutions like Nextcloud Notes.

Significant links mentioned in the video:
👩🏻‍💻 My blog post which covers this topic: https://vkc.sh/vimwiki-101
👷 VimWiki's GitHub page: https://github.com/vimwiki/vimwiki
☁️ Nextcloud, my preferred self-hosted file sync solution: https://nextcloud.com
📓 Nextcloud Notes on GitHub: https://github.com/nextcloud/notes-android
🎈 Eleventy, my preferred SSG: https://www.11ty.dev/
🦖 Wikipedia's page on how modes work as an interface concept (Vim being an example of a "modal editor"): https://en.wikipedia.org/wiki/Mode_(user_interface)

This video has no sponsors except for my channel's Patrons and Ko-Fi members.
🅿️ Patreon: https://patreon.com/VeronicaExplains
☕ Ko-Fi: https://ko-fi.com/VeronicaExplains

Chapters:
0:00 I say "greetings" and tell you about VimWiki
1:33 Getting and installing VimWiki
3:46 Using VimWiki
6:51 Customizing VimWiki: switching it to Markdown
8:28 Changing the VimWiki directory (to sync with Nextcloud)
10:10 Navigating around in VimWiki
12:12 Conclusion: I think VimWiki is neat

#linux #vim #homelab

❤️ With all the installations on #GNU/#Linux (servers, vms, desktop, ... ), #BSD and #Unix systems, #MacOS, #Microsoft #Windows and WLS) I feel comfortable to claim there or way more than 1 billion installations of Vi*; often without people knowing about it.❤️

❤️ Thank you Bram Moolenaar, Christian Brabandt, the whole #Vim community, and all the people from projects like #NeoVIM, #Nvi, #Busybox #Vi, who develop and maintain their #vim flavour. ❤️

https://k7r.eu/thank-you-for-the-editor-of-the-beast/ ❤️ #ilovefs ❤️

Problem with that is (besides occasional bugfixes), most people including myself would see #curl to be functionally complete and anything "nice to have" would be considered not worth the balooning in #complexity and #size.

• I mean, does curl need to be able to do #BitTorrent (magnet:), #IPFS (ipfs://) or god forbid #blockchain (i.e. #EVM) support?
• Do you really want to integrate @torproject / #Tor support natively into curl when using #HTTP (localhost:8118) and #SOCKS5 (localhost:9050) #proxy allows for the same and doesn't necessitate having to handle and ingest Tor arguments as well??

In fact if #toybox didn't have a #wget implementation that I could use for OS/1337 I would've merely chosen tiny-curl -o as a global alias or if #tinycurl wasn't an option, curl -o instead.

• Maybe someone who wants to have said functionality like tor support built-in will go and IDK make i.e. #[url=https://infosec.space/tags/neocurl]neocurl[/url] or sth. along those lines or build something like #[url=https://infosec.space/tags/ethcurl]ethcurl[/url] or #[url=https://infosec.space/tags/tor]tor[/url]curlor #[url=https://infosec.space/tags/ipfs]ipfs[/url]curl or whatever...

That being said I am glad curl isn't solely maintained by you but has other contributors (give them a shoutout!) but I also am glad you maintain that vital software that most "#TechIlliterate #Normies" most likely never heard of but propably use on a daily basis as part of all the #tech they use to #consume media with...

• I consider curl to be "the #vim of downloaders" (tho that's kinda insulting and limiting since curl is more than just a downloader and more intuitive than vim) with wget being "the #vi of downloaders" (tho wget is even simpler to use than vi)...

Either way, curl is awesome...

#OS1337 #Enshittification #Bloat #Bloatware

Set aliases globally for all users

I have certain paths, which are too long to type, so I need to wrap all those in one script as alias and source that script to my existing package code. These should set alias permanently over that

^{Stack Overflow}

No, that is not how you exit Vim.

#vim #unix #macos #linux #thinkpad

It was a huge honour for me today with Raphael to posthumously hand over the European #SFSAward 2024 to #vim developer Bram Moolenaar for his invaluable contributions to the #FreeSoftware community.

If you are a #vim user, have been an #vim user, or admire Bram's work, please boost this message.

https://fsfe.org/news/2024/news-20241108-01.html