dwmblocks VS NvChad

Status bar : dwmblocks

dwmblocks: a clickable dwm statusbar written in c. would require some scripting and learning on your part. prob the only way you can get axactly what you are asking for outside of the look while remaining "suckless"

I just patched statuscolors to my dwm build with the aim of bringing colors to my statusbar (I use dwmblocks). I want to achieve something aesthetically similar to bumblebee-status, with each statusbar block appearing in a different color. As explained in the patch documentation, I defined an array of colors in my dwm config, something like this:

I use this https://github.com/torrinfail/dwmblocks, this will take care of slstatus stuff for you.

As of now, I have the official vanilla dwm, with just the statuscmd patch, AND vanilla dwmblocks from torrinfail, also with the statuscmd patch made for it. I'm having trouble understanding how to configure clickable modules.

At the moment in trying to patch the torrinfail version.

To update the status you can use a shell script see the suckless site. or use an external program such as dwmblocks.

Need suggestion on how are you restarting your dwm status bar set with xsetroot and not the classic dwmblocks. I have a script dwmbar which loads the status bar. Then I use another script which reloads the status bar whenever I press volume key, which takes significant time.

NvChad

If you use Android device, you can try Termux , and in Termux I recommend NavChad as IDE . You can also find a lot of other useful packages .

git clone https://github.com/NvChad/NvChad $HOME\AppData\Local\nvim --depth 1 && nvim # if the above path doesnt work, try any of these paths : %LOCALAPPDATA%\nvim %USERPROFILE%AppDataLocal\nvim C:Users%USERNAME%AppDataLocal\nvim

line 1: you would have to copy it and remove all the nvchad keymaps and additionally reformat your keymaps to adopt this format. for example, if you copied the file in the link to lua/user/mappings.lua I believe you can just replace the first line with:

I'm confused as to why this is happenening as I have been able to load LunarVim and NvChad with any problems whatsoever.

I would suggest to start getting into vim by first trying out popular vim keybinding plugins available on your favorite code editor and get used to those first. Then, if you want to dive deeper into the power of Neovim, try out popular configs like LazyVim, LunarVim, NvChad... Taking Neovim from a mere text editor to a full-featured IDE with features like intellisense, debugging, testing, etc... on your own takes quite a lot of work and configuration.