You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs(readme): rewrite README with disclaimer to source repo
Remove screenshots, add disclaimer linking to magidc/nvim-config as the
upstream source. Keep Installation, UI Theme, Custom Mappings and
Featured Plugins sections. Drop IDE mappings, Troubleshooting and
Feedback sections.
# Neovim configuration for Java, Python, Rust and Lua
2
2
3
-
This is my personal LUA based configuration for Neovim that I use on a daily basis as Java, Python and RUST IDE. This setup is the product of continuous enhancements based in what I have found in configurations shared by other users. It is an ongoing project that may evolve with time as I come accross with new plugins, refine mappings or refactor configuration files.<br>Feel free to fork this repository and adapt it to your own needs.
3
+
Personal Lua-based Neovim configuration used as a daily IDE for Java, Python and Rust development.
> **Disclaimer:** This configuration is based on and forked from [magidc/nvim-config](https://github.com/magidc/nvim-config). Credits to the original author for the foundational setup.
1. Install latest [NeoVIM version](https://github.com/neovim/neovim/wiki/Installing-Neovim). The configuration also includes an script to install automatically Neovim in APT based Linux distributions (Debian, Ubuntu, PopOs...). See [install_nvim.sh](https://github.com/magidc/nvim-config/blob/master/install_nvim.sh)
29
-
2. Install [ripgrep](https://github.com/BurntSushi/ripgrep) into your OS. It is required by some [Telescope](https://github.com/nvim-telescope/telescope.nvim) plugin searching modes.
30
-
31
-
3. This environment is preconfigured with Language Server Providers (LSP) and Debug Adapters (DAP) for Java, Python, Rust and Lua. These components provide IDE features like autocompletions, error highlight or debugging. As it is required to have installed these components in your system, this Neovim setup relies on [mason.nvim](https://github.com/mason-org/mason.nvim#installation) plugin to install them automatically if they are missing.
32
-
<br>
33
-
34
-
# UI theme
35
-
Several UI themes are preconfigured in this setup. Active theme is set by editing file `lua/settings.lua`.
36
-
Default active theme is [Tokyonight](https://github.com/folke/tokyonight.nvim).
2. Install [ripgrep](https://github.com/BurntSushi/ripgrep) — required by some [Telescope](https://github.com/nvim-telescope/telescope.nvim) search modes.
17
+
3. LSP servers and DAP adapters (Java, Python, Rust, Lua) are managed automatically by [mason.nvim](https://github.com/mason-org/mason.nvim) on first launch.
37
18
38
19
<br>
39
20
40
-
# Custom mappings
41
-
Most of mappings are defined in file `lua/mappings.lua`. WhichKey plugin is used in order to provide a description for each one of them.
42
-
Other mappings can be found in specific plugin configuration files in `lua/plugins/configs` directory. Also, language specific mappings are defined in LSP config files, these mappings are only available when working with specific programming languages (when LSP are attached)
21
+
# UI Theme
22
+
Several UI themes are preconfigured. The active theme is set in `lua/settings.lua`.
# Equivalent mapping configurations for other IDEs VIM integrations
47
-
I have created configuration files with (almost) equivalent mappings for [Eclipse IDE vim plugin (vrapper)](https://github.com/magidc/dotfiles/blob/master/vrapperrc), [IntelliJ vim plugin (ideaVim)](https://github.com/magidc/dotfiles/blob/master/jetbrains/ideavimrc) and [VSCode vim plugin (vscodevim)](https://github.com/magidc/dotfiles/blob/master/vscode/keybindings.json).
48
-
These configurations will allow users who are used to these key combinations to remain confortable and efficient while working with other IDEs.
27
+
# Custom Mappings
28
+
Core mappings are defined in `lua/mappings.lua`. [WhichKey](https://github.com/folke/which-key.nvim) provides inline descriptions for all bindings.
29
+
Plugin-specific mappings live in `lua/plugins/configs/`. LSP mappings are defined in `lua/lsp/` and are only active when a language server is attached.
> Debug Adapter Protocol client implementation for Neovim
65
46
* Others...
66
-
67
-
<br>
68
-
69
-
# Troubleshooting
70
-
If you have problems while installing or using this setup, please report an issue,
71
-
72
-
<br>
73
-
74
-
# Feedback and suggestions
75
-
I would appreciate suggestions and feedback regarding this Neovim configuration. As it is an ongoing project I will be changing over the time to become more useful and easy to use. Please do not hesitate to contact me if you have any comments
0 commit comments