The plugin that brings the “starter” / “welcome” screen when nvim is called without a file is mini.starter, a lua module of the mini plugin. My primary use case for neovim is closer to a feature complete text editor rather than a full fledged IDE, although there definitely is some overlap in my setup.

My set of plugins are roughly as follows

• vim-plug, I will likely replace this one with packer at some point
• goyo.vim and limelight.vim for distraction free viewing and editing
• nnn.nvim to integrate the nnn file manager into neovim
• mini.nvim according to the Github, “Library of 35+ independent Lua modules improving overall Neovim (version 0.7 and higher) experience with minimal effort. They all share same configuration approaches and general design principles.”
  • mini.surround feature rich surround actions
  • mini.statusline a very simple no-frills statusline
  • mini.starter aformentioned start screen
  • mini.pairs inserts the paired character, e.g typing ( will automatically place ) behind the cursors
  • mini.move move selections
  • mini.map has a little map of the file similar to VScode among many other IDEs & text editors
• barbar.nvim Tabbar plugin
• a whole bunch of LSP / autocomplete engines / snippets / git commit messages & signs
• nvim-treesitter for syntax highlighting

And the remaining things in my init.lua file are just keybindings, setting up the plugins, and disabling the swapfile etc. when editing my password secrets in gopass among other ‘secret’ files

It definitely is rather reminiscent of older Windows versions with the seperate application launchers, fully expanded task bar entries that show the name of an app that are ungrouped (until necessary). And the widgets are very reminiscent of Rainmeter.

But I also bring some things from macOS that I enjoyed such as the global menu on the top (sadly Firefox flatpak does not support), virtual desktops with the pager widget on the bottom, and I use Krunner a lot (plasma’s equivalent to macOS “Spotlight”)

I hope your switch to Linux goes well if / when you switch!

I understand why they wouldn’t want to suddenly change the branding of existing projects though.

I’m not sure if I agree, I feel like the long term damage of keeping the names is greater than changing them now to Fedora Plasma Atomic (Formerly Kinoite) / Fedora Atomic Workstation (Formerly Silverblue). Leaving them as is, is just going to create more confusion in the future to new users who won’t immediately understand why the naming convention is different for the other spins and will create more confusion for documentation / support threads online.

I feel that I am 50:50 on it, immutable at least conveyed more information about what it is while Atomic feels a lot more “buzz-word-y” and does not convey as well what it means. Regardless, I’d say the bigger issue is keeping the old Silverblue & Kinoite names, they really should change them even if it means having a ~2 year period of having “Formerly Silverblue / Kinoite”.

Thank you for the very thorough reply! For god knows what reason I get this error: error: app/org.mozilla.firefox/x86_64/stable not installed when running the xdg-open firefox-reader command, yet manually running flatpak run --user org.mozilla.firefox about:reader?url=https://example.com works just fine. I’ll have to troubleshoot it when I have a bit more time ;p

Thanks again for your very thorough write up and the linked articles. Have a good day :)

Update: It seems like on my system, the --user flag was the issue, removing it made the script function. I am using Fedora Kinoite (Immutable version of KDE Plasma), so perhaps it is just a difference in how flatpak is configured between distros? I’ll have to read into it more later.

I’ll keep my answer focused on KDE Connect as I no longer use a TWM. You can most definitely use KDE Connect in non-Plasma environments. For non-Plasma (and non-Gnome ^* ) environments you can just install the kdeconnectd package. Then, to start the KDE Connect daemon manually, execute /usr/lib/kdeconnectd. You can schedule this to autostart as a systemd unit, or in the config for your TWM (I know in sway/i3 you could start it, I’m assuming it is similar for many other options)

If you use a firewall, you need to open UDP and TCP ports 1714 through 1764. If you use firewalld specifically, there’s an option to enable KDE Connect rather than manually specifying it. This also let’s you have it only work on private networks and not public if you so chose.

See Arch wiki for more details

*For gnome I would recommend using gs-connect even if you have a tiling extension

£ KDE-Connect: does that work on TWMs? Is there a good implementation? Can I use GSConnect elsewhere too?

I’d much rather use a separate Firefox (now Mozilla I think) account for my professional work. I also would prefer having separate extensions, notably Zotero connector is kind of useless for my personal browsing

Most of the documents I produce are converted to PDF or printed, so I use Nimbus Roman or Nimbus Sans (I believe). I do use Open Dyslexic font

For UI I really enjoy Inter, although Ubuntu, Roboto and IBM Plex Sans are also nice

For terminal I use Hack, although Source Code Pro is nice