WEBVTT

00:00:00.000 --> 00:00:02.940
I remember you being quite persistent, but that's

00:00:02.940 --> 00:00:09.060
okay. I got what I wanted. Well, yes. I think

00:00:09.060 --> 00:00:13.259
I bribed you a little bit. So, Arch or Gen 2?

00:00:13.380 --> 00:00:16.660
Or Debian? I don't like group box. I think it's

00:00:16.660 --> 00:00:19.980
a thing for old people. You take that back. You

00:00:19.980 --> 00:00:24.739
take that back. Don't want to brag, but I will,

00:00:24.820 --> 00:00:30.100
of course. I've also created the default color

00:00:30.100 --> 00:00:35.320
scheme. For Neovim? For Neovim, yes. It was a

00:00:35.320 --> 00:00:38.479
lot of back and forth between me and Justin.

00:00:39.380 --> 00:00:42.939
Justin M. Keys, which we interviewed. He also

00:00:42.939 --> 00:00:47.259
likes boring colors, it seems, right? It was

00:00:47.259 --> 00:00:49.700
basically, Justin said, it should be this one.

00:00:50.219 --> 00:00:53.320
I said, okay, boss. Why did you move from Vim

00:00:53.320 --> 00:00:57.820
to NeoVim? Because it was cool. What you do is

00:00:57.820 --> 00:01:02.000
copy these three commands. Why did you say like,

00:01:02.020 --> 00:01:03.960
okay, no, you know what? I don't want witch key.

00:01:04.079 --> 00:01:06.159
I don't want anything to do with it. I don't

00:01:06.159 --> 00:01:09.000
like full key. So I'm going to create mini .clues.

00:01:09.159 --> 00:01:13.459
Don't put those words into my mouth. I see you

00:01:13.459 --> 00:01:17.760
use ghosty. Is that fear on missing out as well,

00:01:17.799 --> 00:01:20.219
like NeoVim? If you're listening to this as a

00:01:20.219 --> 00:01:22.359
podcast, remember that it was originally recorded

00:01:22.359 --> 00:01:24.439
as a video. If you're not following along, you

00:01:24.439 --> 00:01:26.219
can go to my YouTube channel. My username is

00:01:26.219 --> 00:01:28.219
Linkarzu. And if you want to support me to keep

00:01:28.219 --> 00:01:30.500
this podcast going, you can donate in Ko -fi.

00:01:30.579 --> 00:01:31.939
I'm going to leave a link in the description.

00:01:32.260 --> 00:01:34.120
All right, so let's get started with this chapter

00:01:34.120 --> 00:01:38.780
then. How do we pronounce your name? That's maybe

00:01:38.780 --> 00:01:42.980
a little bit difficult topic, but I think what's

00:01:42.980 --> 00:01:47.359
the most, the best compromise here might be...

00:01:47.950 --> 00:01:53.290
Yevgeny. Maybe Yevgeny. So it's Yevgeny. Yevgeny.

00:01:53.510 --> 00:02:00.650
Yep. That sounds okay. That's the mix between

00:02:00.650 --> 00:02:08.090
the English, how I wrote it in English, and how

00:02:08.090 --> 00:02:13.250
my actually, the name sounds in Ukrainian. But

00:02:13.250 --> 00:02:16.150
in Ukrainian, it is much more difficult, I think.

00:02:16.740 --> 00:02:22.879
It is Yevheny. Yevheny. Yeah. Oh, maybe it will

00:02:22.879 --> 00:02:25.960
be easier for a Spanish speaker, actually. Yes,

00:02:25.979 --> 00:02:29.699
it is Yevheny. Yevheny. Something like that.

00:02:30.219 --> 00:02:34.639
Something like that, yes. But if you want, you

00:02:34.639 --> 00:02:38.939
can call me either way, actually. Okay. Now,

00:02:39.080 --> 00:02:43.379
why a Chesnovsky? Do most people call you a Chesnovsky?

00:02:43.819 --> 00:02:47.039
Because Chesnovsky... What is that? Is that your

00:02:47.039 --> 00:02:50.219
last name? Yes, it is my last name, almost to

00:02:50.219 --> 00:02:53.639
the letter, yes. Okay. How do people call you

00:02:53.639 --> 00:02:56.259
then? Do they call you Yevgeny or do they call

00:02:56.259 --> 00:03:00.439
you Ichasnovsky? People, like you mean real people

00:03:00.439 --> 00:03:03.340
outside of the internet? No, internet people,

00:03:03.539 --> 00:03:06.259
like in the Neovim community, let's say. In the

00:03:06.259 --> 00:03:09.500
Neovim community, it is Ichasnovsky, yes. Okay.

00:03:09.620 --> 00:03:13.060
E or E? Ichasnovsky. I'll be honest with you,

00:03:13.159 --> 00:03:18.979
only this one time. because this is the first

00:03:18.979 --> 00:03:24.900
time I'm actually speaking out loud. All the

00:03:24.900 --> 00:03:28.180
rest of my conversations are written in English,

00:03:28.379 --> 00:03:32.819
be it metrics, mostly GitHub, Reddit, Blue Sky

00:03:32.819 --> 00:03:37.120
lately. But that's it. So I pronounce it E because

00:03:37.120 --> 00:03:43.409
as in, I don't know, E -ink. as in this technology

00:03:43.409 --> 00:03:48.849
of i think the if e a b c d e it's not a it's

00:03:48.849 --> 00:03:53.909
e so uh i pronounce it each you pronounce it

00:03:53.909 --> 00:03:58.009
however you want because it is a username yeah

00:03:58.009 --> 00:04:01.469
people always ask me so how do you pronounce

00:04:01.469 --> 00:04:04.490
it and i'm like i don't know just pronounce it

00:04:04.490 --> 00:04:08.909
however you can yeah some something similar happens

00:04:08.909 --> 00:04:14.680
then i guess yeah Okay, so Ichasnovsky or Yevgeny,

00:04:14.780 --> 00:04:18.100
right? Yevgeny, yes. Yevgeny, okay. Ichasnovsky

00:04:18.100 --> 00:04:22.360
is going to be easier for me. So thanks for joining

00:04:22.360 --> 00:04:25.759
us today. Thank you. For people that don't know

00:04:25.759 --> 00:04:29.000
you, what is it that you do in the Neobim community?

00:04:29.220 --> 00:04:31.540
You want to share a little bit about you? Like

00:04:31.540 --> 00:04:35.120
you have some plugins. What do you work on? No,

00:04:35.160 --> 00:04:37.579
I don't have plugins. I have one plugin. One

00:04:37.579 --> 00:04:44.300
plugin? Only one. No, not so much, yes. I am

00:04:44.300 --> 00:04:49.860
a NeoVim local plugin developer. My main creation,

00:04:50.000 --> 00:04:55.199
I think, is mini .envim. It is a one single plugin,

00:04:55.339 --> 00:05:01.439
but it contains at the moment 44 different modules.

00:05:01.720 --> 00:05:07.959
And it is almost my entire NeoVim config at this

00:05:07.959 --> 00:05:11.910
point. There are some things that I would like

00:05:11.910 --> 00:05:15.870
also to replace in the future, but maybe not

00:05:15.870 --> 00:05:20.790
now. Okay, so this is pretty much then your own

00:05:20.790 --> 00:05:25.829
NeoVim config, but in modules, right? Well, it

00:05:25.829 --> 00:05:31.209
almost started that way, yes. Initially, it was

00:05:31.209 --> 00:05:39.850
the idea that I want to own most of my NeoVim

00:05:39.850 --> 00:05:45.129
config just for fun. No other reason. Actually,

00:05:45.269 --> 00:05:51.230
there was one reason. I wanted to have both NeoVim

00:05:51.230 --> 00:05:57.329
Lua setup and VimScript setup. And I also wanted,

00:05:57.389 --> 00:06:02.810
because I read that it was nice and cool, to

00:06:02.810 --> 00:06:10.379
have one file .vmrc or vimconfig because you

00:06:10.379 --> 00:06:13.000
will be able to just copy paste it on the remote

00:06:13.000 --> 00:06:17.560
machine and you'll use it as your regular setup.

00:06:17.819 --> 00:06:22.819
So it started that way and I wanted to create

00:06:22.819 --> 00:06:27.519
some basic functionality in a very simple, well,

00:06:27.660 --> 00:06:33.819
spoiler, minimal way. And I started with status

00:06:33.819 --> 00:06:38.079
line. Then it was probably tabline, the thing

00:06:38.079 --> 00:06:43.379
on the top. I don't know the order after that,

00:06:43.519 --> 00:06:50.379
but after about fifth such module, I started

00:06:50.379 --> 00:06:55.600
to also translate this Lua implementations into

00:06:55.600 --> 00:06:59.819
Vim script. So they were in sync. And I had almost

00:06:59.819 --> 00:07:05.810
the same setup in NeoVim and Vim. but Lua in

00:07:05.810 --> 00:07:09.410
NeoVim and VimScript in Vim. I could have done

00:07:09.410 --> 00:07:14.410
also only VimScript implementation, but I thought

00:07:14.410 --> 00:07:20.750
it was different times. It was NeoVim 0 .5, I

00:07:20.750 --> 00:07:24.750
don't know. When you started your NeoVim journey,

00:07:24.850 --> 00:07:28.189
at what version of NeoVim? Oh, I didn't start

00:07:28.189 --> 00:07:30.990
too long ago. I started, let's say, a year and

00:07:30.990 --> 00:07:34.639
a half ago, if I remember correctly. So 0 .10

00:07:34.639 --> 00:07:38.980
probably. I think. Yep. Okay. So you're a newbie

00:07:38.980 --> 00:07:42.399
basically. Yep. Yeah. I'm a newbie. Okay. No,

00:07:42.399 --> 00:07:47.920
I didn't say noob. I said newbie. It's not as

00:07:47.920 --> 00:07:56.480
insulting, right? So it was, how would I describe

00:07:56.480 --> 00:07:59.910
it? Wild, wild west. of Neovim configuration.

00:08:00.389 --> 00:08:04.970
Because some like to say it was a Lua apocalypse

00:08:04.970 --> 00:08:11.970
of Neovim. Because 0 .5 is the version when Neovim

00:08:11.970 --> 00:08:17.050
started to support Lua natively. So people could

00:08:17.050 --> 00:08:23.269
start writing plugins in Lua. And they did. All

00:08:23.269 --> 00:08:27.279
they did. There were so many Lua plugins that

00:08:27.279 --> 00:08:31.259
you actually probably use right now that started

00:08:31.259 --> 00:08:35.340
in that area. Which were they? Do you use LuaLine?

00:08:35.580 --> 00:08:40.139
I use LuaLine, yep, yep. It started basically

00:08:40.139 --> 00:08:45.940
pre -0 .5, I think. So when 0 .5 was nightly

00:08:45.940 --> 00:08:52.440
in development, it was very long. release window

00:08:52.440 --> 00:08:58.639
of 0 .5. I think it was about one and a half

00:08:58.639 --> 00:09:06.620
years between 0 .4 and 0 .5. And a lot of plugins

00:09:06.620 --> 00:09:11.200
started to actually exist back then. So LuaLine,

00:09:11.299 --> 00:09:16.840
which once, well, Minitot and Vim, it was pre

00:09:16.840 --> 00:09:23.159
-0 .5. GitScience .envim also started. Invent

00:09:23.159 --> 00:09:25.820
Blankline, it was one of the first... Sorry.

00:09:26.080 --> 00:09:30.220
It was one of the first plugins that I think

00:09:30.220 --> 00:09:34.679
were popular. So, yeah, something like this.

00:09:34.820 --> 00:09:40.860
So I've written... Let me see. I think it was

00:09:40.860 --> 00:09:48.100
13 modules in total. when I decided to make them

00:09:48.100 --> 00:09:53.399
public, organize them into a separate plugin.

00:09:54.639 --> 00:09:58.480
I think I came up with the name after the fifth

00:09:58.480 --> 00:10:01.620
module. I don't remember the order again. I can

00:10:01.620 --> 00:10:06.879
look in my .files, but maybe later. After about

00:10:06.879 --> 00:10:10.980
fifth module, I decided to actually... Maybe

00:10:10.980 --> 00:10:14.120
it sounds a bit cheesy. But I decided to give

00:10:14.120 --> 00:10:18.360
back to the community and make them public. And

00:10:18.360 --> 00:10:21.779
maybe somebody will use it later. And here we

00:10:21.779 --> 00:10:24.159
are four years later. We have been planning for

00:10:24.159 --> 00:10:26.360
this interview, like, I don't know, for the last

00:10:26.360 --> 00:10:30.320
six months, maybe? When did I reach out? Yes,

00:10:30.360 --> 00:10:34.559
I would like first to apologize to you specifically

00:10:34.559 --> 00:10:40.220
in public. because you did reach out not six

00:10:40.220 --> 00:10:46.059
months it was about around March this year I

00:10:46.059 --> 00:10:50.960
think because I did have to decline hopefully

00:10:50.960 --> 00:10:55.559
politely I don't quite remember no yes okay thank

00:10:55.559 --> 00:11:00.159
you because it was not quite the right time for

00:11:00.159 --> 00:11:03.500
me to do on the camera it just just not the right

00:11:03.500 --> 00:11:08.740
time And then I remember you being quite persistent,

00:11:08.940 --> 00:11:13.799
but that's okay. I got what I wanted. Well, yes,

00:11:13.919 --> 00:11:21.179
I think I bribed you a little bit because I asked

00:11:21.179 --> 00:11:26.220
a few people to do an interview with you. So

00:11:26.220 --> 00:11:29.519
I think it worked quite all right in the end.

00:11:30.240 --> 00:11:35.740
Yeah, it did. So in the summer, I genuinely wanted

00:11:35.740 --> 00:11:38.539
to do it in the beginning of the summer. But

00:11:38.539 --> 00:11:44.940
by that time, I knew that I wanted to do some

00:11:44.940 --> 00:11:49.940
work with media .envim that will become outdated

00:11:49.940 --> 00:11:52.700
very quickly if we do an interview back then.

00:11:53.320 --> 00:11:59.779
Because I basically wanted to move to the...

00:12:00.169 --> 00:12:05.129
a separate github organization so it would have

00:12:05.129 --> 00:12:09.690
been hsnovsky slash nvim on github but now it

00:12:09.690 --> 00:12:19.909
is nvim -mini .mp and the website also was a

00:12:19.909 --> 00:12:24.529
good idea i think it was the result of jump scare

00:12:24.529 --> 00:12:29.779
i'd say but that's okay Jumpscare, I don't know

00:12:29.779 --> 00:12:36.139
if you saw that, I was banned on Reddit for a

00:12:36.139 --> 00:12:42.220
month. Why? Genuinely, it was the false positive

00:12:42.220 --> 00:12:47.480
result of Reddit algorithm. Not moderators, not

00:12:47.480 --> 00:12:54.419
human error, just false positive result. It was

00:12:54.419 --> 00:13:00.909
10th of July. I decided to share my new color

00:13:00.909 --> 00:13:05.370
schemes. Four of them. Yes, that does matter.

00:13:05.570 --> 00:13:09.289
Four of them. Each one has dark and light variant,

00:13:09.450 --> 00:13:14.090
of course, as one does. I don't use light variants,

00:13:14.289 --> 00:13:21.029
I must admit. I also do not, but they should

00:13:21.029 --> 00:13:24.120
have it. Yeah, but I see that very based people

00:13:24.120 --> 00:13:26.899
use light themes when there's a lot of light

00:13:26.899 --> 00:13:33.240
around. But I don't do it. I'm maybe like a vampire

00:13:33.240 --> 00:13:35.259
or something, but I'm not in the light too much.

00:13:35.360 --> 00:13:37.639
But I guess that's when they are useful, when

00:13:37.639 --> 00:13:40.340
there's a lot of light. I also heard that it

