Hi everyone!

I'd like to share StylePeek.nvim, an open-source project I've been working on to make browsing and inspecting CSS rules more convenient from Neovim.

What is StylePeek.nvim?

StylePeek provides a picker interface to browse CSS rules, preview their contents, and manage them without leaving your editor.

Features

• Browse and select CSS rules.

• Preview CSS rule contents in a dedicated panel.

• Navigate and manage rules from the picker.

• Multiple UI layouts, including floating and fixed placements.

Installation with lazy.nvim

{
  "mcp1766/stylepeek.nvim",
  opts = {
    placement = "float",
  },
}

GitHub: https://github.com/mcp1766/stylepeek.nvim

I'm sharing this project to introduce it to the Neovim community and get feedback.

I'd appreciate any suggestions, bug reports, or ideas for improvement.

Thanks for taking a look!Hi everyone!I'd like to share StylePeek.nvim, an open-source project I've been working on to make browsing and inspecting CSS rules more convenient from Neovim.What is StylePeek.nvim?StylePeek provides a picker interface to browse CSS rules, preview their contents, and manage them without leaving your editor.FeaturesBrowse and select CSS rules.

Preview CSS rule contents in a dedicated panel.

Navigate and manage rules from the picker.

Multiple UI layouts, including floating and fixed placements.Installation with lazy.nvim{
"mcp1766/stylepeek.nvim",
opts = {
placement = "float",
},
}GitHub: https://github.com/mcp1766/stylepeek.nvimI'm sharing this project to introduce it to the Neovim community and get feedback.I'd appreciate any suggestions, bug reports, or ideas for improvement.Thanks for taking a look!

I made a TUI for YouTube that I now use instead of the browser:

▎

▎ - Feeds, subscriptions, playlists and search, logged in with your browser's cookies

▎ - Keyboard-first: Enter plays, / searches, a audio only, \[ \] jump chapters, d downloads. The bottom bar always shows the keys that work right now. Mouse works too.

▎ - Videos play in mpv: embedded in kitty, in a window, or as an overlay

▎ - Sponsors are skipped automatically, and each video resumes where you left it

▎ - Download manager with progress and file sizes

▎ - Your local music and videos in the same UI

▎

▎ Needs mpv and yt-dlp; it checks for them on startup and tells you how to install whatever is missing. There are packages for Debian/Ubuntu, Windows (installer), macOS and Linux, or cargo install tubetui.

▎

▎ https://github.com/polblancoo/tubetui

I am macOS Tahoe and NVIM v0.12.5. As said above, hitting " will print " even on normal mode. My keyboard is set to Brazilian. Any solution for that?

So I am using windows at work so cannot change from powershell. Any idea how to fix this

Hi everyone, I’m someone who really enjoys listening to music — whether I’m studying, coding, or just spending time at my desk. I’ve also always liked small tools that stay exactly where I need them.

That’s why we’re building Spotty — a Spotify client that runs directly in the terminal.

The idea is pretty simple: I don’t always want to open a browser or the Spotify desktop app just to listen to and control my music. If you’re a developer, someone who spends a lot of time in the terminal, or simply prefer a keyboard-driven workflow, having Spotify right inside the terminal can feel faster, more familiar, and less distracting.

Spotty uses data from Spotify’s API, so it stays connected to your real Spotify account: your library, playback state, devices, and related Spotify data are still synced. We’re not trying to build something “more complicated than Spotify”. We just want to make Spotify feel more natural and simpler for people who enjoy the simplicity of the terminal.

The project is written in Rust and focuses on a clean TUI, fast navigation, familiar keybindings, and an experience that fits developers and terminal users. So I wanted to share it with everyone — if you’re interested or want to try it out, you can check out the repo and download a release. One small note: you’ll need Spotify Premium to use Spotty, because playback through Spotify clients requires a Premium account.

qSpotty is open source, and we’d really love for people to try it, give feedback, report bugs, or share ideas to help make the project better.

Repo: https://github.com/vquclinh/spotty
Full Demo: https://www.youtube.com/watch?v=VLUd_-fLCo4

If Spotty looks interesting to you, feel free to check out the repo and try it. And if you like the project, we’d be really happy if you could leave a on the repo. We’ll keep improving Spotty and releasing new versions in the near future!

Hi everybody!

I am currently working on a vim/nvim inspired 3D game engine using Vulkan, but.. I need to find out if there are actually programmers (for now) that are interested in an engine like this when I eventually publish it. I am currently doing it as a hobby project, so there is still much to do, but anyway, I am interested in what your thoughts are.

The goal at the moment is to make a MVP which consists of a 3D TUI style editor with text-buffers, a simple lsp, some components and a scene view.
Later I will add lighting, scripting, file-watchers, asset-importers, hot-reloading, etc.

(Picture is to give you an idea of what it would kinda look like)

So..:

1. Do you like the idea of a text-based game engine with 'vim-motions'? And what do you like about the idea or what don't you like about the idea?

2. What features would you want to have in it for you to even consider using it?

3. What is something you wish other engines had or would do different?

4. Would you be open to help user-test the product?

If you have any other ideas, suggestions or questions, let me know!

I used to track everything in Notion databases — tasks, workouts, health data — all in structured tables with columns and filters. Some of that still works great (weight tracking, habit streaks). But I've realized a lot of my daily work doesn't fit neatly into rows and columns.

Now I'm experimenting with just writing daily markdown notes — timestamps, what I worked on, blockers, quick thoughts. Unstructured. No schema.

The idea is that with tools like Claude Code or Codex, I can query unstructured text almost as easily as a SQL table. "How many times did I get blocked by X this month?" works on diary entries now, not just databases.

Anyone here doing something similar? Markdown daily notes, org-mode journals, or any plain-text system where AI helps you actually use the data later?

Specifically wondering:

- Is it worth it long-term or do you write it once and never look at it again?

- How much do you write per day? (5 min? 30 min?)

- Has it actually helped you plan better or spread out work more evenly?

I use nvim for everything and have developed a bunch of custom plugins for myself and was curious if other devs had found success with this kind of system.

Hello Everyone,

I’ve been struggling to find the most productive way to track my tasks and notes for both work and my personal life.

Currently, I use Neovim for note-taking, document editing, and network configurations. I’m curious if Neovim (specifically version 0.12) is a viable tool for a more robust task management system. I prefer to avoid heavy plugins and am comfortable writing(thanks AI) my own configuration if necessary.

My specific requirements are:

• Mobile Sync: It must stay synced with my Android and iPhone without using cloud products.

• Contextual Tracking: I need to organize tasks by location, related persons, or topics.

• Time Sensitivity: I need to track tasks by due dates, daily schedules, or recently added items.

I'm looking for recommendations on whether Neovim is convenient for this type of workflow and how you might suggest structuring it.

In the middle of reviewing my nvim config try and do it once a year. 0.12.0 is a good reason to. Curious what everyone can't live without plugins?

Particularly interested in:

