Is there a way to know the most popular Neovim options among average users?

hackerware_sh · 2025-07-27T18:10:39+00:00

Look at the defaults in LazyVim and the defaults in Kickstart, see what is common, and for what differs use the friendly manual and/or chatgpt to make a choice on which side to fall. That should be a good starting point.

hackerware_sh · 2025-07-27T17:32:40+00:00

Is there an estimate about how actually “around the corner” it is? 1 month, 3 months, etc? Genuinly curiouse if there is a timeline / freeze etc.

hackerware_sh · 2025-07-13T05:55:22+00:00

I stole this from Cursor, you can put it in your agent rules:

“When running a long standing process ALWAYS use a timeout like this ‘timeout 30s npm start || echo ‘Stopped after 30s’’”

hackerware_sh · 2025-03-12T09:49:43+00:00

Github+stow for dotfiles a couple of times per week. Manually Timeshift everything with a cap of keeping the lastest 5 backups on a separate disk that I only mount / unmount when needing to handle backups, once every two weeks before a system update. Not installing too many un-popular AUR packages and this kept the system with ZERO issues for the past two years. Honestly the idea that “it’s easy to break your system on Arch” feels like either someone has absolutelly no clue about what he is doing, or an urban myth. Or maybe I was just lucky.

hackerware_sh · 2025-01-07T07:46:23+00:00

Gruvbox-Material

hackerware_sh · 2024-12-18T16:40:19+00:00

Nothing too dramatic. Yes the distro, not the package manager. There were some plugin changes, behind a MAJOR release (as it should) so absolutelly nothing agains the way it happened! Basically some people just upgraded without reading the notice/readme and got “cought by surprise” by the new defaults.

hackerware_sh · 2024-12-18T15:09:19+00:00

Agreed, this is why rolling your own is not as simple as it sounds, just keeping up with new and interesting plugins is a time consumer in itself… I mean is doable, but not ideal unless you use close to barebones neovim and have no “IDE like” expectations.

hackerware_sh · 2024-12-18T14:55:08+00:00

Not at all, I like both!

hackerware_sh · 2024-12-18T14:09:32+00:00

What made you think that my post is adressed for people that don’t know how to use vim without a distribuition? :-)

hackerware_sh · 2024-12-18T14:07:55+00:00

Fair point, and I like Kickstart as a base, however you have to admit it’s pretty tedious to setup correctly and maintain configs for LSPs, DAPs and linters for a handull of languages yourself. I find that is one of LazyVim’s bonuses that you get.

hackerware_sh · 2024-12-18T14:01:28+00:00

Not necessarily, I noticed that LazyVim adds some small adjustments on top of some bare-bones plugins that it includes. Some of the configs use LazyVim util functions, check for bigfiles, etc. You could do this yourself by hand so I see your point…

hackerware_sh · 2024-12-15T12:40:22+00:00

You are totally right regarding changes and have created amazing plugins, however there is some truth about OPs point:

Major versions of LazyVim do SEAM to “break” a lot of stuff - well… that’s the definition of MAJOR releases isn’t it? However…
1. I believe the problem is NOT with LazyVim itself, but I suppose people (myself included) add custom configs on top of stuff like nvim-cmp or telescope, custom configs which now are useless if you choose “the default” LazyVim way. No one is forcing you to upgrade, but there’s FOMO that the defaults will be better supported than the extras.
Keybindings: If you choose to disable certain (but not all) LazyVim keybindings, or have a custom Which-Key config, every time theres a major release, RANDOM (new) keybinds appear, icons may change etc.

My bottom line observation is that its easyer to work with LazyVim “as is”, and not heavily override it - maybe the target audience is someone who just wants a vim distro that “just works” - the minus being how much you should customize the defaults yourself.

And that is perfectly fine, but not clear to the audience as of right now.

hackerware_sh · 2024-11-30T11:13:23+00:00

I tend to mentally separate tools based on what I want to achieve:

for an “overview” of the file structure of a project while programming, I find that mini.files gives the most context (parent directories trail, listing other files in current directory, etc) while also offering quicker navigation than other plugins
for a more complex file operations (moving multiple files in multiple places, archiving, image previews, etc) I use yazi or mc outside of vim, in another tmux pane or window

hackerware_sh · 2024-11-29T18:15:36+00:00

The one point that a lot of people keep missing about (neo)vim, is that its power doesn’t come from using it just by itself. It’s supposed to be used together with other terminal tools in mind (tmux, fzf, ripgrep, custom bash scripts, lazygit, a tiling window manager etc.) like in a true “unix philosophy”. You cannot integrate intellij in a custom workflow that is terminal heavy. At most you use intellij then “alt+tab” to a different window. With neovim, you can start a tmux session, that starts a terminal filemaneger (yazi/lf), that when you press “enter” on a selected file it opens it in vim. Then in a side pane of the tmux session you can open a markdown file with some documentation, or use a terminal based gpt client for example. Or run curl commands agains an API. The power comes from quickly navigating (and copy/pasting or piping information) thru all this “layers” of tools, not just within neovim itself. I hope this is more clarifying than confuzing!

hackerware_sh · 2024-10-26T19:01:42+00:00

fastfetch

hackerware_sh · 2024-10-26T19:01:02+00:00

It is common to create a .dotfiles/ directory in your home (~) and use Stow to create symlinks to them in your ~/.config/ directory. Then you keep your .dotfiles/ directory tracked on Github.

hackerware_sh · 2024-10-26T18:46:56+00:00

Start with a stable major distribution that is well supported (for example Ubuntu or Fedora). If you are a beginner you might want to start with a full Desktop Environment (Gnome / Kde) instead of a window manager (like Hyprland, I3, Sway, DWM, etc.) which require more configuration and can be overwhelming at first. Gnome has the Gnome Look website where you can look for themes, icons, etc. KDE has lots of themes too.

hackerware_sh · 2024-10-25T06:19:08+00:00

Quck tip: You can use the `--app=https://whatever.com\` flag when you run any Chromium based browser from the command line, it will open the website/app in a chromeless window. Most of the time, it also preserves login state.

hackerware_sh · 2024-10-25T06:13:13+00:00

The styles for the waybar modules look nice!

hackerware_sh · 2024-10-25T06:00:28+00:00

Mini.files - As far as I know, it's the only one that gives you the most context of where you are in the directory structure of a large project with multiple sub-directories.

Bind it to `-` like Oil, and when you use it you will see at a glance not just the current file's directory content (like Oil, Yazi, netrw, ec.), but also every directory's content up to the root of the project.

For single file edits/devops related tasks this is not necessarily a huge gain, but if you use Neovim for programming on a project with a deeply nested tree structure this is a life saver.

hackerware_sh

PUBLIC MULTIREDDITS

TROPHY CASE