00:13:40.340 --> 00:13:47.279
is useful when you're a bit older or have maybe

00:13:47.279 --> 00:13:52.450
a bit worse eyesight. Maybe. Could be. But I

00:13:52.450 --> 00:13:58.610
also think that dark color schemes are more usable,

00:13:58.809 --> 00:14:04.669
maybe. But there is basically a very deep color

00:14:04.669 --> 00:14:08.850
scheme, a color theory reasons behind it. We

00:14:08.850 --> 00:14:11.730
can talk about it. I don't know if you are interested

00:14:11.730 --> 00:14:17.190
in it, in this, but dark, there is a meaningful

00:14:17.190 --> 00:14:21.639
difference with how human eyes work. when it

00:14:21.639 --> 00:14:27.019
comes to light text on dark background. Okay.

00:14:27.779 --> 00:14:30.879
What do you want to share about that with us?

00:14:31.200 --> 00:14:34.700
So light text in a dark background, what we do

00:14:34.700 --> 00:14:39.659
in the terminal, right? Maybe in the terminal,

00:14:39.899 --> 00:14:44.220
maybe not. Yeah, there's people that use light

00:14:44.220 --> 00:14:46.220
themes on the terminal. I was thinking about

00:14:46.220 --> 00:14:48.799
NeoVim only, but yeah, there's people that do

00:14:48.799 --> 00:14:52.840
light themes as well there. uh basically basically

00:14:52.840 --> 00:14:57.100
what basically ah yes basically uh can you share

00:14:57.100 --> 00:14:59.879
my screen now yep let me switch to it hold on

00:14:59.879 --> 00:15:04.419
there i can see it so uh where do i start um

00:15:04.419 --> 00:15:10.299
human eyes uh have very complex mechanism of

00:15:10.299 --> 00:15:14.580
uh perceiving light and colors i i i don't know

00:15:14.580 --> 00:15:22.490
much here but But there are many studies that

00:15:22.490 --> 00:15:29.789
try to create a color space, basically a representation

00:15:29.789 --> 00:15:36.289
of colors that is close to what human eye can

00:15:36.289 --> 00:15:39.610
see. It's very difficult and confusing, but basically

00:15:39.610 --> 00:15:47.480
what there exists some such thing as How is it

00:15:47.480 --> 00:15:52.039
called? I don't remember. It was one and a half

00:15:52.039 --> 00:15:55.139
years ago. What's the blog post? Okay, so basically

00:15:55.139 --> 00:16:02.480
the color space that is uniformly... I don't

00:16:02.480 --> 00:16:07.299
remember. Color spaces that try to mimic how

00:16:07.299 --> 00:16:13.039
human eye perceives difference in colors. and

00:16:13.039 --> 00:16:18.080
try to translate that into numbers. So it's not...

00:16:18.080 --> 00:16:22.639
There is, of course, RGB. You know that. A color

00:16:22.639 --> 00:16:25.980
space. Red, green, and blue. If you convert that

00:16:25.980 --> 00:16:32.120
to numbers, like red from 0 to 255, the same

00:16:32.120 --> 00:16:36.759
for red and green, and you have two colors, and

00:16:36.759 --> 00:16:40.840
you compute the difference between them in any

00:16:40.840 --> 00:16:45.259
meaningful way, the difference the same number

00:16:45.259 --> 00:16:50.419
difference in for example light colors will be

00:16:50.419 --> 00:16:54.299
perceived by human eye differently than in dark

00:16:54.299 --> 00:16:58.279
colors okay this is basically one of the reasons

00:16:58.279 --> 00:17:04.859
why dark background or rather light foreground

00:17:04.859 --> 00:17:08.539
is useful it allows to have can you see it yes

00:17:08.539 --> 00:17:14.569
yep i see i'm clicking yeah In lighter colors,

00:17:14.990 --> 00:17:20.809
there is more possibility of creating more saturated

00:17:20.809 --> 00:17:28.210
color for some hues. A hue is basically a color

00:17:28.210 --> 00:17:31.269
without lightness that is of the red. So it's

00:17:31.269 --> 00:17:36.269
red, orange, green, that is hue. In, for example,

00:17:36.390 --> 00:17:45.700
blue and purple, You can see that darker colors

00:17:45.700 --> 00:17:53.420
can have more saturated values. Do you understand?

00:17:53.519 --> 00:17:58.359
Am I making it clear enough? Or maybe I'm all

00:17:58.359 --> 00:18:05.539
over the place right now. So I see light color

00:18:05.539 --> 00:18:10.329
here. There. where your cursor is that is light

00:18:10.329 --> 00:18:13.970
that's lying at the bottom darker right yes that

00:18:13.970 --> 00:18:17.450
is a gray color so that is low saturated colors

00:18:17.450 --> 00:18:21.150
and to the right is highly saturated colors so

00:18:21.150 --> 00:18:26.869
okay so it is uh more vivid colors oh yeah okay

00:18:26.869 --> 00:18:31.450
so and like this purple one does it go better

00:18:31.450 --> 00:18:35.029
with white or dark background based on what we

00:18:35.029 --> 00:18:39.339
see here It allows more saturated colors with

00:18:39.339 --> 00:18:44.400
darker shades. Okay. So, you see that it is below

00:18:44.400 --> 00:18:50.259
the center line. It is dark. And, for example,

00:18:50.259 --> 00:18:54.740
yellow, that's around yellowish hue. Yep. Around

00:18:54.740 --> 00:19:01.940
yellowish. Yep. It is very saturated on light

00:19:01.940 --> 00:19:08.779
colors. So, usually, having light foreground

00:19:08.779 --> 00:19:14.519
allows for more saturated colors, usually. Okay.

00:19:14.799 --> 00:19:23.000
So you can see, for example, orange is more saturated

00:19:23.000 --> 00:19:29.640
for lighter colors. Yellow, green, but it starts

00:19:29.640 --> 00:19:33.039
shrinking. Cyan also, that's a cyan color around.

00:19:33.240 --> 00:19:37.910
Light blue. and around the blue it's the and

00:19:37.910 --> 00:19:42.289
purple it starts to become more saturated towards

00:19:42.289 --> 00:19:46.329
uh darker colors okay i believe this might be

00:19:46.329 --> 00:19:52.190
the reason uh why purple purple backgrounds color

00:19:52.190 --> 00:19:55.769
schemes are so popular oh it is a theory it is

00:19:55.769 --> 00:19:59.589
a hypothesis i would say but it is what it is

00:19:59.589 --> 00:20:07.109
and it starts to go up again around red so if

00:20:07.109 --> 00:20:13.109
you have light text colors which is what happens

00:20:13.109 --> 00:20:16.890
with the dark color schemes because dark color

00:20:16.890 --> 00:20:20.329
schemes are color schemes that have dark background

00:20:20.329 --> 00:20:25.269
you should be able to have more saturated foreground

00:20:25.269 --> 00:20:31.900
colors and they will be more distinct when it

00:20:31.900 --> 00:20:36.140
comes to comparing each other. By the way, what

00:20:36.140 --> 00:20:38.960
I'm showing right now, it is the color space

00:20:38.960 --> 00:20:44.539
perceptually uniform. I remembered. Okay. Those

00:20:44.539 --> 00:20:47.259
color spaces are called perceptually uniform,

00:20:47.599 --> 00:20:51.660
which means that difference in... Do you see

00:20:51.660 --> 00:20:55.480
my pointer right now? I see it. So basically,

00:20:55.599 --> 00:21:01.200
this is a color. A color. Some color. It has

00:21:01.200 --> 00:21:08.819
a hue value 104, which is around yellow -greenish.

00:21:09.019 --> 00:21:15.359
It has a chroma 10 and lightness 89. If I, for

00:21:15.359 --> 00:21:20.640
example, compare it with this color, for example,

00:21:20.640 --> 00:21:24.390
something like this. I can subtract hue from

00:21:24.390 --> 00:21:28.230
previous one. I can subtract this chroma from

00:21:28.230 --> 00:21:31.130
previous one. I can subtract this lightness from

00:21:31.130 --> 00:21:35.609
previous one and take absolute values of them

00:21:35.609 --> 00:21:40.230
and sum it. This will be one way to compare these

00:21:40.230 --> 00:21:44.710
colors, to compute the difference. It will demonstrate

00:21:44.710 --> 00:21:53.119
the same difference in colors. no matter which

00:21:53.119 --> 00:21:58.539
two colors I compare. So it will be the same

00:21:58.539 --> 00:22:01.420
difference as four darker colors, for example.

00:22:01.599 --> 00:22:07.299
But it will have to be more difference in hue,

00:22:07.460 --> 00:22:11.539
for example, if we compare the same lightness.

00:22:11.720 --> 00:22:17.859
But anyway, that's color theory and it is very

00:22:17.859 --> 00:22:23.599
complex. And it has its roots in biology, which

00:22:23.599 --> 00:22:28.599
means it is not very precise science, but not

00:22:28.599 --> 00:22:31.759
because of biology itself as a science, but because

00:22:31.759 --> 00:22:36.460
it is a study of life, and life is not precise,

00:22:36.640 --> 00:22:43.660
unfortunately. It is a result of evolution that

00:22:43.660 --> 00:22:47.960
the human eye is just the way it is, and it has

00:22:47.960 --> 00:22:53.390
to be studied the way it is and uh not for any

00:22:53.390 --> 00:22:58.289
particular person but across all human human

00:22:58.289 --> 00:23:01.910
species basically and it's very very very difficult

00:23:01.910 --> 00:23:07.230
to do because the researchers basically have

00:23:07.230 --> 00:23:12.769
to invent own ways how to compare and scientifically

00:23:14.260 --> 00:23:19.339
verify their findings because they cannot just

00:23:19.339 --> 00:23:22.019
eyeball it because they have their eyes also.

00:23:24.539 --> 00:23:28.759
It's very complex. I guess that's why some people

00:23:28.759 --> 00:23:31.640
like some color schemes and some people don't

00:23:31.640 --> 00:23:33.619
like other color schemes, right? Everyone has

00:23:33.619 --> 00:23:37.680
different eyes. I don't like group box. I think

00:23:37.680 --> 00:23:40.859
it's a thing for old people. You take that back.

00:23:43.480 --> 00:23:46.460
The colors are too dull. I like bright colors.

00:23:46.720 --> 00:23:49.299
You don't like bright colors, right? You like

00:23:49.299 --> 00:23:56.099
more like... I like bright colors. Bright as

00:23:56.099 --> 00:24:00.220
in... I've seen your color scheme, yes. I slightly

00:24:00.220 --> 00:24:05.700
judged you a little bit when I saw it. Is that

00:24:05.700 --> 00:24:11.400
for weak eyes? It uses highly saturated colors,

00:24:11.539 --> 00:24:18.250
yes. Exactly, yep. I did use it in my very first

00:24:18.250 --> 00:24:21.309
Neolim color scheme, which is called Midi Scheme.

00:24:21.509 --> 00:24:25.349
But I guess as you age, you get older, you mature,

00:24:25.650 --> 00:24:28.869
and you move away from highly saturated colors,

00:24:29.109 --> 00:24:31.710
right? Because they tend to be a little bit hard

00:24:31.710 --> 00:24:35.690
on the sight, right? I'm not sure. Yeah, you

00:24:35.690 --> 00:24:39.329
can share it now, I think. Basically, this is

00:24:39.329 --> 00:24:44.549
what my first creation. color scheme was it is

00:24:44.549 --> 00:24:51.529
a variant of base 16 and which is of course there

00:24:51.529 --> 00:24:55.349
is mini dot base 16 module of mini and vim it

00:24:55.349 --> 00:24:59.829
is very highly saturated i i really really love

00:24:59.829 --> 00:25:07.130
the yellow on blue okay combination and you can

00:25:07.130 --> 00:25:12.470
see right now in practice i have dark blue background,

00:25:12.769 --> 00:25:16.990
which is very saturated because it is around

00:25:16.990 --> 00:25:21.349
that hue that allows very saturated dark blue.

00:25:21.789 --> 00:25:27.769
And I have very saturated light yellow because

00:25:27.769 --> 00:25:30.990
yellow is the color that allows very highly saturated

00:25:30.990 --> 00:25:35.589
white color. So this is very saturated color

00:25:35.589 --> 00:25:39.630
scheme. I don't know why I liked it, to be honest.

00:25:40.079 --> 00:25:44.160
I have my theory. I have my hypothesis. The hypothesis

00:25:44.160 --> 00:25:51.160
is that I created it on my monitor that was a

00:25:51.160 --> 00:25:54.920
bit far away. And maybe, just maybe, I'm not

00:25:54.920 --> 00:25:59.519
quite sure, it was maybe a little bit dusty with

00:25:59.519 --> 00:26:06.140
time. So it didn't have that much, that good...

00:26:06.589 --> 00:26:10.390
color representation, you know? So I needed to

00:26:10.390 --> 00:26:14.769
have more saturation in order to see the difference

00:26:14.769 --> 00:26:17.569
between colors. Maybe that wasn't the reason.

00:26:17.690 --> 00:26:25.029
After I switched to my laptop, which has a much

00:26:25.029 --> 00:26:31.490
better screen, I basically used this one, which

00:26:31.490 --> 00:26:37.210
is similar, but a little less saturated. color

00:26:37.210 --> 00:26:44.789
scheme. But after some time I decided it was

00:26:44.789 --> 00:26:50.829
time to go back to make my own color scheme basically

00:26:50.829 --> 00:26:56.230
because that was base 16. I copy pasted the theme

00:26:56.230 --> 00:27:01.430
base 16 color scheme for Vim but made it Lua

00:27:01.430 --> 00:27:06.220
and tailored it for NeoVim. But this one is mini

00:27:06.220 --> 00:27:10.079
.hues, which is my own color scheme, and which

00:27:10.079 --> 00:27:16.559
was used as an inspiration, basically, for default

00:27:16.559 --> 00:27:19.319
color scheme. Because I don't know if you know

00:27:19.319 --> 00:27:23.039
that. I don't want to brag, but I will, of course.

00:27:25.279 --> 00:27:29.619
I've also created the default color scheme. For

00:27:29.619 --> 00:27:34.700
NeoVim? For NeoVim, yes. This one. oh i didn't

00:27:34.700 --> 00:27:39.920
know okay yeah yeah it was my first big pr after

00:27:39.920 --> 00:27:43.319
uh it was a lot of back and forth between me

00:27:43.319 --> 00:27:48.319
and uh and justin justin m keys which were interviewed

00:27:48.319 --> 00:27:51.680
he also likes boring he also likes boring colors

00:27:51.680 --> 00:27:57.180
it seems right uh he likes its own colors i think

00:27:57.180 --> 00:28:02.539
the main constraint here was that it should be

00:28:03.469 --> 00:28:09.009
It should resemble Neovim. So Neovim logo colors,

00:28:09.230 --> 00:28:13.009
which is green and blue -ish. A lot of different

00:28:13.009 --> 00:28:17.329
blue hues, right? Blue, like... No, no, no. Well,

00:28:17.549 --> 00:28:24.130
the primary color, what we ended up deciding

00:28:24.130 --> 00:28:27.970
on, because it was literally a lot of back and

00:28:27.970 --> 00:28:33.160
forth. I don't know. Maybe... Around six months,

00:28:33.299 --> 00:28:43.180
something like that. It was in 2023, two years

00:28:43.180 --> 00:28:50.940
ago, I think. Yes. And my initial suggestion

00:28:50.940 --> 00:28:55.660
was very close to like that. But oh, this is

00:28:55.660 --> 00:28:59.759
actually my random hue color scheme to more colorful.

00:28:59.940 --> 00:29:03.940
It was more colorful. It had more colors for

00:29:03.940 --> 00:29:10.440
syntax groups, and it had not a great background.

