chore: clean up unused assets

This commit is contained in:
raf 2023-07-16 13:15:32 +03:00
parent c4ae0b140f
commit eaab87d151
No known key found for this signature in database
GPG key ID: 02D1DD3FA08B6B29
5 changed files with 7 additions and 18 deletions

25
.github/README.md vendored
View file

@ -1,5 +1,7 @@
<img align="center" src="../assets/neovim-flake-logo-work.svg" alt="Logo" width="200"> <div align="center">
<h1 align="center">neovim-flake</h1> <img src="../assets/neovim-flake-logo-work.svg" alt="Logo" width="200">
</div>
<h1 align="center">❄️ neovim-flake</h1>
<div align="center"> <div align="center">
<p> <p>
<a href="https://github.com/NotAShelf/neovim-flake/releases/latest"> <a href="https://github.com/NotAShelf/neovim-flake/releases/latest">
@ -61,7 +63,7 @@
## Get Started ## Get Started
### Using `nix` ### Using `nix` CLI
If you would like to try out the configuration before even thinking about installing it, you can run: If you would like to try out the configuration before even thinking about installing it, you can run:
@ -104,17 +106,8 @@ I am always looking for new ways to help improve this flake. If you would like t
## Philosophy ## Philosophy
The philosophy behind this flake configuration is to create an easily configurable and reproducible Neovim environment. While it does sacrifice in size The philosophy behind this flake configuration is to create an easily configurable and reproducible Neovim environment. While it does sacrifice in size
<<<<<<< HEAD
(which I know some users will find _disagreeable_), it offers a lot of flexibility and customizability in exchange for the large size of the flake inputs. (which I know some users will find _disagreeable_), it offers a lot of flexibility and customizability in exchange for the large size of the flake inputs.
The KISS (Keep it simple, stupid) principle has been abandoned here, however, you _can_ ultimately leverage the flexibility of this flake to declare a configuration that follows KISS principles, it is very easy to bring your own plugins and configurations from non-nix. What this flake is meant to be does eventually fall into your hands. Whether you are a developer, writer, or live coder, you can quickly craft a config that suits every project's need. Think of it like a distribution of Neovim that takes advantage of pinning vim plugins and The KISS (Keep it simple, stupid) principle has been abandoned here, however, you _can_ ultimately leverage the flexibility of this flake to declare a configuration that follows KISS principles, it is very easy to bring your own plugins and configurations from non-nix. What this flake is meant to be does eventually fall into your hands. Whether you are a developer, writer, or live coder, you can quickly craft a config that suits every project's need. Think of it like a distributionof Neovim that takes advantage of pinning vim plugins and third party dependencies (such as tree-sitter grammars, language servers, and more).
||||||| parent of d03998c (docs: use new neovim-flake logo)
(which I know some users will find *disagreeable*), it offers a lot of flexibility and customizability in exchange for the large size of the flake inputs.
The KISS (Keep it simple, stupid) principle has been abandoned here, however, you *can* ultimately leverage the flexibility of this flake to declare a configuration that follows KISS principles, it is very easy to bring your own plugins and configurations from non-nix. What this flake is meant to be does eventually fall into your hands. Whether you are a developer, writer, or live coder (see tidal cycles below!), you can quickly craft a config that suits every project's need. Think of it like a distribution of Neovim that takes advantage of pinning vim plugins and
=======
(which I know some users will find _disagreeable_), it offers a lot of flexibility and customizability in exchange for the large size of the flake inputs.
The KISS (Keep it simple, stupid) principle has been abandoned here, however, you _can_ ultimately leverage the flexibility of this flake to declare a configuration that follows KISS principles, it is very easy to bring your own plugins and configurations from non-nix. What this flake is meant to be does eventually fall into your hands. Whether you are a developer, writer, or live coder (see tidal cycles below!), you can quickly craft a config that suits every project's need. Think of it like a distribution of Neovim that takes advantage of pinning vim plugins and
>>>>>>> d03998c (docs: use new neovim-flake logo)
third party dependencies (such as tree-sitter grammars, language servers, and more).
One should never get a broken config when setting options. If setting multiple options results in a broken Neovim, file an issue! Each plugin knows when another plugin which allows for smart configuration of keybindings and automatic setup of things like completion sources and languages. One should never get a broken config when setting options. If setting multiple options results in a broken Neovim, file an issue! Each plugin knows when another plugin which allows for smart configuration of keybindings and automatic setup of things like completion sources and languages.
@ -148,15 +141,11 @@ instead of the `maximal` output. This will reduce size by a lot, but you will lo
Special thanks to Special thanks to
- [@fufexan](https://github.com/fufexan) - For the transition to flake-parts - [@fufexan](https://github.com/fufexan) - For the transition to flake-parts
<<<<<<< HEAD
- [@FlafyDev](https://github.com/FlafyDev) - For getting the home-manager to work - [@FlafyDev](https://github.com/FlafyDev) - For getting the home-manager to work
- [@n3oney](https://github.com/n3oney) - For making custom keybinds finally possible - [@n3oney](https://github.com/n3oney) - For making custom keybinds finally possible
- [@horriblename](https://github.com/horriblename) - For actively implementing planned features and quality of life updates - [@horriblename](https://github.com/horriblename) - For actively implementing planned features and quality of life updates
||||||| parent of d03998c (docs: use new neovim-flake logo)
- [@FlafyDev](https://github.com/FlafyDev) - For getting the home-manager to work - [@FlafyDev](https://github.com/FlafyDev) - For getting the home-manager to work
======= - [@Yavko](https://github.com/Yavko) - For the amazing neovim-flake logo
- [@FlafyDev](https://github.com/FlafyDev) - For getting the home-manager to work
>>>>>>> d03998c (docs: use new neovim-flake logo)
and everyone who has submitted issues or pull requests! and everyone who has submitted issues or pull requests!

Binary file not shown.

Before

Width:  |  Height:  |  Size: 169 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 99 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 171 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 246 KiB