This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Consider having your front door locked for example. You could consider your home secure if your door is locked and insecure if it’s open but that doesn’t say what you’re secure against. It’s missing context. It might prevent opportunistic thefts but a more determined attacker could instead break a window, pick the lock of the door or simply break down the door itself. [Maybe you live in a neighborhood](#) with lots of thefts and you might want an alarm system, a dog or iron bars over your windows.
At the same time it might not be practical to go all out and get the best protection possible. You might not want to give up your life and move to a bunker where your friends can’t visit and a private security force may be slightly too expensive.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@@ -212,117 +212,117 @@ While doing the rewrite I went through my existing plugins to see if they were s
I won't create a list of my favorite plugins, as it would be boring to see yet another list with [LSP][lspconfig], [treesitter][nvim-treesitter] and [cmp][nvim-cmp], I'll instead highlight some good plugins that were new to me:
-[lazy.nvim][]: A modern plugin manager
##[lazy.nvim][]: A modern plugin manager
I've been using [vim-plug][] as my plugin manager since forever. It's been working well, but I figured I should try one of these newer managers to see if I was missing something. And boy, did I. [lazy.nvim][] has some really nice features that I now can't live without:
I've been using [vim-plug][] as my plugin manager since forever. It's been working well, but I figured I should try one of these newer managers to see if I was missing something. And boy, did I. [lazy.nvim][] has some really nice features that I now can't live without:
- Split plugin specifications in separate files as I wrote about [earlier in the post](#structured-configuration).
- Specify plugin dependencies.
- Pin plugin versions.
- Track plugin versions in `lazy-lock.json`, so you can identify what plugin version breaks your setup so you can pin it to a known good version.
- Lazy loading. It's nice to have for those rarely used but heavy plugins.
- Split plugin specifications in separate files as I wrote about [earlier in the post](#structured-configuration).
- Specify plugin dependencies.
- Pin plugin versions.
- Track plugin versions in `lazy-lock.json`, so you can identify what plugin version breaks your setup so you can pin it to a known good version.
- Lazy loading. It's nice to have for those rarely used but heavy plugins.
-[melange-nvim][]: An amazing colorscheme
##[melange-nvim][]: An amazing colorscheme
I've been a gruvbox user since I started using Vim almost 15 years ago. I've tried tons of different colorschemes but nothing has ever come close to gruvbox for me. Most of the popular colorschemes are just too blue, or have too little (or too much) contrast or I just don't like them for some random reason.
I've been a gruvbox user since I started using Vim almost 15 years ago. I've tried tons of different colorschemes but nothing has ever come close to gruvbox for me. Most of the popular colorschemes are just too blue, or have too little (or too much) contrast or I just don't like them for some random reason.
I had almost resigned to becoming a gruvbox-lifer, unable to ever change colorscheme.
I had almost resigned to becoming a gruvbox-lifer, unable to ever change colorscheme.
And then, [melange-nvim][] appeared. And it's glorious!
Now after many long years, I've finally switched to a new colorscheme, and I'm content.
And then, [melange-nvim][] appeared. And it's glorious!
Now after many long years, I've finally switched to a new colorscheme, and I'm content.
(No, switching from the original [gruvbox][] to [gruvbox.nvim][] to [gruvbox-material][] and back again doesn't count.)
(No, switching from the original [gruvbox][] to [gruvbox.nvim][] to [gruvbox-material][] and back again doesn't count.)
Also a shout-out to [kanagawa][] (dragon, the dark variant without blue background) which is the only colorscheme I've found that I didn't eject in horror after 5 minutes, except for gruvbox and melange.
Also a shout-out to [kanagawa][] (dragon, the dark variant without blue background) which is the only colorscheme I've found that I didn't eject in horror after 5 minutes, except for gruvbox and melange.
![Sorry [kanagawa][]. It's not you, it's me.](/images/rewrite_neovim_lua/kanagawa.png)
![Sorry [kanagawa][]. It's not you, it's me.](/images/rewrite_neovim_lua/kanagawa.png)
-[vim-cool][]: Turn off search highlight
##[vim-cool][]: Turn off search highlight
Forget `<C-l>`, this plugin will turn off search highlight when you move your cursor away from it.
Simple, but raises the quality of life a *lot*.
Forget `<C-l>`, this plugin will turn off search highlight when you move your cursor away from it.
Simple, but raises the quality of life a *lot*.
-[conform][]: Format on save
##[conform][]: Format on save
I've used [neoformat][] before, but had some issues where I saved then quickly stared modifying something, but then formating kicked in and removed my changes.
I've used [neoformat][] before, but had some issues where I saved then quickly stared modifying something, but then formating kicked in and removed my changes.
With [conform][] I haven't had these issues, and configuration was quick and easy and LSP fallback is super sweet. Excellent plugin.
With [conform][] I haven't had these issues, and configuration was quick and easy and LSP fallback is super sweet. Excellent plugin.
-[nvim-treesitter-textobjects][]
##[nvim-treesitter-textobjects][]
A common misconception about treesitter is that it only adds semantics to syntax highlighting:
A common misconception about treesitter is that it only adds semantics to syntax highlighting:
I think that's very nice, but treesitter is more than that. And a great example of that is [nvim-treesitter-textobjects][] where you can operate on treesitter nodes. I have for example:
I think that's very nice, but treesitter is more than that. And a great example of that is [nvim-treesitter-textobjects][] where you can operate on treesitter nodes. I have for example:
-`]f` jump to next function.
-`]c` jump to next class.
-`]g` jump to next function or class.
-`<leader>s` swap next parameter.
-`if` textobject for inner function. So `cif` would delete the function body and enter insert mode.
-`ax` textobject for outer comment, to easily delete/change comments.
-`]f` jump to next function.
-`]c` jump to next class.
-`]g` jump to next function or class.
-`<leader>s` swap next parameter.
-`if` textobject for inner function. So `cif` would delete the function body and enter insert mode.
-`ax` textobject for outer comment, to easily delete/change comments.
The beauty is that these work on treesitter nodes, so they work equally well across languages for functions like `fn myfun() { }`rust, `function myfun() ... end`lua or a `def myfun() do ... end`elixir. (Given that the treesitter implementation supports these options. Markdown doesn't have the concept of a function for instance.)
The beauty is that these work on treesitter nodes, so they work equally well across languages for functions like `fn myfun() { }`rust, `function myfun() ... end`lua or a `def myfun() do ... end`elixir. (Given that the treesitter implementation supports these options. Markdown doesn't have the concept of a function for instance.)
-[neogit][]: Git management
##[neogit][]: Git management
[magit][] is widely regarded as the best Git client/integration there is.
When I used Emacs for work (oh yes, the horrors) I did use [magit][] and yes it was great (although too slow on Windows).
[magit][] is widely regarded as the best Git client/integration there is.
When I used Emacs for work (oh yes, the horrors) I did use [magit][] and yes it was great (although too slow on Windows).
I don't think I need to say more than that [Neogit][] is [magit][], but for Neovim, and it is also great.
(It doesn't have feature parity with [magit][] yet, but it's good enough to have replaced [fugitive][] for me.)
I don't think I need to say more than that [Neogit][] is [magit][], but for Neovim, and it is also great.
(It doesn't have feature parity with [magit][] yet, but it's good enough to have replaced [fugitive][] for me.)
I'm going to be honest here: I've always thought that a dashboard was unnecessary fluff and people who used them were just pimping Neovim for the sake of pimping.
I'm going to be honest here: I've always thought that a dashboard was unnecessary fluff and people who used them were just pimping Neovim for the sake of pimping.
And now, I also use a dashboard.
And now, I also use a dashboard.
While it's something I could absolutely live without, by now I'd rather have it than not.
While it's something I could absolutely live without, by now I'd rather have it than not.
Okay, saving a keypress by using `f` instead `<leader>f` isn't a big deal.
And yeah, showing [lazy.nvim][] stats is probably unnecessary.
Okay, saving a keypress by using `f` instead `<leader>f` isn't a big deal.
And yeah, showing [lazy.nvim][] stats is probably unnecessary.
But having a list of keymaps that I should internalize is actually really nice.
It helps remind me of these cool new keymaps I've added, so they don't get forgotten for years until my next config rewrite.
But having a list of keymaps that I should internalize is actually really nice.
It helps remind me of these cool new keymaps I've added, so they don't get forgotten for years until my next config rewrite.
Yes, the list of keymaps is currently just hardcoded in the dashboard config.
But I would like to implement keymap tracking and use it for spaced repetition.
Maybe even have a floating window on startup that you need to clear every day, similar to "flashcards".
This is a nice idea for a plugin that I may or may not write in the future...
Yes, the list of keymaps is currently just hardcoded in the dashboard config.
But I would like to implement keymap tracking and use it for spaced repetition.
Maybe even have a floating window on startup that you need to clear every day, similar to "flashcards".
This is a nice idea for a plugin that I may or may not write in the future...
-[flash.nvim][]: Navigational plugin
##[flash.nvim][]: Navigational plugin
Once upon a time there was [vim-sneak][] that added the motion `s` to jump to any location by specifying two characters.
It was great, and it spawned a slew of other similar plugins that expanded on the idea.
(I'm not sure this is completely historically accurate, but it felt like a good narrative.)
Once upon a time there was [vim-sneak][] that added the motion `s` to jump to any location by specifying two characters.
It was great, and it spawned a slew of other similar plugins that expanded on the idea.
(I'm not sure this is completely historically accurate, but it felt like a good narrative.)
The plugin I've landed on is [flash.nvim][].
What I really like about it is the idea of typing as many characters as possible.
Even with sneak I didn't always arrive where I wanted, so having the option of typing out more things felt good for me.
The plugin I've landed on is [flash.nvim][].
What I really like about it is the idea of typing as many characters as possible.
Even with sneak I didn't always arrive where I wanted, so having the option of typing out more things felt good for me.
Extra functionality such as doing a "remote yank" (search, yank something, then cursor goes back to where it was) and enhancing `f`/`F`/`t`/`T`/`/` is just gravy.
Extra functionality such as doing a "remote yank" (search, yank something, then cursor goes back to where it was) and enhancing `f`/`F`/`t`/`T`/`/` is just gravy.
-[nvim-colorizer][]: Colorizer plugin
##[nvim-colorizer][]: Colorizer plugin
![What are these colors again? It's the palette of [melange-nvim][] of course!](/images/rewrite_neovim_lua/colorizer.png)
![What are these colors again? It's the palette of [melange-nvim][] of course!](/images/rewrite_neovim_lua/colorizer.png)
After [vim-hexokinase][] got archived I had a minor panic.
It was a neat little plugin that highlighted colors inline, but without altering the highlight of the colors themselves, which is what all the other colorizer plugins seemed to do.
After [vim-hexokinase][] got archived I had a minor panic.
It was a neat little plugin that highlighted colors inline, but without altering the highlight of the colors themselves, which is what all the other colorizer plugins seemed to do.
Luckily I found [nvim-colorizer][] that does the same, and without having to build an external binary like hexokinase that always managed to break for some weird reason.
Luckily I found [nvim-colorizer][] that does the same, and without having to build an external binary like hexokinase that always managed to break for some weird reason.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@@ -35,7 +35,7 @@ The simpest [Pygments][] lexer might look like this:
[Pygments]: https://pygments.org/
```python3
```python
from pygments.lexer import*
from pygments.token import*
import re
Expand DownExpand Up
@@ -74,7 +74,7 @@ Regular text â—Š; Trailing comment
Which should be pretty straightforward. We just need to add a single clause to the root state that matches everything from `â—Š;` to the end of the line:
To make this work out of the box we also need to add the regex flags:
```python3
```python
flags = re.IGNORECASE| re.MULTILINE
```
The other thing I want to do is introduce another state. It's not strictly needed in this case, but as `â—Š` can be followed by different cases it makes the lexer easier to follow. Like this:
```python3
```python
'root': [
(r'â—Š;.*?$', Comment),
('â—Š', Name.Variable.Magic, 'post-magic'),
Expand DownExpand Up
@@ -176,13 +177,13 @@ I thought this was going to be really hard, but Pygments supports this in variou
First the import:
```python3
```python
from pygments.lexers.lisp import RacketLexer
```
And the case is simply:
```python3
```python
'post-magic': [
...
(r'(\()(.+)(\))',
Expand All
@@ -192,11 +193,11 @@ And the case is simply:
'#pop')
```
The interesting line is`using(RacketLexer, state='unquoted-datum')`python3 which delegates the lexer to `RacketLexer`, starting in state `unquoted-datum`. How did I figure out which initial state to start in? I tried to [read the code][racket-lexer] and make an educated guess...
The interesting line is`using(RacketLexer, state='unquoted-datum')`python which delegates the lexer to `RacketLexer`, starting in state `unquoted-datum`. How did I figure out which initial state to start in? I tried to [read the code][racket-lexer] and make an educated guess...
But we also need to ensure we use the regex flag of allowing the dot to match newlines as well, otherwise we won't match multiline racket expressions:
```python3
```python
flags = re.IGNORECASE| re.DOTALL| re.MULTILINE
```
Expand All
@@ -213,39 +214,39 @@ First let's support the simpler `â—Švar{text args}` case.
We could do more here, but we're preparing for the future where we can also match against an optional `[...]` after the variable, so we'll delegate to another state. `('#pop', 'curly-start')`python3 essentially means we'll replace the current state `post-magic` with the new `curly-start` state.
We could do more here, but we're preparing for the future where we can also match against an optional `[...]` after the variable, so we'll delegate to another state. `('#pop', 'curly-start')`python essentially means we'll replace the current state `post-magic` with the new `curly-start` state.
Here again we could've done more, but we want to be able to do recursive matching inside `{ ... }` as well. This is what the `curly-end` state does:
```python3
```python
'curly-end': [
(r'\}', Name.Variable.Magic, '#pop'),
include('root'),
],
```
`include('root')`python3 does what you might expect it to do: it copies all cases from our `root` state into the `curly-end` sate. This to avoid code duplication.
`include('root')`python does what you might expect it to do: it copies all cases from our `root` state into the `curly-end` sate. This to avoid code duplication.
And this can indeed highlight `â—Švar{ ... }` recursively!
To support an optional `[ ... ]` we can add another state before `curly-end` that either matches against square brackets or curly brackets:
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters