ayamir/nvimdots

A well configured and structured Neovim.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 26 minutes ago
Type:Configuration / DotfilesCategory(s):Editors & IDEsDeveloper Tools
Added to GitGenius on September 20th, 2026
Created on June 19th, 2021
Open Issues & Pull Requests: 4 (+0)
GitHub issues: Enabled
Number of forks: 479
Total Stargazers: 3,416 (+0)
Total Subscribers: 26 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 287 days
Stale 30+ days: 2
Stale 90+ days: 0

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (28)
  • enhancement (18)
  • lsp (12)
  • upstream (9)
  • usage (8)
  • packaging (7)
  • ui (6)
  • clangd (4)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

nvimdots is a Neovim configuration written in Lua that provides a pre-configured and structured editor setup.

The project addresses the challenge of setting up Neovim with a cohesive configuration by offering a well-organized dotfiles repository. Rather than starting from scratch, users can adopt this configuration as a foundation, which bundles plugin management, keybindings, and editor settings into a structured framework. The approach emphasizes modularity and clarity in how the configuration is organized, making it easier to understand and modify than a monolithic init file.

This configuration suits developers who want a functional Neovim environment without spending time on initial setup and configuration decisions. It works well for those transitioning to Neovim from other editors or those seeking a reference implementation of modern Neovim practices. The project is particularly valuable for users who prefer a Lua-based configuration and want to learn from an established, well-structured example rather than building everything independently.

The project maintains active community engagement through a Discord channel and documentation resources. Development activity shows consistent attention to keeping the configuration compatible with current Neovim versions, with explicit support for recent stable releases. The codebase receives regular updates to adapt to changes in the Neovim ecosystem and plugin landscape.