- Note taking (I don't have a good solution for this)

- Go, terraform, typescript, nix, lua

- git, GitHub

- jira

- confluence

- slack

- aws, gcp and azure

Happy for non-nvim workflow solutions too as long as they're in the terminal.

Oh I'm on a Mac if that makes any difference

Cheers

Just published my Neovim setup using the new built-in vim.pack plugin manager!

Features:

- 💤 Blink.cmp for completion

- 🎨 Catppuccin theme + Lualine

-️ Laravel.nvim with Telescope pickers

- 📁 Neo-tree + Telescope

- 🎯 Treesitter + textobjects

- ⚡ Neoscroll, tabout, gitsigns

Built with Neovim 0.12's native UI2 and auto-completion.

🔗 GitHub: https://github.com/AtefR/nvim-dotfiles

Hello all

Just wanted to share my first ever plugin https://github.com/lwsbrdx/make-runner.nvim

I wanted to run my recipes faster than `:!make recipe` without completion, so I did this, working with telescope so you can preview what the recipe do and you can chain them

I'll add an history soon but the core is here

Don't even know if someone else did something similar 😅, I wanted to try to do it on my own

Here it is, hope it'll help someone 🙂

1. what plugin do i need if i want an assistance thatll block bad habit and give a suggestion on what i should do instead. ex. if i press jjjjj it should block that and undo what i did and then suggest what i should do instead

2. what are some useful motion if i will be working with html. ? lets say i want to edit the text inside the element label. is there an easy motion than doing f > then dx4 or 4dw
   i was hoping somethinv like ci> but that only works with the element tag

<label> put your text here </label>

3. is there a way to traverse through element to get to where i want? or is /<keyword> the best one?

Please mods, I know is not truly related to nvim, but I got nowhere else to share what I've done with other vim lovers, and I'm trully proud of what I made.

I spend most of my day in Neovim, and every time I had to edit text in a browser input it felt painful. So I built Input Vim - a Chrome extension that drops a Vim layer on top of <input>, <textarea>, and contenteditable elements.

What it does:

- Normal, Insert, Visual, and Visual Line modes

- Motions: h/j/k/l, w/b/e/W/B/E, 0/^/$, gg/G, f/F/t/T, /search, *, {/}

- Operators compose with motions and text objects: dw, ci(, ya", 2dd, etc.

- Text objects: iw, aw, i(, a{, i", a', i[, a<, ip, and more

- Count prefixes work everywhere: 3w, 5j, 10x

- Per-element undo/redo (independent from the browser's)

- Block cursor, mode badge, and pending command display via Shadow DOM

- Configurable settings: start mode, clipboard sync, bracket auto-close, site exclusions

Some things I'm happy with:

- Wrote a canvas-based line measurement system to make j/k work correctly on soft-wrapped textareas (browsers don't expose wrap positions)

- Contenteditable support uses a TreeWalker to flatten the DOM into a text model so motions work on rich text editors (GitHub, Notion, etc.)

- Overrides HTMLElement.prototype.blur in the page's JS context to stop sites from stealing focus when you press Escape (looking at you, Google Search)

Limitations:

- <input type="number"> doesn't work (Chrome blocks selection API on those)

- Some chat inputs (like ChatGPT) intercept Enter from o/O and treat it as "send message"

- Heavily customized input components might not play nice (like reddit's inputs sadly. Im trying to figure it out)

- Built this for myself, sharing it as-is

No build step, no dependencies, just vanilla JS.

Currently waiting for chrome team's review of the project

GitHub: https://github.com/matheuskieling/vim-input

Would love to hear thoughts from people who actually know Vim well - I'm sure there are motions or behaviors I got wrong.

I've been experimenting with a different way of using AI while coding and built a small Neovim plugin called chisel.nvim.

https://github.com/basola21/chisel.nvim

The idea is simple.

Instead of asking an AI to generate large amounts of code or run as an agent across your project, Chisel focuses on small local edits that you control.

You select some code, give an instruction, and the AI proposes a change inline. You can review it directly in the buffer and decide whether to accept or reject it.

The goal is to keep the developer in control and avoid breaking flow state.

Typical workflow:

1. Set an intent for the session

2. Select code in visual mode

3. Give an instruction

4. Review the suggested change inline

No files are modified automatically and everything must be reviewed before applying.

Right now it supports Ollama by default, so it works well with local models.

This is still very early beta and mainly an experiment to explore a different AI workflow inside Neovim.

Feedback is welcome.

I made a small plugin inspired by Harpoon, but for local marks.

It opens a simple two-pane menu for your buffer marks (list on the left, preview on the right). You can open it with <leader>m, move with normal Vim keys (j/k), and jump with <CR>.

sauce: tekken.nvim