nvim-config VS pudb

If u decided to keep using nvim, u can checkout my config here. I wrote a util that makes it ez to setup lsp, and i put them in my dotfiles repo which makes it ez to sync between my mac and school ubuntu server. There’s also lsp-zero which sets up completion and lsp all at once for u. There’s also many distros u can use which provide a starting point with preconfigured plugins and stuff.

Well after rewriting my config from scratch after using neovim for almost a year, my config is actually stable and pretty organized. I tried lsp-zero but i found it hard to fine tune the ui stuff, so i wrote a little util that’s basically lsp-zero without cmp. Here’s my config.

Modified, One Dark Pro (love the vscode theme but the nvim plugin got some sus highlights so i modified it)

I simply use the superb pudb. Press ctrl+e to open the current file at the current line in your editor.

such a waste of time...

To this day, I'm baffled by the dynamic language folks who cannot get they head around how strictness/rigor (via a good expressive type system) actually makes maintenance easier and more importantly: cheaper.

[1] https://github.com/inducer/pudb

I use the very under-rated pudb in an adjacent terminal window.

I've been using PuDB for a while now.

I think it is also worth mentioning pudb here

Most of the time I simply use icecream (a much better version of print()), and sometimes, I use pudb (a visual debugger) for tougher/trickier bugs.

For a quick view etc I usually fire up pudb in an adjacent terminal window but for a detailed/heavy debugging session I fire up VS Code (with the vim plugin of course). I have used vi/vim for 37+ years now so it is part of my DNA and use VS Code only for it's great vim + debugging facility.

Two that I haven’t seen here and have saved me tons of time are pudb, a great debugger and petl a simple powerful ETL toolkit.

If you want to debug Python then pudb is simply superb. Vim users don't really want or need to "debug inside of vim" do they? We usually are happy to use multiple command line and other tools in adjacent windows. Also, you can just step around and view variables etc in pudb and then press ctrl+e to edit that file in vim, then q to restart debugger.