00:29:10.720 --> 00:29:16.039
But it was a lot of negotiations. Well, I say

00:29:16.039 --> 00:29:19.180
negotiations. It was basically Justin said, it

00:29:19.180 --> 00:29:25.599
should be this one. I said, okay, boss. He said

00:29:25.599 --> 00:29:35.210
dictator then. No. No, he's not. He is, how do

00:29:35.210 --> 00:29:39.269
I put it? He has his own vision, that's for sure.

00:29:39.769 --> 00:29:45.650
But he is quite flexible in areas that I think

00:29:45.650 --> 00:29:52.549
that he knows other people might have more input

00:29:52.549 --> 00:29:59.269
that he can provide, I think. so with the color

00:29:59.269 --> 00:30:08.250
scheme i did a lot of study beforehand as i think

00:30:08.250 --> 00:30:15.130
you couldn't see it prior in my gibberish explanations

00:30:15.130 --> 00:30:19.190
about color spaces but when i'm not on camera

00:30:19.190 --> 00:30:22.769
and i have time to actually write stuff i think

00:30:22.769 --> 00:30:29.630
explanation about contrast ratios about accessibility

00:30:29.630 --> 00:30:35.069
uh i i took a lot of time into actually quantifying

00:30:35.069 --> 00:30:38.930
that so and i guess you couldn't come to justin

00:30:38.930 --> 00:30:41.809
and just tell him okay so look i want to use

00:30:41.809 --> 00:30:44.289
this cutter scheme because it looks beautiful

00:30:44.289 --> 00:30:46.529
right because he was going to be like but but

00:30:46.529 --> 00:30:50.069
why so you had to have a lot of backup right

00:30:50.069 --> 00:30:53.750
to to back that color scheme so that he would

00:30:53.750 --> 00:30:56.779
listen and say ah makes sense yeah Let's think

00:30:56.779 --> 00:31:00.779
about it. I'll be honest one more time here.

00:31:01.819 --> 00:31:08.420
It was not quite to convince Justin. It was also

00:31:08.420 --> 00:31:12.759
to convince me that I'm doing the right thing.

00:31:13.059 --> 00:31:19.779
Because if I cannot back it up, it is actually

00:31:19.779 --> 00:31:23.440
a matter of taste. But if I can back it up with

00:31:23.440 --> 00:31:28.359
actual numbers, this background with this foreground

00:31:28.359 --> 00:31:36.099
has enough contrast ratio that these hues are

00:31:36.099 --> 00:31:40.440
different enough because they are created using

00:31:40.440 --> 00:31:45.640
perceptually uniform color space and because

00:31:45.640 --> 00:31:48.740
they have this much difference between them.

00:31:49.000 --> 00:31:53.380
So it was mostly for me and for future generations

00:31:53.380 --> 00:31:57.220
to see. Yeah, but colors are extremely complex

00:31:57.220 --> 00:32:00.160
because I have noticed you're not going to agree

00:32:00.160 --> 00:32:04.079
with everyone. And depending on the monitor that

00:32:04.079 --> 00:32:06.799
they have, if they have a 4K monitor, they will

00:32:06.799 --> 00:32:10.640
see colors differently compared to my 1080p monitor.

00:32:11.480 --> 00:32:13.539
I'm not going to look at the colors the same

00:32:13.539 --> 00:32:15.380
way that someone with a better monitor does.

00:32:15.900 --> 00:32:21.099
Man, it's extremely complex to please everyone.

00:32:22.119 --> 00:32:25.460
What happened with the pen? What? With the ban

00:32:25.460 --> 00:32:27.480
on Reddit, because we were talking about the

00:32:27.480 --> 00:32:30.380
ban and then we jumped into colors. Let's go

00:32:30.380 --> 00:32:38.720
back. I created... You've seen the random hue

00:32:38.720 --> 00:32:41.259
color scheme I showed previously. The one that

00:32:41.259 --> 00:32:44.640
you showed, yep. Yes, it was random as in its

00:32:44.640 --> 00:32:47.920
name, random hue. It was a random color scheme

00:32:47.920 --> 00:32:52.349
that used beanie .hues. module of mini .envim.

00:32:53.410 --> 00:32:59.390
But at the time, I also knew that I wanted to

00:32:59.390 --> 00:33:04.029
create not a NeoVim distro like LazyVim, but

00:33:04.029 --> 00:33:09.230
some config example that primarily uses mini

00:33:09.230 --> 00:33:13.549
.envim. I knew that. I knew that for about one

00:33:13.549 --> 00:33:15.730
and a half, two years that I wanted to create

00:33:15.730 --> 00:33:23.920
that. I only had random hue, which was relatively

00:33:23.920 --> 00:33:27.819
beautiful to my eye color scheme, but it is not

00:33:27.819 --> 00:33:31.180
for everybody to daily drive random color scheme.

00:33:31.319 --> 00:33:34.160
Because I did daily drive it for about three

00:33:34.160 --> 00:33:38.400
or four months. Basically, when you log in into

00:33:38.400 --> 00:33:41.359
NeoVim, it chooses random color scheme for you.

00:33:41.619 --> 00:33:45.970
Okay. It's nice. It works. Some color schemes

00:33:45.970 --> 00:33:50.430
I had to cheat and restart a couple of times

00:33:50.430 --> 00:33:53.130
because I didn't like them. Basically with the

00:33:53.130 --> 00:33:57.589
dark yellowish background. That's not for me.

00:33:57.710 --> 00:34:03.009
But we'll see. And so I wanted to create some

00:34:03.009 --> 00:34:06.890
static color schemes. Well, normal ones, not

00:34:06.890 --> 00:34:12.170
static. Normal color schemes. And I did daily

00:34:12.170 --> 00:34:16.489
drive them for about... several months up to

00:34:16.489 --> 00:34:21.210
that point. The four color schemes are inspired

00:34:21.210 --> 00:34:26.230
by seasons of nature. Mini -winter, mini -spring,

00:34:26.429 --> 00:34:31.409
mini -summer, and mini -autumn. The blue, green,

00:34:31.750 --> 00:34:37.110
orange, yellow, and purple, basically. And I

00:34:37.110 --> 00:34:40.909
decided to release them. Up to that point, the

00:34:40.909 --> 00:34:44.090
release of the module or something mini -dotenvim

00:34:44.480 --> 00:34:47.159
or something Neovim -related, really. For me,

00:34:47.179 --> 00:34:51.480
it was to post it on Reddit, on r slash Neovim

00:34:51.480 --> 00:34:55.239
subreddit. Okay. That was the release for me.

00:34:55.300 --> 00:35:00.760
And I did. I did post on July 10th this year

00:35:00.760 --> 00:35:05.579
eight screenshots of color schemes, because it

00:35:05.579 --> 00:35:08.079
is four color schemes with two variants. And

00:35:08.079 --> 00:35:12.119
basically, last -minute decision. Very dumb last

00:35:12.119 --> 00:35:18.239
-minute decision. was to add to each screenshot

00:35:18.239 --> 00:35:24.280
a link to color scheme, basically. But that link

00:35:24.280 --> 00:35:28.880
was the same. So what Reddit thought I did, I

00:35:28.880 --> 00:35:34.480
created a post with eight very similar screenshots.

00:35:35.420 --> 00:35:38.400
because they are the same text, just different

00:35:38.400 --> 00:35:42.639
colors. Each one with the same link, which is

00:35:42.639 --> 00:35:47.199
very suspicious. I agree. It was my mistake,

00:35:47.440 --> 00:35:51.860
and it's probably a good decision by Reddit filter.

00:35:52.159 --> 00:35:55.500
But also, I think what contributed to that ban

00:35:55.500 --> 00:36:02.340
was that I also created a comment under that

00:36:02.340 --> 00:36:06.489
post. written some stuff, here are my color schemes,

00:36:06.710 --> 00:36:11.050
hooray. But after that, I immediately noticed

00:36:11.050 --> 00:36:16.349
a typo and edited it. Okay. I might have done

00:36:16.349 --> 00:36:19.210
it also the second time. I don't quite remember.

00:36:19.469 --> 00:36:23.289
But on the second or third time, after I wanted

00:36:23.289 --> 00:36:26.230
to edit it again, because I did notice something

00:36:26.230 --> 00:36:31.010
again, Reddit said, you cannot do that. I said,

00:36:31.110 --> 00:36:37.110
why, Reddit, why? And it turned out I was shadow

00:36:37.110 --> 00:36:41.269
banned because I got an email right away that

00:36:41.269 --> 00:36:44.630
we are concerned for your safety, your account

00:36:44.630 --> 00:36:49.530
demonstrated some suspicious activity, which

00:36:49.530 --> 00:36:57.090
it did. I agree. I fully agree it did look suspiciously.

00:36:57.090 --> 00:37:03.719
But it was honest work. I would say. So it asked

00:37:03.719 --> 00:37:07.739
me to change my password. I did immediately within

00:37:07.739 --> 00:37:12.900
10 minutes. And I was able to log in. My surprise

00:37:12.900 --> 00:37:17.739
and horror, all my previous posts were hidden

00:37:17.739 --> 00:37:22.019
by the Reddit algorithm, which it is the result

00:37:22.019 --> 00:37:25.460
of the shadow ban, as I later discovered. And

00:37:25.460 --> 00:37:31.449
I tried to appeal, made multiple appeals. In

00:37:31.449 --> 00:37:36.650
total. I read a lot of stuff how to do it. Because

00:37:36.650 --> 00:37:44.010
basically all things NeoVim related that I did,

00:37:44.110 --> 00:37:46.869
I did through Reddit, announced them through

00:37:46.869 --> 00:37:52.050
Reddit. They were searchable in all major search

00:37:52.050 --> 00:37:55.050
engines through Reddit. The only thing that's

00:37:55.050 --> 00:37:59.000
left is GitHub, which is okay. of course but

00:37:59.000 --> 00:38:02.920
uh all those announcements and conversations

00:38:02.920 --> 00:38:07.099
and comments under uh posts were done and if

00:38:07.099 --> 00:38:09.480
you search in google you get to a reddit post

00:38:09.480 --> 00:38:15.780
usually right so yes yeah so i was very upset

00:38:15.780 --> 00:38:21.820
very uh but oh well i decided to try to appeal

00:38:21.820 --> 00:38:26.000
they didn't work it was july 10th again after

00:38:26.670 --> 00:38:31.469
About a month, I thought, well, this might be

00:38:31.469 --> 00:38:34.150
a good opportunity to create a website and to

00:38:34.150 --> 00:38:41.030
actually own the content that I create. And if

00:38:41.030 --> 00:38:44.429
when there is an opportunity for me to post on

00:38:44.429 --> 00:38:48.210
Reddit, I will do it via blog post and just share

00:38:48.210 --> 00:38:51.050
a link to the site. That's it. Something that

00:38:51.050 --> 00:38:54.809
I noticed on Reddit is that if the post is too

00:38:54.809 --> 00:38:58.800
long, It goes through moderator approval. But

00:38:58.800 --> 00:39:01.300
if it's like extremely long, because I used to

00:39:01.300 --> 00:39:03.679
share a video with a lot of text, right? The

00:39:03.679 --> 00:39:06.039
timeline for the videos. The timestamps. The

00:39:06.039 --> 00:39:08.980
timestamps. Yeah, I know. The entire thing. And

00:39:08.980 --> 00:39:12.039
it goes through approval. And I was like, I asked

00:39:12.039 --> 00:39:14.460
the moderators, but why does it do that? And

00:39:14.460 --> 00:39:17.500
they're like, it's Reddit. And then I said, okay,

00:39:17.579 --> 00:39:20.840
let me try just posting the video without the

00:39:20.840 --> 00:39:24.369
timestamps. And it goes through, right? if someone

00:39:24.369 --> 00:39:28.349
watching this out there post like really long

00:39:28.349 --> 00:39:32.889
um posts of course on reddit they might go through

00:39:32.889 --> 00:39:36.650
moderator and uh there's not much but it's only

00:39:36.650 --> 00:39:40.110
if it's huge if if the text is it's like a lot

00:39:40.110 --> 00:39:43.530
like five five thousand words well it makes sense

00:39:43.530 --> 00:39:47.769
i cannot blame this side it makes sense to do

00:39:47.769 --> 00:39:51.059
that yeah yeah yeah it does it does but i didn't

00:39:51.059 --> 00:39:53.440
know i was like but why does it go through mother

00:39:53.440 --> 00:39:55.880
and some of them wouldn't go through approval

00:39:55.880 --> 00:39:58.719
and some other did and i was like why does it

00:39:58.719 --> 00:40:01.960
do that but it's if it's a long post it does

00:40:01.960 --> 00:40:07.260
it yeah but to finish that story on a bright

00:40:07.260 --> 00:40:12.820
note after about one and a half months literally

00:40:12.820 --> 00:40:18.659
i decided literally on august 23rd i decided

00:40:18.659 --> 00:40:25.610
to create a new account okay and explain maybe

00:40:25.610 --> 00:40:32.570
to people or just try to acquire more karma to

00:40:32.570 --> 00:40:37.489
be able to post again but the day i decided to

00:40:37.489 --> 00:40:43.349
do that i wake up and on reddit by total coincidence

00:40:43.349 --> 00:40:49.420
i swear there was a post from some user asking,

00:40:49.480 --> 00:40:53.360
there was a mini .env author here, very active.

00:40:53.679 --> 00:40:58.880
Does anybody know where he is? What's the matter?

00:40:59.679 --> 00:41:03.480
So I decided to, it's still locked, that post.

00:41:03.599 --> 00:41:07.659
I decided to still create a backup. Not still,

00:41:07.800 --> 00:41:12.539
I decided to make it that the new account right

00:41:12.539 --> 00:41:16.570
away created it. and described what happened,

00:41:16.670 --> 00:41:19.809
basically what I told to you, but more concisely.

00:41:20.030 --> 00:41:24.769
It got upvoted. Many people shared, that's terrible.

00:41:25.690 --> 00:41:30.449
I said, I know. And this was with your new account,

00:41:30.670 --> 00:41:33.329
right? With the other account. Yes, yes, yes.

00:41:33.550 --> 00:41:36.449
Because the old one, you cannot post anything

00:41:36.449 --> 00:41:40.710
at all. I could post it, but nobody could see

00:41:40.710 --> 00:41:44.030
it. oh that's what shadow bat is okay it's uh

00:41:44.030 --> 00:41:47.750
it's what i learned is that a pretty clever way

00:41:47.750 --> 00:41:54.230
i think to uh deal with spam bots okay bots uh

00:41:54.230 --> 00:41:58.090
you don't show anything that they are blocked

00:41:58.090 --> 00:42:01.210
they keep spamming they they think they work

00:42:01.210 --> 00:42:06.500
great yes but nobody no nobody sees them Okay,

00:42:06.639 --> 00:42:10.840
makes sense. Yeah, so from the new account, I

00:42:10.840 --> 00:42:17.900
described what happened. And by sheer miracle,

00:42:18.079 --> 00:42:23.699
within... Ah, no, there is a moderator, Lukas

00:42:23.699 --> 00:42:27.159
Reinek. Lukas, let's just call him Lukas. The

00:42:27.159 --> 00:42:30.719
creator of Rainbow... No, indent blank line.

00:42:30.940 --> 00:42:35.750
Indent, yeah. Yes, he is the main moderator there

00:42:35.750 --> 00:42:42.429
on Reddit. And he answered, well, that's awful,

00:42:42.670 --> 00:42:46.849
but if you have links to the posts that were

00:42:46.849 --> 00:42:50.849
hidden in the Neovim community, I can see, I

00:42:50.849 --> 00:42:55.889
think I can make them visible, but they will

00:42:55.889 --> 00:43:01.809
not show in Google. in any other major search

00:43:01.809 --> 00:43:05.210
engines uh i said great thank you that's very

