.dotfiles VS bottom

Once I finished the C code and compiled I only had to set the ld library path so that ffi.load can find my module: export LD_LIBRARY_PATH="$HOME/.config/nvim/lua/config/nvim/" I wanted to do everything from C but calling drop (source) requires a struct args that doesn't look fun to setup. The C code is available here and the ffi here. And here the final utility for the better gF

Credit goes to https://github.com/protiumx/.dotfiles/blob/main/stow/wezterm/.config/wezterm/wezterm.lua

I use LspSaga in my status line with lua line, config here

Another cool feature is that you can get the process name and working dir, so in my Tab title I have a nerd font icon and the folder. In addition the font color changes if the tab has new output for any of its pane. You can check my config here

(source)

I created a new branch and a PR in my dotfiles repo to integrate this changes in case it helps to anyone https://github.com/protiumx/.dotfiles/pull/2

You can check my powerlevel10k config file here.

bottom

I'd suggest Bottom as a TUI alternative to the in-built task managers - https://github.com/ClementTsang/bottom

It works on Windows also.

If anyone is looking for a "top" like, written in Rust, might have a look at https://github.com/ClementTsang/bottom

Looks like bottom with another theme

bottom - A cross-platform graphical process/system monitor with a customizable interface and a multitude of features.

As a macOS user, it boils my brain whenever I've to type in something like ~/Library/Application Support/org.rust-lang.Cargo/config.toml. macOS users have been begging CLI tools to support XDG variables on macOS too. Setting defaults is a strong indication to the community what should be the "preferred" locations. The defaults defined in your article will invariably lead to some authors saying that if that path is good enough for cargo, then it is good enough for their tool. Even the latest draft RFC acknowledges that macOS should use XDG variables too. I've written more about this here.