Age | Commit message (Collapse) | Author |
|
|
|
This could probably be stored in git, but I'm going to exclude it for
now
|
|
I hope to get this working well enough where I can run tests from within
neovim
|
|
Order them first too
|
|
Fun thing make text go brrrt
|
|
|
|
|
|
This seems fixed now
|
|
This seemed to have a pretty good performance increase
|
|
|
|
- Tab manipulation
- Zen mode
- Force kill buffer (quit without writing)
|
|
|
|
|
|
The old plugin was causing issues with treesitter and tsx files. Syntax
highlighting wouldn't work by default, so you had to turn it on for
every tsx buffer.
This seems to have fixed it.
|
|
I always remember this after I've already broken it lol
|
|
This is a plugin that adds icons in certain areas
|
|
This plugin shows indentation guides as well as whitespace. I'm not
crazy about this setup currently, but it's kinda nice.
|
|
Startify is actually really cool. I wasn't sold on like project
management with vim until I saw how easy it was with startify and now I
love it.
|
|
SPC-v-c opens a calendar so you can easily open a vimwiki diary entry
for the selected day.
There's also a way to search through calendar entries, so I might add
something for that.
|
|
|
|
|
|
A lot of this stuff is handled by an lsp, but this has some niceness
about it.
|
|
|
|
I need to store the actual script somewhere. Maybe in a git gist.
|
|
|
|
|
|
|
|
|
|
While using airline, it shows your mode at the bottom anyway. So there's
no need for it twice.
|
|
|
|
|
|
These schemes are cool. I am using gruvbox right now because it matches
my wallpaper best.
But Ayu is amazing, I think it's my favorite one I've tried.
The TempleOS one was a test. I installed the TempleOS font and color
scheme and wanted to see if I could try using it (I cold not), but I'm
not the greatest programmer who ever lived.
|
|
|
|
LSP has some formatters that you can use and run, this command was just
written wrong.
|
|
Allows you to close a buffer without losing your window placement
(splits)
|
|
|
|
This was overdue. Vimwiki is nice, but Markdown I think leaves me open
for more options, and markdown has an LSP I can use.
|
|
I finally understand more about LSP and think I have a good setup now.
The biggest changes are the order of the autocomplete stuff. This helps
with the lag issues(I hope).
I also ensure that a few language servers are installed, because those
are the languages I use most. I will probably add more soon (SQL).
|
|
|
|
Writing markdown became unbearable because anytime I typed "ti", or "th"
it would slow down and freeze for a few seconds. It was really
aggravating. This is what I thought was causing that issue to start
with. This is an area of neovim I really should research more, because
it's a lot more complicated than I thought.
|
|
This is a real help because I like keeping 2 separte wikis for work and
personal
|
|
o for ":only" makes more sense to me than "quit".
|
|
If anything that pertains to how vim functions or operates, I think i'd
like it to go here. Very nice.
|
|
gcc makes more sense to me to make a new commit, where gca is amend.
|
|
I mostly do this in the command line, but it's cool in vim too.
|
|
Right now I mostly use :Git and then do it that way instead of using the
keymaps. But either way is cool.
|
|
|
|
This is a workaround so that way vim-css-color will work. The plugin
vim-css-color would not display the colors over their respective color
codes, which being able to see the colors is helpful especially in CSS.
I don't write enough CSS to try to figure out how to get the 2 to work
together, so disabling treesitter for css is easiest right now.
|
|
I mostly end up using the actual commands for these, but having them in
keybinds is nice.
|
|
Originally I had my personal one inside of my work one. And I store my
work one on our work servers, so I had to ignore my personal one and use
a separate git repo inside of it. It was not elegant. Now I just have 2
separate ones and commit and use them each as I please.
|