00:43:05.210 --> 00:43:11.230
helpful of you i i shared all the uh posts because

00:43:11.230 --> 00:43:15.909
i did have them all the links just in case and

00:43:15.909 --> 00:43:21.250
he did he did go one by one uh manually clicking

00:43:21.250 --> 00:43:24.530
on them and making them visible which i'm very

00:43:24.530 --> 00:43:27.309
grateful to you lucas if you happen to see this

00:43:27.309 --> 00:43:30.679
i don't know but after that within hour or two

00:43:30.679 --> 00:43:36.260
i get a direct message on reddit on the ua account

00:43:36.260 --> 00:43:40.800
that with text something like this can you check

00:43:40.800 --> 00:43:44.219
your previous account it should be restored okay

00:43:44.219 --> 00:43:48.219
who are you why should be restored i don't know

00:43:48.219 --> 00:43:51.920
if it is it a scam about a scam or i don't know

00:43:51.920 --> 00:43:55.030
i check It is restored. I don't know what to

00:43:55.030 --> 00:44:00.449
say. I have tears of joy. I laugh through the

00:44:00.449 --> 00:44:04.929
roof for Hooray and so on. But I answer, yes,

00:44:04.929 --> 00:44:07.570
it is. Thank you so much. It turns out that it

00:44:07.570 --> 00:44:11.929
was a person who works in Reddit in the company.

00:44:12.090 --> 00:44:17.610
And he is a new user or just a new subreddit

00:44:17.610 --> 00:44:22.329
enjoyer. I don't know. But he shared this with...

00:44:22.860 --> 00:44:28.579
team moderator with reddit admins okay and they

00:44:28.579 --> 00:44:32.579
saw that it was just a false positive from the

00:44:32.579 --> 00:44:35.059
algorithm and they restored the account immediately

00:44:35.059 --> 00:44:40.519
so i have the e chasnovsky a chasnovsky account

00:44:40.519 --> 00:44:45.199
on reddit which i'm very happy about but it did

00:44:45.199 --> 00:44:49.340
make a jump scare which provided very beautiful

00:44:49.340 --> 00:44:52.340
results for me in the form of the website which

00:44:52.340 --> 00:44:55.360
i'm very grateful i think when life gives you

00:44:55.360 --> 00:44:59.840
lemons you make let's say lemonade okay so now

00:44:59.840 --> 00:45:02.619
your website is gonna be like the main source

00:45:02.619 --> 00:45:05.639
you know for for the information right i plan

00:45:05.639 --> 00:45:12.019
to yes uh i plan to also uh i won't say move

00:45:12.019 --> 00:45:18.860
off github but i do plan to first introduce mirrors

00:45:18.860 --> 00:45:23.969
outside of github or the plugin itself. And in

00:45:23.969 --> 00:45:27.110
the future, I don't know how distant. It may

00:45:27.110 --> 00:45:30.989
be several months, maybe one or two years. I

00:45:30.989 --> 00:45:36.090
sincerely don't know. I want to self -host a

00:45:36.090 --> 00:45:43.349
Git server and to make it the primary source

00:45:43.349 --> 00:45:47.489
for Media .nv plugin. So a lot of people are

00:45:47.489 --> 00:45:49.969
moving over to Codeburg. Have you thought about

00:45:49.969 --> 00:45:54.880
it? yeah or no uh it it is it will be one of

00:45:54.880 --> 00:45:58.139
the mirrors okay i've already i've already created

00:45:58.139 --> 00:46:02.579
their my username i also created an organization

00:46:02.579 --> 00:46:07.380
for nvims the dash mini uh i have that the other

00:46:07.380 --> 00:46:11.659
one i plan to do i think you you might not have

00:46:11.659 --> 00:46:14.940
heard about it do have you heard about uh the

00:46:14.940 --> 00:46:20.880
site called tangled nope e -a -n G -L -E -T,

00:46:21.059 --> 00:46:24.599
Tangled. Let me look it up. Tangled .org. It

00:46:24.599 --> 00:46:30.280
is a Git forge that, yeah, it is a Git forge

00:46:30.280 --> 00:46:35.320
that is based on AT Proto, AT Protocol, which

00:46:35.320 --> 00:46:42.159
is one of the main creations of Blue Sky company

00:46:42.159 --> 00:46:47.320
right now. Okay. Blue Sky, it is not only the

00:46:47.320 --> 00:46:51.719
Twitter. alternative right now or microblogging

00:46:51.719 --> 00:46:57.179
site they also create a well sort of decentralized

00:46:57.179 --> 00:47:02.920
protocol a protocol for a decentralized social

00:47:02.920 --> 00:47:07.599
stuff open social it's usually called in the

00:47:07.599 --> 00:47:12.460
internet so Tangled is very much it is very new

00:47:12.460 --> 00:47:18.360
it is basically planned to be a github alternative

00:47:19.199 --> 00:47:25.719
what is called git forges not only a git server

00:47:25.719 --> 00:47:31.519
but git forge where you can file issues create

00:47:31.519 --> 00:47:35.639
prs pull requests or merge requests or patch

00:47:35.639 --> 00:47:39.280
requests there are many of them okay i spent

00:47:39.280 --> 00:47:43.980
i spent a couple of months ago quite obsessively

00:47:43.980 --> 00:47:49.849
obsessively researching this this topic because

00:47:49.849 --> 00:47:56.210
uh sometimes uh i do think a lot about self -hosting

00:47:56.210 --> 00:48:03.469
but and uh the research it was a lot basically

00:48:03.469 --> 00:48:06.889
because and why github why are you planning on

00:48:06.889 --> 00:48:09.389
are you leaving github completely like in the

00:48:09.389 --> 00:48:12.210
future or you're you're still gonna have it okay

00:48:12.210 --> 00:48:15.670
just as backups the other options right well

00:48:16.119 --> 00:48:19.099
Let's just say, unless something really terrible

00:48:19.099 --> 00:48:22.619
happens with GitHub, like really terrible, I

00:48:22.619 --> 00:48:25.360
don't really know what. I don't think it will,

00:48:25.500 --> 00:48:30.480
but maybe, but probably not. I do plan, of course,

00:48:30.500 --> 00:48:33.500
to have at least a mirror on GitHub, yes. But

00:48:33.500 --> 00:48:38.079
it is very probably, probably very distant plans.

00:48:38.400 --> 00:48:41.260
It is not immediate plans, probably very distant.

00:48:41.559 --> 00:48:47.400
Immediate short -term plans. are to just create

00:48:47.400 --> 00:48:51.760
off GitHub mirrors. And that's all. All interactions,

00:48:51.920 --> 00:48:56.360
issues, PRs will be on GitHub for the foreseeable

00:48:56.360 --> 00:49:03.300
future. But I understand that people, the ever

00:49:03.300 --> 00:49:06.360
-growing number of people do not like to use

00:49:06.360 --> 00:49:11.260
GitHub. And I get that, honestly. I can understand

00:49:11.260 --> 00:49:16.719
it. I'm still... tied to this as a platform but

00:49:16.719 --> 00:49:20.840
oh well yeah okay okay makes sense now there

00:49:20.840 --> 00:49:23.699
was a lot of confusion for me with your repo

00:49:23.699 --> 00:49:26.019
because it's like a repo and it has a lot of

00:49:26.019 --> 00:49:29.079
modules but you already changed that so now it's

00:49:29.079 --> 00:49:31.500
in a different organization same organization

00:49:31.500 --> 00:49:35.079
you mind explaining How all this works is I don't

00:49:35.079 --> 00:49:37.739
understand. I know there's mini .envim. Why don't

00:49:37.739 --> 00:49:40.559
we start from there? What is mini .envim? How

00:49:40.559 --> 00:49:44.039
do the modules work? The repos? I think we can

00:49:44.039 --> 00:49:46.239
switch to your screen if it makes it easier for

00:49:46.239 --> 00:49:50.260
you. My trackball, I don't use mouse at the moment.

00:49:50.340 --> 00:49:54.280
My trackball is on the left side because this

00:49:54.280 --> 00:49:58.780
is the only way I can set up the camera. Okay.

00:50:00.860 --> 00:50:06.460
Media .envim is a plugin. Okay. One single plugin.

00:50:06.579 --> 00:50:10.059
You can install it. This is the current form

00:50:10.059 --> 00:50:16.460
of how to install it prior to NeoVim 0 .12, which

00:50:16.460 --> 00:50:20.139
will have the built -in plugin manager. But until

00:50:20.139 --> 00:50:23.559
then, you can just bootstrap it, install it,

00:50:23.639 --> 00:50:28.300
and you'll have 44, at the moment, there will

00:50:28.300 --> 00:50:32.139
be more, different modules. All of them... All

00:50:32.139 --> 00:50:38.940
of them are separate, independent, provide functionality

00:50:38.940 --> 00:50:42.820
that is actually useful in day -to -day life.

00:50:43.199 --> 00:50:45.500
Most of them, apart from these three. I have

00:50:45.500 --> 00:50:47.420
a question. Hold on, I'm sorry to interrupt.

00:50:47.800 --> 00:50:50.179
What do you use for the picker? Because for the

00:50:50.179 --> 00:50:53.480
picker, I use one by Folky. What is it called?

00:50:53.659 --> 00:50:55.539
I don't know how to pronounce Folky, by the way.

00:50:55.880 --> 00:50:58.679
Folkaf? I don't know, but... You know how to

00:50:58.679 --> 00:51:00.539
pronounce it. I think you pronounce it correctly,

00:51:00.800 --> 00:51:04.960
Folky. bulky okay okay i i think so yes okay

00:51:04.960 --> 00:51:09.880
i use um which is the snacks snacks snacks .picker

00:51:09.880 --> 00:51:12.659
yes yeah picker yeah you have one for a picker

00:51:12.659 --> 00:51:17.019
as well of course of course i do this one okay

00:51:17.019 --> 00:51:20.860
this is uh this is mini peak mini dot pick what's

00:51:20.860 --> 00:51:23.199
the difference between this okay because here

00:51:23.199 --> 00:51:25.940
you can search right and many that files you

00:51:25.940 --> 00:51:31.800
can see like many files many files it is Or it

00:51:31.800 --> 00:51:35.179
is File Explorer. Okay. I use MIDI files and

00:51:35.179 --> 00:51:38.099
I use NextPicker. But you have a picker as well.

00:51:38.199 --> 00:51:44.480
I'm sorry. Of course. Of course I do. It is the

00:51:44.480 --> 00:51:49.980
most complex module to date because it has to

00:51:49.980 --> 00:51:55.440
be performant. Which it is. It is very performant.

00:51:55.539 --> 00:52:00.039
This is the MIDI .pick. which has these built

00:52:00.039 --> 00:52:05.760
-in pickers for files for live grep or grep i

00:52:05.760 --> 00:52:10.440
think for buffers help tags for command line

00:52:10.440 --> 00:52:16.179
output you can use it already it is enough in

00:52:16.179 --> 00:52:22.519
itself the the the lisan vimgaib showcased it

00:52:23.600 --> 00:52:32.340
Because I did notice some spike in midi .pick.

00:52:34.199 --> 00:52:37.119
Clones, git clones, GitHub can show you that.

00:52:37.320 --> 00:52:42.059
I did notice some spike when he mentioned it

00:52:42.059 --> 00:52:45.960
in one of his videos that he at that point at

00:52:45.960 --> 00:52:53.699
least preferred midi .pick. That's all that pickers

00:52:53.699 --> 00:52:57.480
are built in. Can you create your custom filter?

00:52:58.019 --> 00:53:05.079
Yes, yes. You can create anything. Where is it?

00:53:05.760 --> 00:53:12.719
You can create custom picker from ground up.

00:53:13.019 --> 00:53:19.110
It can have custom... name, working directory,

00:53:19.349 --> 00:53:25.449
it can match differently, like the, for example,

00:53:25.630 --> 00:53:30.889
file speaker has default matching, which is very

00:53:30.889 --> 00:53:37.090
simple. The idea was to create first, performance,

00:53:37.489 --> 00:53:42.510
and second, simple enough that users can actually

00:53:42.510 --> 00:53:47.369
understand what's going on. Because many pickers,

00:53:47.409 --> 00:53:52.630
well, I won't say many, but what tends to happen

00:53:52.630 --> 00:53:55.170
with fuzzy pickers, in my mind, in my opinion,

00:53:55.329 --> 00:54:01.349
is that the results are a bit too magical, at

00:54:01.349 --> 00:54:05.550
least to my taste. For example, some pickers,

00:54:05.550 --> 00:54:10.070
when you type, I don't know, two letters, they

00:54:10.070 --> 00:54:17.280
prefer to first match How do I describe it? To

00:54:17.280 --> 00:54:21.920
match, to... Search for the exact match? No,

00:54:22.139 --> 00:54:25.440
that's not it. Not for exact match. Okay. They

00:54:25.440 --> 00:54:32.019
tend to give more, to prefer more those items

00:54:32.019 --> 00:54:39.159
that have, for example, first letter as the first

00:54:39.159 --> 00:54:42.099
letter of the directory. and the second letter

00:54:42.099 --> 00:54:47.300
as the first letter of the file name. So the

00:54:47.300 --> 00:54:50.860
logic is that if you want to find a file, for

00:54:50.860 --> 00:54:54.480
example, like here, a test .dir .visit file,

00:54:54.719 --> 00:55:00.239
you just type tdf, and it will match it first.

00:55:00.519 --> 00:55:07.860
But in Minipig, if you type tdf, it prefers...

00:55:08.639 --> 00:55:13.320
to, it prefers matches that have, it prefers

00:55:13.320 --> 00:55:18.519
items that match this query with the shortest

00:55:18.519 --> 00:55:22.119
distance between first and last match. So this

00:55:22.119 --> 00:55:25.239
is, here is one, two, three, three letters between

00:55:25.239 --> 00:55:31.940
T and F. Okay. If there are three letters, if

00:55:31.940 --> 00:55:38.360
several items have match. with the same width,

00:55:38.579 --> 00:55:40.739
which is three letters, well, like first and

00:55:40.739 --> 00:55:44.519
second here, it will prefer the one which has

00:55:44.519 --> 00:55:50.280
the first match closer to the start of the string.

00:55:50.739 --> 00:55:53.739
And that's basically it. That's the whole matching

00:55:53.739 --> 00:55:58.380
algorithm. You can see it right here. First match

00:55:58.380 --> 00:56:04.340
starts at 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, I think.

00:56:04.760 --> 00:56:08.539
Tenth letter. the second match has the same width

00:56:08.539 --> 00:56:13.440
but it starts later so it is preferred less next

00:56:13.440 --> 00:56:17.679
matches are start even further and they preferred

00:56:17.679 --> 00:56:23.699
even even less even more less even less preferred

00:56:23.699 --> 00:56:28.320
less if i can navigate or it could be a lot ah

00:56:28.320 --> 00:56:31.460
here it is let me ask you something does it have

00:56:31.460 --> 00:56:36.329
yeah a free cnc or recent option uh uh it doesn't

00:56:36.329 --> 00:56:40.030
have uh at the moment not in the moment it doesn't

00:56:40.030 --> 00:56:46.130
have in minipig itself okay but uh as as as is

00:56:46.130 --> 00:56:50.309
the case uh often in minute and vim uh there

00:56:50.309 --> 00:56:54.409
is another module for that okay uh there is a

00:56:54.409 --> 00:56:58.090
like a job just here many visits many visits

00:56:58.090 --> 00:57:05.650
is is a uh module that automatically tracks your

00:57:05.650 --> 00:57:10.849
file and directory visits in a persistent manner.

00:57:11.050 --> 00:57:15.969
It basically stores it on the disk and allows

00:57:15.969 --> 00:57:25.309
to sort those visits based on how often you visit

00:57:25.309 --> 00:57:31.699
that path. And how recent, basically, Frequency.

