syntect VS neovim

Zola (https://www.getzola.org/) can generate from markdown-ish files nice looking documentation websites (and also RSS feeds), it uses syntect (https://github.com/trishume/syntect) which supports sublime syntax highlight files. For github readme I don't have a solution besides using a png.

Syntax highlighting: https://github.com/trishume/syntect

I wonder if a plugin integrating syntect would be possible.

I love that idea! I think there might be a better way than just hardcoding all the comment types for all the languages, though. I'm using the syntect library which will parse the code based on syntax files, so I opened an issue there to see if they have anything that could help.

Very recently, I stumbled onto a library called syntect, which is a syntax highlighting library, and I got interested in the project because it promises to be really fast.

As a software engineer, choosing and understanding your text editor is important part of your work, as it impacts your productivity and workflow efficiency. It's like choosing the perfect tool for any trade - you need to know what tool to use and how to use it effectively if you want to excel. For me, I use Neovim as my editor and I have been using it for a little over a year now.

This got me thinking about my recent pivot, my switch to Neovim by way of LazyVim to write most of my code, and using tmux to keep terminal states alive after closing a session.

Neovim: Make sure you have Neovim installed on your system. You can check the official website for installation instructions: https://neovim.io/ Git: We'll be using Git to clone the LazyVim starter pack. If you don't have Git, you can download it from https://git-scm.com/downloads

There are several ways to install Neovim. This wiki provides several guidelines on how to install Neovim.

All these thoughts I've shared, I would have them on occasion - but ever since I switched to Linux and Neovim, my curiosity has been through the roof. Switching over to Neovim and Linux was a not so fun weekend of configuration and spending half a day getting my work's local dev environment running on my new OS (which no one has tested development on). But I now have a deeper understanding of the tools I use, and have a text editor configured to be the most optimal for the way I want to use it.