00:57:31.940 --> 00:57:38.679
Frequent and recent. So it is in a separate picker.

00:57:39.000 --> 00:57:42.880
Okay. A separate picker, this one, which is visited

00:57:42.880 --> 00:57:47.739
paths. See? Visited paths from all working directories.

00:57:47.840 --> 00:57:52.159
This is what my Frequency algorithm shows right

00:57:52.159 --> 00:57:56.239
now. So ghosty config, change log, pick because

00:57:56.239 --> 00:58:00.800
I recently did it, visited it. And a lot of other

00:58:00.800 --> 00:58:04.440
stuff. So you have to open a different picker

00:58:04.440 --> 00:58:08.780
for this, right? For Frequency, yes. For Frequency?

00:58:09.039 --> 00:58:14.039
Okay. For Frequency. For Files Picker, it just

00:58:14.039 --> 00:58:24.860
asks Ribjarep, RG, Klee, to please give me a

00:58:24.860 --> 00:58:32.610
list of files. it does so very quickly and file

00:58:32.610 --> 00:58:37.570
speaker just shows that after that it is it the

00:58:37.570 --> 00:58:43.150
match is done by a mini pick itself it is purely

00:58:43.150 --> 00:58:47.750
lua so it's fairly fast and without overhead

00:58:47.750 --> 00:58:51.110
okay there are other other there are other pickers

00:58:51.110 --> 00:58:54.989
that are also great snake speaker is great it

00:58:54.989 --> 00:59:00.429
has It might be a bit complicated, but it works.

00:59:01.289 --> 00:59:07.730
And it works good. There is also FZF -Lua. Also

00:59:07.730 --> 00:59:11.730
great. It works. But it has also slightly different

00:59:11.730 --> 00:59:17.610
approach. It uses FZF CLI tool directly in what

00:59:17.610 --> 00:59:21.670
basically is, I think, built -in terminal window.

00:59:22.489 --> 00:59:26.840
It has its... It has its downsides, it has its

00:59:26.840 --> 00:59:30.639
upsides, but I really like Minipig. What can

00:59:30.639 --> 00:59:34.079
I say? You're biased, of course. Of course. And

00:59:34.079 --> 00:59:36.480
Telescope. What about Telescope? Have you ever

00:59:36.480 --> 00:59:41.780
used it? I used it prior to Minipig, yes. Well,

00:59:42.599 --> 00:59:48.280
basically because it was the one picker at the

00:59:48.280 --> 00:59:55.219
time, yes. I used it, yes. It was fine. How do

00:59:55.219 --> 00:59:59.800
I put it? It was a revelation for me to actually

00:59:59.800 --> 01:00:02.420
start using fuzzy pickers because I didn't use

01:00:02.420 --> 01:00:07.159
them prior to that. It is really a cool idea.

01:00:09.059 --> 01:00:13.099
And I did use it. Could we say, do you know if

01:00:13.099 --> 01:00:16.579
there were any pickers before? Because DJ is

01:00:16.579 --> 01:00:19.219
the one that started with the telescope, right?

01:00:19.280 --> 01:00:23.480
Yes, yes, yes, he did. Did he then... create

01:00:23.480 --> 01:00:28.079
that idea of fuzzy pickers? No, no, no. Of course.

01:00:28.400 --> 01:00:32.539
Well, at least FZF is a thing for a very long

01:00:32.539 --> 01:00:36.519
time. Oh, okay. Yeah, FZF. But I say NeoVim plugins.

01:00:36.880 --> 01:00:40.960
Did we have any? Well, prior to NeoVim, there

01:00:40.960 --> 01:00:46.539
was Vim. And for Vim, there are a lot of fuzzy

01:00:46.539 --> 01:00:50.820
pickers as well. Okay. Well, I say a lot, not

01:00:50.820 --> 01:00:54.320
a lot. But they definitely were. I think, yes,

01:00:54.400 --> 01:00:58.659
Snap was a fuzzy picker. VimScript, I think it

01:00:58.659 --> 01:01:02.900
still is around. It might be. Okay. Because Vim

01:01:02.900 --> 01:01:07.820
users will use Vim. Okay. Why, man, we're all

01:01:07.820 --> 01:01:09.820
over the place. We're all over the place. Yes.

01:01:10.119 --> 01:01:13.840
It doesn't matter. We will remember and we will

01:01:13.840 --> 01:01:16.420
come back to your demo. But I just want to ask

01:01:16.420 --> 01:01:20.650
you, why did you move from Vim to NeoVim? Because

01:01:20.650 --> 01:01:24.170
it was cool. Okay, the cool kids were doing it.

01:01:24.309 --> 01:01:29.750
No, not necessarily cool kids were doing it.

01:01:29.869 --> 01:01:36.050
Why did I move? It was, let me, ah, yes, I think

01:01:36.050 --> 01:01:40.590
I remember. My whole journey was a bit, it started

01:01:40.590 --> 01:01:51.079
in, I think, 2019, 19 or 18. I saw on the internet

01:01:51.079 --> 01:01:54.480
discussions about Vim versus Emacs because it

01:01:54.480 --> 01:01:58.340
was a very hot topic, I think, even back then.

01:01:59.519 --> 01:02:05.159
And I did try Emacs. I did. I didn't like it.

01:02:06.539 --> 01:02:11.260
Mostly because I think it was a separate application

01:02:11.260 --> 01:02:15.119
that I needed to install. It is okay. for people

01:02:15.119 --> 01:02:21.019
if they want to use that. I just liked the idea

01:02:21.019 --> 01:02:31.559
of Vim itself and its motions philosophy, its

01:02:31.559 --> 01:02:36.579
text editing as a language philosophy. Like operators,

01:02:37.159 --> 01:02:43.440
text objects, motions, like IW for inner word.

01:02:44.239 --> 01:02:49.599
f to find all that stuff like d i w delete inside

01:02:49.599 --> 01:02:56.559
word and it's like it's magic so i sticked with

01:02:56.559 --> 01:03:02.420
vim at that point but not vim vim i at that time

01:03:02.420 --> 01:03:08.599
used the tool ide called r studio because i worked

01:03:08.599 --> 01:03:12.619
with r language still work a bit but at the time

01:03:12.619 --> 01:03:16.719
it was more professional basically with R language

01:03:16.719 --> 01:03:20.599
in R studio and I used a Vim emulation there

01:03:20.599 --> 01:03:27.840
it was okay so I tried to ease myself into using

01:03:27.840 --> 01:03:33.139
actual Vim I might have tried it late 2019 I

01:03:33.139 --> 01:03:37.440
think actual Vim but I remember I remember one

01:03:37.440 --> 01:03:41.599
episode very vividly. I think it was first or

01:03:41.599 --> 01:03:46.679
second day when I started to try to daily drive

01:03:46.679 --> 01:03:52.739
it in the office and work when I worked. Okay.

01:03:53.039 --> 01:03:57.980
Where I worked back then. And someone wanted

01:03:57.980 --> 01:04:03.820
me to share a link from my document, which was

01:04:03.820 --> 01:04:07.460
opened in Vim. And I could not do it. I could

01:04:07.460 --> 01:04:14.099
not copy into the clipboard. Yes, I could not

01:04:14.099 --> 01:04:18.039
do it. I don't know. I didn't know how to do

01:04:18.039 --> 01:04:22.920
it. I was very green back then. So I panicked

01:04:22.920 --> 01:04:27.500
a bit and thought maybe a bit later, maybe when

01:04:27.500 --> 01:04:31.780
I have more time to practice, maybe I then daily

01:04:31.780 --> 01:04:36.599
drive it. But I did it for some time. Then COVID

01:04:36.599 --> 01:04:42.119
happened in March 2020, in Ukraine at least.

01:04:42.340 --> 01:04:50.480
And we were starting to work remotely. And for

01:04:50.480 --> 01:04:54.440
me, it was, I'm so sorry that I have to share

01:04:54.440 --> 01:04:59.280
this, but I started to use VS Code back then.

01:04:59.719 --> 01:05:08.099
mostly because it allowed very easily for a remote

01:05:08.099 --> 01:05:11.440
work and i could remotely connect to my working

01:05:11.440 --> 01:05:15.519
computer and do some heavy data analysis which

01:05:15.519 --> 01:05:20.420
i did back then on the work computer so i did

01:05:20.420 --> 01:05:27.179
use vs code but with the vim emulation but not

01:05:27.179 --> 01:05:32.230
just Not just Vim emulation, but the one that

01:05:32.230 --> 01:05:36.250
comes from VS Code NeoVim plugin. Oh, I saw that

01:05:36.250 --> 01:05:38.190
and I didn't understand the difference between

01:05:38.190 --> 01:05:41.550
the Vim and NeoVim one. And I was like, I don't

01:05:41.550 --> 01:05:47.349
know. What VS Code NeoVim does, it actually runs

01:05:47.349 --> 01:05:54.230
NeoVim, actual NeoVim in the background and communicates

01:05:54.230 --> 01:05:59.579
between VS Code's text. file buffer, I don't

01:05:59.579 --> 01:06:02.900
know how it's called in VS Code, communicates

01:06:02.900 --> 01:06:07.800
to the actual NeoBeam, does its work back there,

01:06:08.000 --> 01:06:13.519
and translates it back into VS Code. So it's

01:06:13.519 --> 01:06:17.059
not emulation. It's not a Veeam emulation, it's

01:06:17.059 --> 01:06:20.739
actual NeoBeam that runs in the background. Okay.

01:06:21.000 --> 01:06:25.099
I think, I'm not sure, you might correct me later,

01:06:25.320 --> 01:06:29.019
I think Justin M. Keys, was heavily involved

01:06:29.019 --> 01:06:33.480
in creating this uh might be might be probably

01:06:33.480 --> 01:06:37.619
not the creator the creator was acevetlakov i

01:06:37.619 --> 01:06:40.280
think it was on github but justin was heavily

01:06:40.280 --> 01:06:45.960
involved in i think making it work so that's

01:06:45.960 --> 01:06:49.559
where i thought that neo vim is cool basically

01:06:49.559 --> 01:06:56.500
and i i've searched my dot files today in preparation

01:06:56.500 --> 01:07:00.500
for this interview. And I think my actual NeoVim

01:07:00.500 --> 01:07:06.639
config started around summer of 2020. It was

01:07:06.639 --> 01:07:10.360
Vim script back then, but I used NeoVim. Started

01:07:10.360 --> 01:07:15.099
to use NeoVim probably because of VS Code NeoVim

01:07:15.099 --> 01:07:20.309
plugin in VS Code. So the first time that you

01:07:20.309 --> 01:07:22.989
tried, well, the first few times you got defeated

01:07:22.989 --> 01:07:26.090
by Vim motions and NeoVim, right? Yeah, okay.

01:07:26.289 --> 01:07:29.190
No, not Vim motions, not Vim motions, just clipboard.

01:07:29.409 --> 01:07:31.570
Oh, the clipboard. Oh, the system clipboard,

01:07:31.590 --> 01:07:33.929
yeah. Because there's a lot of people that, you

01:07:33.929 --> 01:07:37.969
know, try to start with NeoVim. Because you see

01:07:37.969 --> 01:07:41.250
YouTubers flying around in NeoVim and copy -paste

01:07:41.250 --> 01:07:43.289
and from here to there and from this session

01:07:43.289 --> 01:07:46.489
to this other session, open file, you know, and

01:07:46.489 --> 01:07:49.280
it's like, man. That seems nice. That seems easy.

01:07:49.519 --> 01:07:51.659
Let me give it a try. And when you give it a

01:07:51.659 --> 01:07:55.559
try, man, it's like, I remember, you know, my

01:07:55.559 --> 01:07:59.119
first few rounds with Vim, you know, this was

01:07:59.119 --> 01:08:02.480
way, way too long ago before Niven was a thing.

01:08:03.019 --> 01:08:06.579
And I didn't like it. I was like, I have to do

01:08:06.579 --> 01:08:09.239
it. Why do people do it? That's what I wondered.

01:08:10.090 --> 01:08:12.650
Why does someone go through this like H -A -K?

01:08:12.849 --> 01:08:15.110
Oh, man, just use the mouse, copy, paste, and

01:08:15.110 --> 01:08:17.210
you're done. And I was like, no, I don't like

01:08:17.210 --> 01:08:20.090
this. I tried it, like, to be honest with you,

01:08:20.109 --> 01:08:21.949
I don't know, four or five times. And I was like,

01:08:22.090 --> 01:08:25.710
no, no, no, no, not for me. Went to Nano. I used

01:08:25.710 --> 01:08:28.390
VS Code. I'm not a programmer, you know, so I

01:08:28.390 --> 01:08:31.329
didn't have to use it that much. But I was like,

01:08:31.489 --> 01:08:35.170
no, no, no, no, not for me. Do you remember feeling

01:08:35.170 --> 01:08:37.470
that way? Or do you think it's at the beginning,

01:08:37.689 --> 01:08:43.659
the very beginning? try to not forget this feeling,

01:08:43.840 --> 01:08:49.979
that feeling of people that are new to both of

01:08:49.979 --> 01:08:57.659
them. But I think I start to forget how they

01:08:57.659 --> 01:09:04.220
feel. Yes, that's a very big thing for me. And

01:09:04.220 --> 01:09:11.229
one of the main motivations for... Well, probably

01:09:11.229 --> 01:09:14.569
not the main motivations, but why... How do I

01:09:14.569 --> 01:09:20.609
describe it? Probably that I enjoy reading and

01:09:20.609 --> 01:09:25.550
helping people on Reddit, because they might

01:09:25.550 --> 01:09:30.130
not understand some things, and it is a win -win

01:09:30.130 --> 01:09:35.850
for me. I help them, and they already have helped

01:09:35.850 --> 01:09:41.680
me. by providing a feedback on what things might

01:09:41.680 --> 01:09:44.859
be complex for them to understand. It is both

01:09:44.859 --> 01:09:50.000
for NeoVim and mini .envim, basically. So every

01:09:50.000 --> 01:09:54.319
question, there are no stupid questions. Well,

01:09:54.439 --> 01:10:00.159
there might be, but most of them that people

01:10:00.159 --> 01:10:04.939
think are stupid are not. people have stupid

01:10:04.939 --> 01:10:08.439
questions then it might be because documentation

01:10:08.439 --> 01:10:14.439
is bad it might be because the actual thing is

01:10:14.439 --> 01:10:18.899
not intuitive of course but usually it is a bad

01:10:18.899 --> 01:10:25.220
document after there is a better help better

01:10:25.220 --> 01:10:33.729
docs it might be easier for next people to start

01:10:33.729 --> 01:10:37.810
adopting and daily driving. NeoVim, Vim, whatever,

01:10:38.069 --> 01:10:42.210
something like that. Oh, yeah, yeah. So I think

01:10:42.210 --> 01:10:45.130
NeoVim, a lot of options, a lot of tutorials

01:10:45.130 --> 01:10:48.770
out there. Yes. So you have to make the decision

01:10:48.770 --> 01:10:52.210
first. Do I build my own config? I try to learn

01:10:52.210 --> 01:10:55.829
Vim motions while I build my config, while I

01:10:55.829 --> 01:10:58.350
learn Lua, while I learn about plugins, while

01:10:58.350 --> 01:11:01.789
I learn about the NeoVim documentation, or...

01:11:02.090 --> 01:11:05.590
Should I use distribution, read the documentation,

01:11:06.029 --> 01:11:09.609
don't understand anything about NeoVim, or should

01:11:09.609 --> 01:11:15.810
I do something like kickstart .envim? Or use

01:11:15.810 --> 01:11:20.770
Minimax, which is also a thing. Okay, that's

01:11:20.770 --> 01:11:24.510
an option. Let's take a look at that. Why don't

01:11:24.510 --> 01:11:28.270
you let us know first, what do you think about

01:11:28.270 --> 01:11:31.409
distros? Is this a distro? What do you recommend

01:11:31.409 --> 01:11:34.510
to someone just starting out with Neovim? Like,

01:11:34.569 --> 01:11:37.909
I'm new. I don't know about Vim Motions, but

01:11:37.909 --> 01:11:40.710
I see what these YouTubers do. The magic they

01:11:40.710 --> 01:11:43.550
do when they switch between files, copy, paste,

01:11:43.750 --> 01:11:46.989
you know, and, you know, select text inside quotes

01:11:46.989 --> 01:11:49.649
and all that stuff. Yeah, yeah, yeah. But I know

01:11:49.649 --> 01:11:51.529
nothing. What do you recommend to someone like

01:11:51.529 --> 01:11:57.189
that? I would recommend what is recommended by

01:11:57.189 --> 01:12:02.710
Neovim docs already. There is a page that helps

01:12:02.710 --> 01:12:07.869
you what to do when you start. It used to be

01:12:07.869 --> 01:12:16.970
just in basic help, but what it does is suggests

01:12:16.970 --> 01:12:24.050
some pages to read. Lua intro, there is a help

01:12:24.050 --> 01:12:27.579
tag, I think. Lua Neo Vim or something like that.

01:12:27.739 --> 01:12:36.260
But the main starting point is Vim Tutor. Yes.

01:12:36.760 --> 01:12:39.739
I think I also started with that. I'm not sure.

01:12:39.880 --> 01:12:46.380
Maybe. It should be a good starting point for

01:12:46.380 --> 01:12:51.020
people that don't know anything about Vim motions,

01:12:51.420 --> 01:12:56.220
how Vim works, modes. because model editing is

01:12:56.220 --> 01:13:01.539
indeed not a very intuitive concept for people

01:13:01.539 --> 01:13:10.140
that come from Notepad++ or some other commonly

01:13:10.140 --> 01:13:14.680
used editors. I understand that. But the Vim

01:13:14.680 --> 01:13:17.560
Tutor is the place that most people recommend

01:13:17.560 --> 01:13:20.399
and which I think I also started with. But I

01:13:20.399 --> 01:13:22.260
honestly cannot remember. There is also this

01:13:22.260 --> 01:13:25.220
site, I think, Vim Adventures. Yep, the game.

01:13:25.380 --> 01:13:28.399
I used to play that with my daughter. Yeah, I

01:13:28.399 --> 01:13:31.899
think I also played it a couple of times. Not

01:13:31.899 --> 01:13:35.060
sure if it helped or if it was already after

01:13:35.060 --> 01:13:41.819
I mastered it. who was aware of how vim motions

01:13:41.819 --> 01:13:46.399
and vim works so bottom line start with vim tutor

01:13:46.399 --> 01:13:51.640
read one or two documentations that are present

01:13:51.640 --> 01:13:55.439
in neo vim itself maybe watch a couple of youtubers

01:13:55.439 --> 01:14:02.939
that you think are a reliable source of information

01:14:02.939 --> 01:14:08.850
probably watch the link arzu Oh, I've heard he's

01:14:08.850 --> 01:14:13.949
good. YouTube channel. He's okay, I think. The

01:14:13.949 --> 01:14:17.090
interviews are better, right? Interviews are

01:14:17.090 --> 01:14:21.390
much better, yes. Oh, man. Ben, what do you think

01:14:21.390 --> 01:14:24.029
about distros? Are you in favor of distros or

01:14:24.029 --> 01:14:27.069
against distros? They're fine. People can use

01:14:27.069 --> 01:14:32.590
them. It's just, how do I put it? I think half

01:14:32.590 --> 01:14:36.850
the fun of using new them is to make it your

01:14:36.850 --> 01:14:42.960
own. That's what most people say. Most people

01:14:42.960 --> 01:14:47.380
who have gone to troubles of actually configuring

01:14:47.380 --> 01:14:55.359
them, they might have told them, they might tell

01:14:55.359 --> 01:15:00.180
it to themselves that it is actually fun. But

01:15:00.180 --> 01:15:03.380
it is fun. For me personally, it is very fun

01:15:03.380 --> 01:15:10.409
to configure NeoVim. It is magic, basically,

01:15:10.550 --> 01:15:18.590
when you have nearly instant feedback of what

01:15:18.590 --> 01:15:23.010
you have. You typed some words, you restarted

01:15:23.010 --> 01:15:26.550
maybe new Vim, and it does the thing. It is magic.

01:15:27.750 --> 01:15:34.210
Very close to magic. And maybe it is close to

01:15:34.210 --> 01:15:40.729
a... Well, not close. It is an instant endorphin

01:15:40.729 --> 01:15:45.210
rush, maybe, when you see something working.

01:15:45.449 --> 01:15:50.090
When you install a new plugin and you can now

01:15:50.090 --> 01:15:55.670
navigate files. Or install a new plugin. It works,

01:15:55.850 --> 01:15:59.869
yes, right away. And you install a new plugin

01:15:59.869 --> 01:16:02.729
and you have auto -completions in command line,

01:16:02.850 --> 01:16:08.479
for example. That's awesome. Something, I like

01:16:08.479 --> 01:16:15.439
that. People, usually, people who end up liking

01:16:15.439 --> 01:16:20.399
to use NeoVim are people who like this kind of

01:16:20.399 --> 01:16:25.899
activity, I think. Distros are a great starting

01:16:25.899 --> 01:16:32.520
point, that's for sure, because it limits the

01:16:32.520 --> 01:16:39.319
decision. decisions for new people. But they

01:16:39.319 --> 01:16:43.659
tend to be a bit overly complicated. That's my

01:16:43.659 --> 01:16:48.380
opinion. Both, well, not both. They look fantastic.

01:16:48.600 --> 01:16:54.020
They work and feel great. LazyVim, EnvyChad,

01:16:54.260 --> 01:16:59.300
Asteroid and Vim. In the early days, LunarVim.

01:16:59.439 --> 01:17:02.399
Have you heard about LunarVim? Done, right? Or

01:17:02.399 --> 01:17:05.479
not? Well, It is there, but it's not maintained.

01:17:05.840 --> 01:17:12.699
What LunarVim did for me personally is that its

01:17:12.699 --> 01:17:18.140
creator, I remember the, no, I don't remember

01:17:18.140 --> 01:17:23.439
the actual name, but its creator created a series

01:17:23.439 --> 01:17:26.960
of YouTube videos about how to start with NeoVim.

01:17:27.060 --> 01:17:32.909
And I think that's what I used as my... primary

01:17:32.909 --> 01:17:38.250
source of Neovim introduction. It built Neovim

01:17:38.250 --> 01:17:42.670
from source, but in a way that resembled LunarVim,

01:17:42.810 --> 01:17:45.529
but did not actually use LunarVim. I think that

01:17:45.529 --> 01:17:52.390
was the idea. Oh, okay. So, short story, distros

01:17:52.390 --> 01:17:57.109
are a great start, but I honestly recommend building

01:17:57.109 --> 01:18:02.449
your own config. If you do not enjoy the process

01:18:02.449 --> 01:18:07.090
of building your own config maybe neo vim is

01:18:07.090 --> 01:18:10.529
not the right tool for maybe uh you can keep

01:18:10.529 --> 01:18:15.470
using uh distro that's okay no shame in there

01:18:15.470 --> 01:18:21.409
honestly i i do not joke here use it uh but most

01:18:21.409 --> 01:18:27.350
the fun usually is uh configuring okay yeah yeah

01:18:27.350 --> 01:18:31.100
i'm still on lazy vim and i'm like i should build

01:18:31.100 --> 01:18:33.859
my own config, you know, but then it's like,

01:18:33.960 --> 01:18:36.300
it's going to take me some time. And I'm like,

01:18:36.359 --> 01:18:39.739
I'm postponing that, you know, and I will record

01:18:39.739 --> 01:18:43.100
videos when I finally decide to, but yeah, LazyVim

01:18:43.100 --> 01:18:46.140
is not easy either. Cause you know, it's, it's

01:18:46.140 --> 01:18:49.579
quite complex and it has a lot of different stuff,

01:18:49.680 --> 01:18:52.539
but that is the way that I got to know a lot

01:18:52.539 --> 01:18:54.699
of different plugins that I love, like many of

01:18:54.699 --> 01:18:59.199
the files, you know, it's because. LazyVim, right?

01:18:59.359 --> 01:19:02.779
Or the mini that's around, I think it was, right?

01:19:02.960 --> 01:19:06.420
Yes. Because of LazyVim. There's a lot that are

01:19:06.420 --> 01:19:09.560
included in LazyVim, so it helps you get to know

01:19:09.560 --> 01:19:14.659
new stuff, I guess, but yeah. Yes, but I think

01:19:14.659 --> 01:19:22.359
that kickstart .nvim is a better approach at

01:19:24.880 --> 01:19:30.020
educating educating your users how to actually

01:19:30.020 --> 01:19:36.279
use and build so it it teaches you to fish instead

01:19:36.279 --> 01:19:40.880
of giving you the fish makes sense okay that

01:19:40.880 --> 01:19:45.560
makes sense okay that's why uh minimax which

01:19:45.560 --> 01:19:50.880
is uh config examples that are based on minute

01:19:50.880 --> 01:19:55.210
and vim take the similar approach It is not a

01:19:55.210 --> 01:19:59.729
distro. It is basically a NeoVim with Maximum

01:19:59.729 --> 01:20:05.010
Mini. That's the tagline. What you do is copy

01:20:05.010 --> 01:20:10.090
these three commands. First one will download,

01:20:10.590 --> 01:20:14.970
well, in this case, git clone the project itself.

01:20:15.350 --> 01:20:20.069
The second one will set up your config. With

01:20:20.069 --> 01:20:23.010
this command, it will set up in a special...

01:20:23.550 --> 01:20:25.930
separate config, not your full -time config,

01:20:26.090 --> 01:20:29.510
which is explained in the documentation. And

01:20:29.510 --> 01:20:32.890
the third one will start it right away. So you

01:20:32.890 --> 01:20:36.569
copy -paste, you hit enter, and you wait. It

01:20:36.569 --> 01:20:41.850
already started it the first time, and it currently

01:20:41.850 --> 01:20:46.250
installs all necessary plugins that are used

01:20:46.250 --> 01:20:51.880
in this config example. This config is currently

01:20:51.880 --> 01:20:56.739
set up for NeoVim 0 .11. That's it. It's already

01:20:56.739 --> 01:21:02.340
finished. You can document it in the example,

01:21:02.619 --> 01:21:05.939
in the code that you copy -pasted. You press

01:21:05.939 --> 01:21:10.340
space, which adds a leader key, E for explore,

01:21:10.699 --> 01:21:14.699
I for init law, and you start reading. Okay.

01:21:14.960 --> 01:21:21.159
It describes what it is. its structure, how it

01:21:21.159 --> 01:21:27.859
is organized, and so on. Hold on. I have a question

01:21:27.859 --> 01:21:31.500
for you. Is this designed for people that are

01:21:31.500 --> 01:21:34.399
just starting, or is this for an intermediate

01:21:34.399 --> 01:21:38.340
user? Here are the prerequisites. Here's what

01:21:38.340 --> 01:21:44.659
you need to understand. And I do understand that

01:21:44.659 --> 01:21:48.430
it is not quite for... very, very new users.

01:21:49.130 --> 01:21:53.670
It is probably not for that. You probably need

01:21:53.670 --> 01:21:59.050
to have understanding about some stuff, at least

01:21:59.050 --> 01:22:02.689
some stuff. So if you finished Vim Tutor and

01:22:02.689 --> 01:22:08.229
read links that are present here, they are here

01:22:08.229 --> 01:22:12.710
for a reason, then you could probably start using

01:22:12.710 --> 01:22:17.579
it. So not for... the person who woke up and

01:22:17.579 --> 01:22:20.960
decided, I want to use NeoVim, probably not for

01:22:20.960 --> 01:22:24.500
them, for those people. But if you have already

01:22:24.500 --> 01:22:27.119
an idea of Vim motions and you can navigate your

01:22:27.119 --> 01:22:33.119
way around NeoVim... Well, not necessarily...

01:22:33.119 --> 01:22:36.279
Well, navigate, yes. H, J, K, L, you know that

01:22:36.279 --> 01:22:40.880
those are arrows. You know how to start NeoVim

01:22:40.880 --> 01:22:46.350
from your command line. And you know the basics

01:22:46.350 --> 01:22:51.029
of Lua language. That's what is variables, what

01:22:51.029 --> 01:22:54.590
are files, and so on. That basically should be

01:22:54.590 --> 01:22:57.510
enough, I think. Okay. And someone like me that

01:22:57.510 --> 01:22:59.989
uses LazyVim as a daily driver, would it make

01:22:59.989 --> 01:23:05.390
sense to try Minimax? Of course. Of course. Would

01:23:05.390 --> 01:23:08.329
it help me to build my own config? Is that what

01:23:08.329 --> 01:23:13.069
it... What you are looking at, this init .lua,

01:23:13.189 --> 01:23:17.770
this is already your config. There is nothing

01:23:17.770 --> 01:23:25.210
else to it. It is not an extra layer of abstractions

01:23:25.210 --> 01:23:30.210
around your config, which is basically what a

01:23:30.210 --> 01:23:37.489
distribution is, is an extra abstraction on top

01:23:37.489 --> 01:23:42.930
of... plugins and new in itself but this is no

01:23:42.930 --> 01:23:48.729
this this this already uh or am i pointing to

01:23:48.729 --> 01:23:52.170
right direction this yep oh no the other side

01:23:52.170 --> 01:23:57.390
the other side this this is already uh a your

01:23:57.390 --> 01:24:00.670
company okay uh you can you can modify it you

01:24:00.670 --> 01:24:05.260
can do whatever you want with it It is in a separate

01:24:05.260 --> 01:24:09.699
directory. As you can see, it is not .config

01:24:09.699 --> 01:24:14.000
slash nvim. It is .config slash nvim -minimax.

01:24:14.180 --> 01:24:19.579
It is completely separate from what you will

01:24:19.579 --> 01:24:22.880
use as your daily driver or as your current driver.

01:24:23.020 --> 01:24:26.000
You can basically copy -paste those three lines

01:24:26.000 --> 01:24:30.060
right now, and it will create this for you. If

01:24:30.060 --> 01:24:36.039
you use LazyVim or any other, or if you have

01:24:36.039 --> 01:24:40.180
a config on your computer, this will create a

01:24:40.180 --> 01:24:44.479
separate config, which you can play with. So

01:24:44.479 --> 01:24:49.239
yeah, it is a config mostly based on mini .envim.

01:24:49.720 --> 01:24:54.439
And its configuration is split into four files.

01:24:54.560 --> 01:25:00.420
One for options. which describes some basic stuff

01:25:00.420 --> 01:25:05.779
about how to read this text and then sets every

01:25:05.779 --> 01:25:11.239
necessary option in the way which I used it for

01:25:11.239 --> 01:25:14.680
several years. This is mostly a copy -paste from

01:25:14.680 --> 01:25:19.659
my config and maybe a little bit toned down for

01:25:19.659 --> 01:25:24.039
people that don't like some stuff like folds,

01:25:24.140 --> 01:25:28.239
etc. It contains explanation. Of every line,

01:25:28.380 --> 01:25:33.000
what's every option. Yes, what every option does,

01:25:33.319 --> 01:25:38.739
what every value is trying to achieve, and so

01:25:38.739 --> 01:25:42.439
on. It also sets up diagnostic for you. And what

01:25:42.439 --> 01:25:46.000
about LSP? We'll get to that a bit later. Okay.

01:25:46.619 --> 01:25:52.840
The second file is for mappings, which basically

01:25:52.840 --> 01:25:58.010
creates all leader mappings. like this which

01:25:58.010 --> 01:26:02.149
are in the bottom right it is mini .clue which

01:26:02.149 --> 01:26:05.390
is similar to you probably have which key yes

01:26:05.390 --> 01:26:10.810
yep which key yes this is a similar tool for

01:26:10.810 --> 01:26:16.989
showing clues mini .clue okay show clues about

01:26:16.989 --> 01:26:22.210
what are you typing right now so this file creates

01:26:22.210 --> 01:26:26.210
all the leader mappings Like for fun. Let me

01:26:26.210 --> 01:26:27.829
ask you something, just obviously before you

01:26:27.829 --> 01:26:31.329
continue. Why did you take the decision of saying,

01:26:31.369 --> 01:26:33.569
okay, I'm not going to create many that clues.

01:26:33.750 --> 01:26:37.289
I'm going to use, what did we say right now?

01:26:37.649 --> 01:26:40.270
Witchkey. Witchkey, yeah. Why did you say like,

01:26:40.350 --> 01:26:42.250
okay, no, you know what? I don't want witchkey.

01:26:42.369 --> 01:26:44.470
I don't want anything to do with it. I don't

01:26:44.470 --> 01:26:46.909
like folky. So I'm going to create many that

01:26:46.909 --> 01:26:51.609
clues. Don't put those words into my mouth. I

01:26:51.609 --> 01:26:58.210
did not say that I don't like Falky. There will

01:26:58.210 --> 01:27:02.069
be a Reddit thread tomorrow that you, Chesnovsky,

01:27:02.130 --> 01:27:04.350
don't like Falky. Don't do that to me, please.

01:27:04.689 --> 01:27:08.229
Yeah, for sure. So next time we will have a Chesnovsky

01:27:08.229 --> 01:27:14.039
and Falky in a call. Hopefully. If you can manage

01:27:14.039 --> 01:27:18.119
to find Falky when he's not on vacation, which

01:27:18.119 --> 01:27:21.479
is very rare. Oh, so you're hanging. He's mostly

01:27:21.479 --> 01:27:26.220
on vacation. Okay, yeah. To answer your question

01:27:26.220 --> 01:27:30.000
a bit more seriously, I already answered it.

01:27:30.119 --> 01:27:36.699
I want to own my config. I find it fun to create

01:27:36.699 --> 01:27:42.539
stuff for Neovim, and I find it... fun to own

01:27:42.539 --> 01:27:50.899
what I use. And I have time and knowledge to

01:27:50.899 --> 01:27:55.359
do that. So specifically about which key, what

01:27:55.359 --> 01:27:59.659
was it? I think it was that I didn't really like

01:27:59.659 --> 01:28:04.880
some design decisions about complexity of how

01:28:04.880 --> 01:28:09.119
it is supposed to be used. I don't quite remember.

01:28:09.760 --> 01:28:12.600
There is a comparison here. They are basically

01:28:12.600 --> 01:28:18.859
similar, but main UI of which key at the time

01:28:18.859 --> 01:28:25.560
was like bottom bar, which I didn't like. Also,

01:28:25.840 --> 01:28:31.340
semi -funny story here that, well, not okay.

01:28:31.659 --> 01:28:36.100
I tried with every new module, I tried to create

01:28:36.100 --> 01:28:41.989
something new. because just copy -pasting functionality

01:28:41.989 --> 01:28:45.729
and design of other plugins is not fun. Provide

01:28:45.729 --> 01:28:50.029
something new for the community, be it different

01:28:50.029 --> 01:28:56.409
configuration defaults or usually lately a different

01:28:56.409 --> 01:28:59.149
functionality. With this one, I came up with

01:28:59.149 --> 01:29:04.810
the idea of showing this clue window to the side.

01:29:04.989 --> 01:29:08.979
They are not below. but on the right side where

01:29:08.979 --> 01:29:13.960
you usually don't have text. And who created

01:29:13.960 --> 01:29:16.680
this idea? Because I think Helix has this as

01:29:16.680 --> 01:29:19.060
well. Did they copy you or did you copy them?

01:29:19.560 --> 01:29:23.880
That is a funny story. I swear. I genuinely swear.

01:29:24.100 --> 01:29:30.079
I did not know that Helix had this UI. Genuinely.

01:29:30.539 --> 01:29:33.859
I thought about this idea, the floating window

01:29:33.859 --> 01:29:37.000
in the bottom right corner. That's great. That's

01:29:37.000 --> 01:29:40.520
a great idea. Let's do this. And I did. And I

01:29:40.520 --> 01:29:45.279
think maybe several months afterwards or when

01:29:45.279 --> 01:29:51.319
I released on Reddit post that described that,

01:29:51.380 --> 01:29:56.779
oh, that's how Helix does it. So I wait. I opened

01:29:56.779 --> 01:30:02.500
Helix. Yes, yes. It is how it does it. Well,

01:30:02.600 --> 01:30:10.119
okay. Maybe, maybe. I saw it previously. Forgot.

01:30:10.479 --> 01:30:14.159
And then one morning I thought, whoa, that's

01:30:14.159 --> 01:30:18.720
a great novel idea. Maybe. Could be. I cannot

01:30:18.720 --> 01:30:24.239
confirm nor deny that. But honestly... I thought

01:30:24.239 --> 01:30:27.840
that this was a novel idea. Witchkey has that

01:30:27.840 --> 01:30:31.020
layout now, and it's the default now, on the

01:30:31.020 --> 01:30:36.119
right. Yes, but it came after Miniclue did this,

01:30:36.239 --> 01:30:40.300
and of course Helix. Okay, okay. So it was a

01:30:40.300 --> 01:30:44.880
Witchkey version 3 rewrite about a year ago,

01:30:44.960 --> 01:30:50.300
I think. Year, year and a half. So, let's go

01:30:50.300 --> 01:30:54.159
back to Minimix. Yep, let's go back there. so

01:30:54.159 --> 01:30:58.920
the second file is for creating key maps which

01:30:58.920 --> 01:31:05.399
are mostly leader keys oh one more thing about

01:31:05.399 --> 01:31:10.979
miniclue is that the different idea behind it

01:31:10.979 --> 01:31:16.159
is it is it is implemented significantly different

01:31:16.159 --> 01:31:19.539
i remembered which key does this weird thing

01:31:19.539 --> 01:31:23.439
at least in version tool version one when it

01:31:23.439 --> 01:31:30.000
was around it creates some special mapping to

01:31:30.000 --> 01:31:35.579
some weird character to act as a trigger i think

01:31:35.579 --> 01:31:40.819
it was so unnerving for me to see when i explored

01:31:40.819 --> 01:31:44.939
all the mappings it is very technical very technical

01:31:44.939 --> 01:31:48.640
very niche reason to do this but but i really

01:31:48.640 --> 01:31:52.930
did not like it I can later maybe search in the

01:31:52.930 --> 01:31:57.489
issues or whatever, I don't quite remember. But

01:31:57.489 --> 01:32:01.949
I did not like it. So I decided to create my

01:32:01.949 --> 01:32:10.409
own implementation of how these clues are shown.

01:32:10.710 --> 01:32:15.909
What you see right now is you press space and

01:32:15.909 --> 01:32:22.810
it is a own... key query process. So it is not

01:32:22.810 --> 01:32:29.789
how NeoVim interprets key presses. Without any

01:32:29.789 --> 01:32:38.649
clue, if you press space and wait for a second...

01:32:38.649 --> 01:32:42.109
Okay, that's what I configured and that was going

01:32:42.109 --> 01:32:45.130
to be my question because I did configure one

01:32:45.130 --> 01:32:48.100
second delay for... which key to show up, because

01:32:48.100 --> 01:32:50.760
I didn't like that I pressed space, and it showed

01:32:50.760 --> 01:32:54.520
up immediately. So you can configure that. Well,

01:32:54.939 --> 01:32:58.699
you can, yes, but it's not about that. Let me

01:32:58.699 --> 01:33:03.159
just do it like that. I see you use ghosty. Is

01:33:03.159 --> 01:33:06.720
that fear on missing out as well, like any of

01:33:06.720 --> 01:33:13.939
them? No, it's not. I'll get to that later. Let

01:33:13.939 --> 01:33:19.520
me just... Stop interrupting me, you say. No,

01:33:19.520 --> 01:33:23.720
no, no, not like that. So I have created one

01:33:23.720 --> 01:33:30.600
normal mode mapping, space L, okay? So if I press

01:33:30.600 --> 01:33:34.979
them in a quick succession, space L, it shows

01:33:34.979 --> 01:33:40.119
one, as it should. Space L. But if I press space,

01:33:41.470 --> 01:33:44.329
and wait for one second, and now press L, nothing

01:33:44.329 --> 01:33:47.569
happened. Space, you see it in the bottom right

01:33:47.569 --> 01:33:51.010
corner, the 20 sign, it's how space is interpreted.

01:33:51.229 --> 01:33:54.489
L, nothing happens. Space, L, happen. That's

01:33:54.489 --> 01:33:59.949
how NeoVim and Vim interprets key presses. There

01:33:59.949 --> 01:34:04.369
is an option timeout then, which is by default

01:34:04.369 --> 01:34:08.050
1 ,000 milliseconds, which is one second. It

01:34:08.050 --> 01:34:10.369
is time in milliseconds to wait for a mapped

01:34:10.369 --> 01:34:13.170
sequence to conclude. So if there is a delay

01:34:13.170 --> 01:34:15.810
more than timeout length between key presses,

01:34:16.449 --> 01:34:21.350
Veeam thinks that user stopped inputting the

01:34:21.350 --> 01:34:27.489
mapping and executes it as it is. But with the

01:34:27.489 --> 01:34:32.750
leader key in particular, I like to press leader

01:34:32.750 --> 01:34:37.270
and then maybe think a bit. like leader f and

01:34:37.270 --> 01:34:40.170
then oh which speaker i want to choose maybe

01:34:40.170 --> 01:34:44.210
it's that or maybe it's not and if i think more

01:34:44.210 --> 01:34:48.109
than one second it disappears and i have to press

01:34:48.109 --> 01:34:55.350
space africa but with mini clue it implements

01:34:55.350 --> 01:34:58.989
in its own key query process when after you press

01:34:58.989 --> 01:35:06.909
space mini clue takes over this interpretation

01:35:06.909 --> 01:35:13.170
of how the user presses keys. So you can space,

01:35:13.489 --> 01:35:21.590
F, backspace, B, and look at different mappings.

01:35:21.829 --> 01:35:28.630
This is a different approach at how MiniClue

01:35:28.630 --> 01:35:30.989
is different to WitchKey, because WitchKey relied,

01:35:31.229 --> 01:35:34.569
I think, a bit more about the built -in key query

01:35:34.569 --> 01:35:38.489
process at that time. Okay. Maybe a little bit

01:35:38.489 --> 01:35:43.710
more. Maybe when if Polky is on your interview,

01:35:44.050 --> 01:35:48.430
you can ask him that. I don't know. Okay. If

01:35:48.430 --> 01:35:50.729
he remembers that. I tried to get him already.

01:35:50.850 --> 01:35:53.409
I sent him a message on Twitter and I was just

01:35:53.409 --> 01:35:56.170
ignored. So I don't think that's going to happen.

01:35:56.489 --> 01:35:59.649
But I'll keep trying. He's on vacation. He is

01:35:59.649 --> 01:36:04.149
on vacation. Probably, yeah. So that's Mini Clue.

01:36:04.289 --> 01:36:08.670
It shows all leader mappings that are created

01:36:08.670 --> 01:36:18.569
in this file. The third row of four main configuration

01:36:18.569 --> 01:36:22.949
files is basically for mini configuration, which

01:36:22.949 --> 01:36:25.949
is the most important here because it covers

01:36:25.949 --> 01:36:30.949
most of the functionality. Basically, well, I

01:36:30.949 --> 01:36:34.329
don't know how... How deep I should go here to

01:36:34.329 --> 01:36:41.510
describe? It is basically a collection, mostly

01:36:41.510 --> 01:36:47.569
all mini .nv modules set up and described what

01:36:47.569 --> 01:36:51.829
they do and how to use them in a very, very,

01:36:51.869 --> 01:36:54.109
very concise manner. But this is a different

01:36:54.109 --> 01:36:58.289
file. This is the mini .lua file, right? Yes,

01:36:58.329 --> 01:37:03.350
it is a part of your configuration. Oh, but the

01:37:03.350 --> 01:37:07.909
plugins have their entire code in here? Or just

01:37:07.909 --> 01:37:11.210
a configuration, right? This is just to configure

01:37:11.210 --> 01:37:16.130
mini plugins, correct? Yes, which are installed

01:37:16.130 --> 01:37:25.130
using mini .debs. No, the mini .nvim are installed

01:37:25.130 --> 01:37:29.899
like this. it is bootstrapped via git clone which

01:37:29.899 --> 01:37:35.960
is a uh an only uh viable method of doing this

01:37:35.960 --> 01:37:41.520
on neo vim uh prior to 0 .12 which will have

01:37:41.520 --> 01:37:45.739
and already has a built -in plugin manager within

01:37:45.739 --> 01:37:50.420
pack okay now your config right this min max

01:37:50.420 --> 01:37:54.560
mini max config already yes min max or mini max

01:37:54.560 --> 01:38:00.689
well it's mini to the max mini max okay yeah

01:38:00.689 --> 01:38:04.989
it already has all of the mini plugins installed

01:38:04.989 --> 01:38:13.149
right yes it is uh uh in local share and and

01:38:13.149 --> 01:38:20.390
the mini max here that's where uh mini .nvm is

01:38:20.390 --> 01:38:25.229
installed Here are all the modules. Module here

01:38:25.229 --> 01:38:31.810
is basically a file that acts as a separate plugin.

01:38:32.050 --> 01:38:37.930
But it is a single file complete with its documentation.

01:38:38.609 --> 01:38:43.170
Here you can see that. This is actual file on

01:38:43.170 --> 01:38:47.229
your disk, which you can require. Require mini

01:38:47.229 --> 01:38:54.670
.ai. This is the result of sourcing this file,

01:38:54.989 --> 01:38:59.770
mini .ai .law. It contains all the documentation.

01:39:00.750 --> 01:39:04.890
You can compare it with this one. See the resemblance?

01:39:05.069 --> 01:39:09.329
It's the same text, basically. But this is a

01:39:09.329 --> 01:39:12.609
help file, which you can navigate as a help file.

01:39:14.029 --> 01:39:17.710
That's an internal... implementation detail in

01:39:17.710 --> 01:39:22.029
detail i've seen but it is here oh what if there's

01:39:22.029 --> 01:39:26.010
someone that is like okay i prefer to use that

01:39:26.010 --> 01:39:29.449
speaker instead of mini .pic what would that

01:39:29.449 --> 01:39:32.949
person do in that case is minimax not an option

01:39:32.949 --> 01:39:36.109
for them of course and it is an option totally

01:39:36.109 --> 01:39:39.250
an option if you they want to use a different

01:39:39.250 --> 01:39:42.609
picker different what what else notifications

01:39:42.609 --> 01:39:49.250
like in bim notify or what they want to use other

01:39:49.250 --> 01:39:52.869
okay maybe they want to use git signs instead

01:39:52.869 --> 01:39:57.409
of a minid all they had to do is to possibly

01:39:57.409 --> 01:40:03.189
if they want to be as clean and to have a config

01:40:03.189 --> 01:40:07.449
as clean as possible they have to disable minipig

01:40:07.449 --> 01:40:13.310
setting up a minipig go go to the to the force

01:40:14.239 --> 01:40:18.619
file, which is for external plugins. It has installed

01:40:18.619 --> 01:40:22.020
Nvim TreeSitter by default and set up TreeSitter.

01:40:22.159 --> 01:40:28.979
LSP config. I'll show how to enable and set up

01:40:28.979 --> 01:40:34.560
LSP. You asked that before, I think. And other

01:40:34.560 --> 01:40:38.140
plugins as well. So what they'd have to do here,

01:40:38.359 --> 01:40:46.220
I think, is to use this later function to lazy

01:40:46.220 --> 01:40:52.779
-load it, use snacks and vim, and I think how

01:40:52.779 --> 01:40:56.640
snacks picker is set up. Do you remember? Is

01:40:56.640 --> 01:41:01.420
it like, I think it is picker enabled true. I

01:41:01.420 --> 01:41:05.960
think it's like this. Then, I think it's like

01:41:05.960 --> 01:41:10.399
this. Then restart. It auto -installs snacks

01:41:10.399 --> 01:41:15.699
for them. That's installed. And I think how the

01:41:15.699 --> 01:41:20.180
Snacks speaker is Lua, Snacks, speaker, files.

01:41:20.500 --> 01:41:27.520
Here are the files. But it does it by default

01:41:27.520 --> 01:41:35.680
in this home directory. You can navigate to Minimax

01:41:35.680 --> 01:41:41.079
and start it from here. Lua, Max, speaker. Here

01:41:41.079 --> 01:41:44.880
are all the files from your config, for example.

01:41:45.159 --> 01:41:48.199
So it is possible. Of course, it is a config.

01:41:48.539 --> 01:41:54.279
It is a collection of files that live in a dedicated...

01:41:54.279 --> 01:41:59.659
I should adjust many hues, probably. Or snacks,

01:41:59.960 --> 01:42:05.640
because it is invisible. Interesting. So it is

01:42:05.640 --> 01:42:09.680
just a collection of files that live in a dedicated...

01:42:10.029 --> 01:42:14.909
directory and load it when new vim starts that's

01:42:14.909 --> 01:42:18.750
all what what's new in config is okay and i see

01:42:18.750 --> 01:42:20.930
that all of the external plugins you have them

01:42:20.930 --> 01:42:24.170
in a single file do you prefer yes yes that or

01:42:24.170 --> 01:42:27.189
have a directory and have all the plugins inside

01:42:27.189 --> 01:42:30.510
that directory the external ones like each file

01:42:30.510 --> 01:42:35.470
or plugin well this is the structure that i prefer

01:42:36.380 --> 01:42:40.420
One file for options, one file for keymaps or

01:42:40.420 --> 01:42:43.479
mappings, one file specifically for mini .envim,

01:42:43.579 --> 01:42:46.500
and one file specifically for external plugins.

01:42:46.760 --> 01:42:51.180
I don't think anything more is needed. If people

01:42:51.180 --> 01:42:56.319
prefer to structure it in a separate file per

01:42:56.319 --> 01:43:00.279
plugin, they, of course, can do that. They can

01:43:00.279 --> 01:43:04.699
create a new file, what do you want, which plugin

01:43:04.699 --> 01:43:08.100
should be installed. You can try. No, I don't

01:43:08.100 --> 01:43:13.260
even know what plugins they have installed. Qmk

01:43:13.260 --> 01:43:18.659
.lua for the keyboard. Qmk .lua. Okay, Qmk. What

01:43:18.659 --> 01:43:24.720
is... It's code thread. The repo is code thread.

01:43:24.960 --> 01:43:30.039
This? Yep. Slash Qmk .envim. Probably like this,

01:43:30.140 --> 01:43:34.640
yeah? Well, let's try. It is installed. How can

01:43:34.640 --> 01:43:40.000
I use it? I don't know. Probably... Of course

01:43:40.000 --> 01:43:44.939
it isn't. Does Snack have a picker for help?

01:43:45.359 --> 01:43:49.119
Yes. It is installed already. You can use it.

01:43:49.380 --> 01:43:53.140
Okay, that's good. That's good. Awesome. Let

01:43:53.140 --> 01:43:58.079
me please get back to MIDI pick because... It's

01:43:58.079 --> 01:44:03.140
difficult to navigate. Yes. At least it is not,

01:44:03.140 --> 01:44:08.180
how do I say it, not comfortable for me at the

01:44:08.180 --> 01:44:16.420
moment. Yep. All mappings use minipig. They all

01:44:16.420 --> 01:44:23.140
use pig command, not snacks. What about plugin

01:44:23.140 --> 01:44:28.520
manager? What do you use? Mini .deps. Yes. Okay.

01:44:28.970 --> 01:44:33.729
But it will soon probably be not deprecated,

01:44:33.750 --> 01:44:38.550
but superseded by Winpack. Okay, that was going

01:44:38.550 --> 01:44:40.470
to be my question. So you're not going to...

01:44:40.470 --> 01:44:44.770
Your main one will be to use the option that

01:44:44.770 --> 01:44:49.510
NeoWin provides, right? I want to be... How would

01:44:49.510 --> 01:44:57.140
I say it? Humble, please. Probably. i i i i sincerely

01:44:57.140 --> 01:45:03.180
cannot uh even be humble here because uh that's

01:45:03.180 --> 01:45:07.180
the truth uh okay impact is based on minute of

01:45:07.180 --> 01:45:15.279
depths oh uh it is uh i my pr into neo vim to

01:45:15.279 --> 01:45:20.439
create a built -in plugin manager okay and it

01:45:20.439 --> 01:45:24.770
is heavily inspired by mini taps this is a 0

01:45:24.770 --> 01:45:28.289
.12 right now. Yes, it will use instead of...

01:45:28.289 --> 01:45:35.250
You can see it has... This is how it installs

01:45:35.250 --> 01:45:42.149
and loads plugins. Just a single Winpack app

01:45:42.149 --> 01:45:47.630
call which contains a full link to a plugin and

01:45:47.630 --> 01:45:52.449
afterwards it can use required to configure and

01:45:52.449 --> 01:45:58.449
use it. cut to how minidevs does things it has

01:45:58.449 --> 01:46:03.430
single add function that installs and loads the

01:46:03.430 --> 01:46:07.050
plugin well with hooks but vimpak doesn't have

01:46:07.050 --> 01:46:10.270
it doesn't have them and afterwards it can be

01:46:10.270 --> 01:46:14.449
configured it can use installed plugin directly

01:46:14.449 --> 01:46:21.760
so yes uh this uh minimax uses mini .debs right

01:46:21.760 --> 01:46:27.439
now and it will use it mini .debs for neo vim

01:46:27.439 --> 01:46:32.920
version less than 0 .12 because minimax is not

01:46:32.920 --> 01:46:39.199
a single config we can show it minimax is a collection

01:46:39.199 --> 01:46:41.800
of configs which at the moment contains only

01:46:41.800 --> 01:46:45.260
a single config but it is designed as a collection

01:46:45.960 --> 01:46:51.659
It will automatically decide which config is

01:46:51.659 --> 01:46:55.819
the best for your current NuVim installation.

01:46:56.340 --> 01:47:01.000
And copy -paste, basically, copy -paste necessary

01:47:01.000 --> 01:47:06.479
files. Right now it copy -pastes only files from

01:47:06.479 --> 01:47:11.760
a single directory in vim -0 .11. But I should

01:47:11.760 --> 01:47:15.180
have done this sooner, probably before this interview.

01:47:15.869 --> 01:47:20.590
oh well there will be more configs like for example

01:47:20.590 --> 01:47:28.189
in vim dash 0 .12 will be most most likely resemble

01:47:28.189 --> 01:47:33.350
the config for 0 .11 but it will use vimpack

01:47:33.350 --> 01:47:40.529
for sure okay and it will have certain options

01:47:40.529 --> 01:47:44.029
enabled that are present only on neo vim 0 .12

01:47:44.029 --> 01:47:50.640
okay The current plan is to have Minimax evolve

01:47:50.640 --> 01:47:56.159
along with the NeoVim versions and have each

01:47:56.159 --> 01:48:00.460
separate NeoVim version its own config for stability.

01:48:00.979 --> 01:48:09.359
So if people for some reason need to use earlier

01:48:09.359 --> 01:48:13.600
versions of NeoVim, they will be able to do that.

01:48:14.010 --> 01:48:17.729
well starting from probably a 0 .9 version oh

01:48:17.729 --> 01:48:22.550
so should i wait till neovim 0 .12 to try minimax

01:48:22.550 --> 01:48:25.989
then so that i don't have to so if i go with

01:48:25.989 --> 01:48:29.649
0 .11 right now when neovim 0 .12 comes out i

01:48:29.649 --> 01:48:32.029
would probably have to upgrade minimax right

01:48:32.029 --> 01:48:36.470
you uh you do not upgrade minimax you upgrade

01:48:36.470 --> 01:48:40.449
your own config that's that's uh after you you

01:48:40.449 --> 01:48:43.750
will set up minimax you will have your config,

01:48:43.930 --> 01:48:49.750
and it will be tailored for NeoVim 0 .11. Okay.

01:48:50.109 --> 01:48:55.409
You can already use, I think, NeoVim 0 .12. It

01:48:55.409 --> 01:49:01.069
is more or less stable with occasional issues.

01:49:01.270 --> 01:49:05.729
If some problematic PR is merged, there might

01:49:05.729 --> 01:49:09.010
be some issues, but it is fairly rare, I would

01:49:09.010 --> 01:49:13.800
say. So I, for example, already mostly daily

01:49:13.800 --> 01:49:20.800
driving 0 .12 with the difference that I need

01:49:20.800 --> 01:49:29.560
to have all versions installed that mini .nvim

01:49:29.560 --> 01:49:35.800
is set to support. At the moment it is 0 .9,

01:49:35.859 --> 01:49:40.819
0 .10, 0 .11 and lately 0 .12. So Minit .envim

01:49:40.819 --> 01:49:49.579
has a very strict and wide policy for supported

01:49:49.579 --> 01:49:52.640
newly versions, I would say. It's fairly rare.

01:49:52.819 --> 01:50:00.039
It is one of the prides for me to be able to

01:50:00.039 --> 01:50:03.199
say that Minit .envim does that. Okay, so if

01:50:03.199 --> 01:50:05.680
you're on Mini that and Vim and if you installed

01:50:05.680 --> 01:50:08.359
it when it was in 0 .11 and you want to upgrade

01:50:08.359 --> 01:50:11.300
to Vim pack, I guess you will have documentation

01:50:11.300 --> 01:50:16.020
in your site? Yes, of course. Mini Macs will

01:50:16.020 --> 01:50:21.020
have somewhere probably on this page. There will

01:50:21.020 --> 01:50:27.199
be not only links to the config themselves. You

01:50:27.199 --> 01:50:31.180
can watch, you can read story. You can read the

01:50:31.180 --> 01:50:35.479
whole config on the site. You can just read it.

01:50:35.539 --> 01:50:42.140
You can consult it if you want to decide if it

01:50:42.140 --> 01:50:44.619
is for you or not. You don't have to even install

01:50:44.619 --> 01:50:48.319
it. You can read it here. So the idea is that

01:50:48.319 --> 01:50:58.100
alongside actual configs, there will be a difference.

01:50:58.859 --> 01:51:04.000
between, for example, NenVim 0 .11 and NenVim

01:51:04.000 --> 01:51:09.960
0 .12. So it will show what have changed in regards

01:51:09.960 --> 01:51:16.199
of Minimax config. For 0 .11 to 0 .12, it will

01:51:16.199 --> 01:51:21.760
be a bit too much because of the transition to

01:51:21.760 --> 01:51:28.109
Vimpack. I've already done that recently. It

01:51:28.109 --> 01:51:34.250
will not be a huge issue, but it will be somewhat

01:51:34.250 --> 01:51:37.649
of a big change. If you want to try Minimax,

01:51:37.829 --> 01:51:41.010
I would encourage you to try it right now because

01:51:41.010 --> 01:51:43.430
it is already too late. You should have done

01:51:43.430 --> 01:51:49.409
this yesterday, I think. But if you want to wait

01:51:49.409 --> 01:51:56.789
0 .12, it is one of my next items on my to -do

01:51:56.789 --> 01:52:01.489
list. is to actually do nvim 0 .12 first i think

01:52:01.489 --> 01:52:09.289
i will finalize the vimpak before the 0 .12 release

01:52:09.289 --> 01:52:13.689
because it is still a little no it is it works

01:52:13.689 --> 01:52:17.329
but there are some things that i wanted to have

01:52:17.329 --> 01:52:21.550
before 0 .12 release like do you know what check

01:52:21.550 --> 01:52:25.729
health is yep yep or the impact currently does

01:52:25.729 --> 01:52:29.329
not have it But I think it should. The reason

01:52:29.329 --> 01:52:32.810
why it doesn't have it is because it shouldn't

01:52:32.810 --> 01:52:37.609
need it. Because it's perfect, right? Yes, yes,

01:52:37.750 --> 01:52:42.710
yes. Okay. It should just work, ideally. Ideally,

01:52:42.789 --> 01:52:46.130
if you follow the documentation, if you just

01:52:46.130 --> 01:52:52.550
add vimpac .add to your init .tool file, it will

01:52:52.550 --> 01:52:57.329
just work. Okay. This is a fresh config. Something

01:52:57.329 --> 01:53:04.609
that we will see with NeoVim 0 .12. If you are

01:53:04.609 --> 01:53:08.090
on a brand new machine, you should create init

01:53:08.090 --> 01:53:12.670
.lua file. You should add one line of Winpack

01:53:12.670 --> 01:53:16.710
add. Restart. It asks you to install the plugin.

01:53:17.010 --> 01:53:20.949
You should wait some time depending on your internet

01:53:20.949 --> 01:53:24.409
connection. It finished installation. And it

01:53:24.409 --> 01:53:31.229
can already be used. This is the color scheme

01:53:31.229 --> 01:53:34.430
from MediaNP. It is already present on your disk.

01:53:35.689 --> 01:53:42.029
Here you can do something like... And it should

01:53:42.029 --> 01:53:46.989
already be surround -enabled. You can change

01:53:46.989 --> 01:53:53.729
quotes, you can delete quotes, etc. So basically

01:53:53.729 --> 01:53:58.130
one line is all you need to install a plugin.

01:53:58.609 --> 01:54:03.930
That's all. And afterwards you can use it. This

01:54:03.930 --> 01:54:09.270
is not much different from what currently is

01:54:09.270 --> 01:54:15.909
being done for 0 .11 and Minimax. But there will

01:54:15.909 --> 01:54:18.510
be some differences between 0 .11 and 0 .12.

01:54:18.890 --> 01:54:22.930
Oh, I think. okay okay now do you use any other

01:54:22.930 --> 01:54:27.789
plugins besides mini plugins or just your plugins

01:54:27.789 --> 01:54:35.149
uh this is my uh my file for the for my external

01:54:35.149 --> 01:54:40.310
plugins okay is mostly the same that is in shown

01:54:40.310 --> 01:54:46.630
in minimax but i have a vim script drama a vim

01:54:46.630 --> 01:54:50.630
script plugin for uh managing built -in terminal

01:54:50.630 --> 01:54:59.649
so like that yeah that opens a split window with

01:54:59.649 --> 01:55:02.989
the built -in terminal i use it all the time

01:55:02.989 --> 01:55:08.630
and besides minimax what is listed in minimax

01:55:08.630 --> 01:55:12.789
i have some plugins for running tests which i

01:55:12.789 --> 01:55:16.310
haven't used in a really really long time because

01:55:16.310 --> 01:55:24.229
all i do now is is use mini .test for testing

01:55:24.229 --> 01:55:30.909
mini and Vim. There are some file type for CSV

01:55:30.909 --> 01:55:34.930
and Markdown. Markdown preview. It's Markdown

01:55:34.930 --> 01:55:38.430
preview plugin, yes. And that's it. That's all

01:55:38.430 --> 01:55:42.289
I use. Everything else is mini. Okay, awesome.