DONT use Neovim!! (in these scenarios)

[@itsfkf6106]

Thanks, Nerd

[@typecraft_dev]

Thank you, Nerd

[@RedbeardyMcGee]

In a twist of ultimate irony, I put both `yazi` and `lazygit` inside my `nvim` to be summoned with a keybind in a floating terminal.

[@sspaeti]

nice, just replaced oil with yazi inside neovim on keystroke `-`. Feels nice. I used to use ranger before, never got use of oil. Thanks for the tip

[@BlastHardCheese711]

yup floating lazygit, terminal, and yazi. Sooooo good.

[@raymondkemboi1349]

To add, I also found mini.files to be better than oil.nvim

[@sspaeti]

​@@BlastHardCheese711 Yes! Except for terminal stuff I use tmux and open a separate terminal.

[@sutirk]

​@@raymondkemboi1349agree, mini.files takes care of all my file managing demands, much better than oil. I might look into how yazi integrates with neovim though

[@JonathanRose24]

I’ll admit, I don’t use Neovim to brush my teeth. It’s just not very good at it from my experience

[@redbolder]

patiently waiting for him to say: you should use Jetbrains

[@typecraft_dev]

I WOULD NEVER

[@samhindhaugh696]

If you are ever in the unfortunate position of needing to write java Intellij is your best bet, or a massive c/cpp codebase

[@aryanshmahato]

​@@typecraft_dev Why??

[@w01dnick]

@@aryanshmahato From my perspective. I'm not against IDE as a concept, but jetbrains products are too intrusive and trying to be too smart. I've often ended up fighting against it rather than it helping me.

[@txarli]

Debugging on rubymine is a hidden pleassure..

[@codemustbeelegant]

Yeah, Neovim isn't just another Emacs

[@typecraft_dev]

truth

[@ToveriJuri]

If it's bad design to use Neovim as fully featured Integrated Development Environment. Then there's no reason for me to use Neovim at all instead of something like Jebtrains IDEs with Vim motions. If I have to launch bunch of separate little tools for every single job instead of having them efficiently in the same place combined by conceptual need (say software development) then I'm just going to find another solution. I also think this video kind of misses the point of what Unix philosophy is and that Neovim with git management, a file tree, and a visual debugger *does actually follow the unix philosophy.* These tools aren't integrated into a monolithic software known as Neovim. They are separate tools and extensions that can be brough together into a tool to add functionality, but they are still developed and maintained separately. And while there is a lot of good in Unix development it is also outdated for some modern tools and workflows. Imagine using a web browser that follows Unix Philosophy. There are attempts at those, but there's a reason we mostly use chromium or Firefox based browsers instead.

[@gromph4]

Epistemology vs Ontology of text editors

[@typecraft_dev]

what did you call me?

[@stefanbondzulic]

I see a lot of comments agreeing here, so I must be in the minority. One of the selling points apart from modal editing of Neovim is its extensibility and hence why I don't use vi as my text editor, so this premise does not hold much weight, at least for me. I would much rather edit my commit messages in Neovim, as I have snippets, spell checking (not a native speaker), cmp auto complete of my issues, etc. Same for file editing as I usually want to start my actions (renaming, adding, moving) from the current file path which is easier with help of Neovim, then opening new pane, and navigating again. And the only reason I'm leaving this comment is that I have been influence by videos like this multiple times over the years to go and change my workflow, just to end up coming back, and ultimately wasting time. But at the end of the day we all have our preferences, so I guess trying it and figuring out for yourself even if it ends up being a waste of time may be the best option.

[@007arek]

The problem with having everything in nvim is that you will have to maintain it. Tell me how many times did you change your file manager plugin? The main argument from this video is that you should use a proper tool and combine them. For example you can open a TUI file manager in a nvim window with this extension - fm-nvim

[@stefanbondzulic]

@007arek Well, first off, the argument about "proper" tool is very subjective in my opinion. Second, I would argue that your suggestion could be worse, depending on how you look at it. Instead of having a one plugin, you have one plugin, plus external program which are not connected, and say external program introduces a breaking change now what? And lastly, about changing the plugins. While it's true that i over the years changed many, that was because I wanted to, not that I had to. The same can be said for dedicated file managers, first was ranger, then lf, then nnn, then yazi etc

[@007arek]

@@stefanbondzulic A proper tool is a program designed for a specific task. Do you manage all your files in nvim? That would be absurd, wouldn't it? This is the point: if an external program breaks, you change to another. If nvim stops working, you will not be able to manage your files. That addition plugin is just a helper - if you like, you can use nvim's windows. I explained my argument about maintenance incorrectly. When you have many plugins, it starts to become a pain, especially in small projects like nvim. Sometimes, you will need to migrate or fix breaking changes because plugins depend on each other and the nvim API. It is better to separate tools.

[@sutirk]

Yeah his points do make sense, because its feels right to be able to use the same tool for a task regardless of being inside vim, but in tasks that you mostly already have vim open, using a different program just seems counterproductive. I use tmux way before ever getting deep in vim, and i never even think about opening a terminal inside vim because to me text editing and terminal commands are different beasts entirely. Also tmux is always running underneath vim, so i already have an efficient way of dealing with new shells. But im way too comfortable using fugitive, gitsigns and minifiles, these are already integrated in my neovim. Also lets be honest, how often do you do heavy interactions with git, or do complex file managing shenanigans outside of a project you're already working (and textediting) on using vim? I looked up the keybinds for lazygit and yazi, and while they do have some vim-like keybinds, some of their keybinds are just the opposite of what you'd expect. Theyr vimmyness is about the same as the websites that allow you to scroll with jk and use / to search. For example, yazi uses y to yank file, d to thrash file and x to cut file. That's both similar and different enough from vim to cause confusion. Also it uses cc for copy file path, and r to rename. Thanks, but I'll stick to the default vim keybinds and textobjects inside of minifiles.

[@TehKarmalizer]

I didn’t like the terminal experience in an nvim tab. Just didn’t feel natural. Fugitive seems okay, but I guess I’m just too used to using git via command line. I haven’t tried visual debugging, but I’m curious about that as I have a project where it would be beneficial.

[@integeroverflowexception]

Had me in the first half of the title

[@soy_ari_gutierrez]

What a video! And here's my 2 cents: I think the "problem" of overloading tasks in neovim comes from the idea of moving from a visual IDE to terminal one; and where's the "starting point". Visual IDEs handles the whole thing inbounds; and some of them do it great, such as many Jetbrains products. In the terminal, you have to craft your own DE, and "conceptually" you start from the editor, because is the one that provides the same main task of your workflow, and the one we think is the "core" of our workflow; because you have no need to exit from it to build, debug and push and pull changes. Those pipes into an IDE are blurry. In terminal DEs; the core is the interpreter itself or the multiplexer, and using different tools to each step. It's a game changer to understand where's your "core node" of your workflow if you see it as a graph, and where you pivot to the different nodes. Maybe this approach helps to keep nvim more clean and light, freeing of it from several tasks. But the question is, which tool can be used to step by step debugging and variables monitoring in a "similar" way than the ones in IDEs? Even though vscode suffers the problem of plugin overloading; but it's the one that really shortened the gap to IDEs like Jetbrains' ones. LSP as an example, it was a game changer and by far it's the best contribution to software development tools made by Microsoft. BTW, i use ranger instead of yazi; I should take a look of it 😉.

[@ToveriJuri]

I think this video misses the point of what Unix development is in the first place and that Neovim with all its plugins does in fact follow the unix philosophy by its very nature of giving you this extended functionality through plugins. It could be argued that Neovim distributions is where we break away from the more granular design philosophy, but ultimately even distributions are just bunch of smaller tools packaged together for convenience and ease of use. If you wanted to stretch the concept a bit, you could consider even the distribution just as another tool that helps tie other tools together for accessibility.

[@DreamingDolphing]

And neovim is also not very convenient for constant work with AI helpers, as it is in these fancy new code editors like Cursor. Some people don't like AI assistants at all, but we can't deny that they're changing the way we write code right now.

[@hamm8934]

In earnest, I still dont understand comments like these. I still struggle to find use for AI outside of replacing the occasional google search of a reminder of something i already understand but need a refresher of

[@1Caja]

​@@hamm8934 Same

[@Greenmarty]

When the hype was high i tried multiple AIs in multiple IDE/editors and i came to conclusion that in the end code is better to be written without them for multiple reasons (random AI hallucinations, dumping ones brain, debugging someone else code sucks, etc.). But i admit AI is useful for administrative souse like docs and emails.

[@abdallahelsayed7072]

Oh man the title of the video, I thought me changing to NeoVim was a mistake for a second after watching the whole series of NeoVim!🤣 Thanks man you are the best out there!

[@brunofilipe9623]

Unfortunately another thing neovim isnt great for is managing files with multiple languages, like jupyter notebooks. I know there are people who made it work but its not easy to get it configured. A professor is suggesting us to use it for a classe but Im really not feeling like it for this precise reason 🙃

[@ericjmorey]

I'm trying to use quarto with Neovim to produce Jupyter notebooks. I'm not sure if I will stick with it long term, but it's workable so far

[@josesblima]

Neorg! Was a pain to config, I just couldn't get all the dependencies to work together. I used the Neorg starter pack now and it works flawlessly, basically my ground setup is just Neorg starter config with kickstart.nvim

[@alecclews]

Don't use vi/vim/neovim when you should use sed. When is that? 1. When you need to script editor actions (for example change a config file during a build) 2. When you need to make identical/similar edits to multiple files Note: Many people use awk or something similar for this type of job, but sed is faster AND it makes you look like a UNUX wizard 🙂

[@michaelwesolek]

Regarding #1. It only works, because the output of your test is so short. I usually get allot of deprecation warnings, because my co-workers don't run pytest from the command line, but rather use Pycharm which doesn't display these warnings. So i usually have to scan if there is anything that is from me or new in there.

[@onewhoanimates9016]

This is so true sir. I’ve truly been feeling a sense of plugin overload on nvim lately that I’ve been using vim with a light vimrc to keep it simple. Next time I have time to do a fresh start on my nvim I’ll probably start with the vimrc as the skeleton

[@assyriaaaaa]

Thanks, I like your channel and started subscribing.

[@typecraft_dev]

Awesome, thank you! Welcome

[@serhgoch]

Moving files example might not always be correct: some LSP(e.g. tsserver) provides code action that also updates imports of those files, so one doesn’t have to update them manually after moving the files

[@desvendandoornasaude4127]

Greatings from Brazil

[@AGentooUser]

Thanks for lua! the best interpreted language ever.

[@Amaraticando]

​@@AGentooUser it literally sucks. Lua is painful and the libraries are pretty much nonexistent. Luarocks is a disgrace to humanity. Brazilians (like Indians) are needy, they always feel the urge to say where they came from.

[@AbhinavKulshreshtha]

What is your recommendation for a tui based visual debugger. That is the last thing I need to completely remove vscode from my system.

[@hamm8934]

i disagree with his point in the video about not using nvim for debugging. I've switched almost exclusively to nvim's dap for debugging and have setup a workflow that makes using any other debugger feel slow and inefficient. tbh i think a lot of the takes in this video are just preference without substance. he mentions advanced file management, and even mentions oil.nvim, but says "nah dont use that, it's not good enough." You can literally use vim macros in oil.nvim... Oil is by far capable of many, many advanced file actions.

[@jefferyosei101]

Thank you, you gave me a good laugh in that intro

[@mrjson3039]

I loved this video, thanks to remind me about yazi. With my current workflow alone I just couldn't make nvim my PDE, I love to use tools that excel at that "one" thing. Amazing video!!!! I'm already doing these things, I feel validated hahaha

[@게임제작]

I put a lot of effort into trying to use Neovim and Arch Linux recently (mainly because they looked cool...). Now that it's time to prepare for job hunting, I often encounter situations like "Please take the coding test using Chrome on Windows OS." After using Neovim for a while, I found it confusing to switch back to IDEs like PyCharm or VSCode, so I eventually decided to temporarily stop using Neovim and Linux. Since my English isn't very good, I'm not sure if this is what the video was about, but I agree that it's important to use appropriate tools, IDEs, and operating systems according to the situation. I hope I can get a job soon so I can dive back into the world of Linux and Neovim! Thank you for the interesting video.

[@tears_falling]

Totally agree. That's why I use Alacritty + Tmux + Neovim, and the Git CLI.

[@mobugs]

ultimately it's down to user preference; if it helps your workflow use it, if it adds friction find a better way.

[@kevas777]

I was configuring nv half a year, and i still need maybe 3+ years of configuring all my staff...i drop nv, because its such a pain. Why i need to use git out of textediting...if you want text editor use vim. Neovim isteed must be ide, or it just no sence from lua integration. Programmers in 100% cases need not only text editing, so if nv needs to be used only like text editor, so i dont need it at all.

[@Lado93]

Agree with the video! You should not use nvim for Java and debugging :)

[@JulianInsua]

Great take! What do you use outside of neovim to visually debug code?

[@w0ode198]

The voices in my head told me to steal your mug, so when you feel comfortable to reach out and make your selective tea / Coffee it doesn't exist anymore.

[@purplelord8531]

the thing about the built-in terminal or other situations like it is that they're still separate programs - as you said, you can decide whether to run it inside or not. I'm a ranger user and the fact that it opens neovim when I enter a file isn't necessarily a complication when ranger doesn't suit my needs I can just leave and use nvim from the terminal I can also replace ranger with something else when it doesn't have a feature I want

[@rumble_bird]

I think about Neovim now not as just a text editor but as an environment, meaning it's similar to terminal more, despite the fact that it's not really meant to be used as one. Neovim being an environment has it's own unix philosophy within with plugins, what I mean is that every plugin inside of Neovim has one and only task and is really good at it, however the "editor" itself is not an editor now, but a runtime for those little unix-like plugins. That being said, it's not an ideal solution, and I would much rather have separate tools for each task, sadly with things like LSP and treesitter it's nearly impossible to make such a tool that would inject information inside an editor without a need for a plugin ecosystem.

[@maleldil1]

I know it was just an example, but you can do that file operation with Oil really easily, too. Ever since I started using it, I rarely feel the need for something else, with Oil and standard cp/mv/rm operations doing everything I need. I fully agree on the terminal thing, though. I really like using splits where I have my editor and terminal for running quick tasks side-by-side, and nvim's terminal simply isn't as powerful as a tmux or kitty split.

[@hendrykhoza4782]

For the first time where I don't agree with you. Reason I like to do all those task in Neovim is to be able to create a mapping for them

[@robfahey7363]

Great vid, it's always good to ask when you should stop injecting "features" into apps and instead use an app designed for what you are trying to to.

[@ivanjermakov]

I don't quite agree on the point of not using a terminal within nvim. Text editing is not only about modifiction, but also about navigating, reading and searching. If I need to copy a part of some command's output into the file I have open, there is no better way than to run it from the :term, this way the full power of nvim's text navigation can be used to find and select text needed.

[@hamm8934]

It all boils down to personal preference. I agree with some of your examples, i disagree with others. When should we not be using neovim? When it doesnt make sense to us. Dont listen to videos for how your workflow should be if it doesnt resinate with you. PS neovim debugging has become my favorite debugger of all time. Ive created to most efficient debugging workflow ive ever had.

[@CaioLesnock]

What exactly is visual debugging? Are dap + dapui considered visual debugging? If so, what is the alternative?

[@typecraft_dev]

Yes, dap and dap ui are visual debugging. Honestly, whatever the preferred debugging tool for the language you're writing would suit best

[@ryannathanwilson]

Any recs for debugging software for JS/NextJS outside of neovim ? I have VS-- basically just for the debugger, but would love something else.

[@sjthesahiljoseph]

My way of writing code is (by the way I use Emacs but still), Use text editor separately, and open up a terminal, that's it. Even I don't use panes, splits, for terminal and editor. These are two different software.

[@legendcat8913]

What’s the difference between a visual debugger and a…. Non-visual debugger? What’s an example? I’m new to coding and haven’t heard of another method to debugging

[@onewhoanimates9016]

Type gdb in your terminal. Run it without the tui command

[@typecraft_dev]

vision

[@ToveriJuri]

Hardcore developers debug while blindfolded. That's why our (my) code is damn buggy...

[@8uff3r]

I agree with almost everything, except using it for git, neogit is just too good...

[@DanelonNicolas]

strongly agree on all of it. good video!

[@typecraft_dev]

thanks!

[@m4kamran008]

When dealing with long-running processes, how would you handle actions like navigating to a file with an error? For example, within Neovim, I can bind gf to quickly jump to the file directly in my Neovim instance. Is there a way to achieve similar functionality using tmux?

[@raymondkemboi1349]

Idk about tmux, but with Kitty you can use nvim as a scrollback pager, position the cursor under the filename and visit the file with “gf”

[@rodelias9378]

Give this guy an oscar. Pure genius!! Thanks for the talk!

[@Deimort310]

Honestly I mostly agree with what was said in the video, which is already what I tend to do these days with my dev workflow. However, I still think that git repository management can be done really well within the editor (I personally prefer to use neogit for that). I don't really want to have to switch tabs in tmux/zellij since I usually do a lot of small commits

[@seggcsont]

When I used Intellij for development I turned off git integration. For me writing code and managing vcs are different tasks. Needs different thinking, so it is better to separate

[@007arek]

I don't use tmux, mostly because I use a TM. I assume that in NVIM, you also don't need to use tmux for creating terminal panes - NVIM has a built-in terminal emulator. Tmux also breaks UNIX philosophy - it has session and window management.

[@m4kamran008]

Regarding file management, if we separate it from the nvim, we lose the LSP rename functionality, which can achieve with something like neo-tree.

[@TurntableTV]

Those whispers were just Nix users telling typecraft to use their nix configs.

[@RenderingUser]

5:42 funnily enough, i use oilnvim only for advanced file management. because thats literally more suited.otherwise i just use dolphin

[@LilaHikes]

I expanded nvim with kickstart for Python development and hated ever last thing about it. The best way I can describe it is, feature-creep from hell.

[@oleingemannk]

great video, and thanks for pointing at Yazi, i'll give that a try. My biggest "dilemma" these days is chosing between ai-heavy work using Cursor, vs. neovim. I would love to stay in neovim, but the ai stuff I get from cursor is crazy good. Ive been trying out Avante the last couple of days, but it's miles away from cursor. Not sure it will never get close. What do you think?

[@typecraft_dev]

Personally, sometimes I'll use cursor to get something started. Then edit the rest in neovim

[@oleingemannk]

@@typecraft_dev Yeah, I guess a combo will stick for a while even though we wish it was different :P

[@oleingemannk]

@@typecraft_dev Have you tested Avante?

[@Thundechile]

Well, if I'm inside Neovim and I need to for example use Lazygit, I can open it in a terminal popup (inside neovim) and when I'm done just exit the popup and continue. That saves me launching tmux pane, and starting the Lazygit from there. Win-win?

[@enu42]

Where'd you get the TestDouble hoodie? I worked there for the last 4 years.

[@ir8293]

I use gitui, helix, yazi and terminal tabs a lot.

[@HeleneHolst-n1i]

you and quinn nelson sound so alike in terms of your voices. ❤

[@gulpowizzard]

That is kind of the why I am not using NeoVim and I stay satisfied with just vanilla or almost vanilla Vim, despite me being just lazy and not willing to invest myself into NeoVim ;). Why would I overcomplicate my environment (besides "because I can") :).

[@raeperd]

then what u use for debugging? using dlv in cli??

[@BucketHead6541]

I never thought about using something like lazygit in a tmux window instead of a git plugin... I'll have to give it a try. Thanks!

[@mudziahutama7787]

As always..catppuccin 😎

[@mikel8190]

Would love to see your take on the vifm file manager. It has been my favorite for years

[@radosawkak738]

I think the same. Just code in Neovim. The rest is "rest".

[@0oNoiseo0]

This talk on Neovim confference 2024 was one of the best!

[@typecraft_dev]

awwwwwww you're making me blush

[@Silver-eb7zm]

Church of Emacs Propaganda. I wont falter!!!

[@Danielo515]

I don't know man, when I like a tool or a language I want to use it for everything all the time, even things that go beyond it's original intended use and even if it is not the best tool for the job. How can we call that? The Emacs philosophy?

[@itsabhiyan]

I didn't know that people use neovim for the purposes you mentioned

[@Sqwert-g6h]

What gnome extensions are you using?

[@TheBadFred]

That looks more like straw than grass...

[@devopstoolbox]

I just ❤ videos that make you think.

[@gfhdlsk]

I was waiting for something like kotlin development or android reverse engineering. Btw what other program do you use to debug Rust?

[@vanvothe4817]

Hey, do you think the neovim team integrating terminal and LSP was a mistake?

[@sallyhaj]

For me, I don't use nvim while I am asleep.

[@rzyr]

It might sound crazy, but for my git repo management I use git.

[@ercntreras]

Exactly, the terminal already can handle all the tasks, what's the problem by just quitting the text editor, aah forget perhaps newbies don't know how to quit.

[@codywtucker]

I love the opinionated content, it feels like I learned something. It's almost philosophical, and that's cool. Makes me wonder where else I could apply this logic.

[@lipepaniguel]

this is a good take

[@glowing_flare]

I 100% agree.

[@vikaspoddar001]

we need newer version of POXIS standard/specification

[@cuicuidev]

Great stuff! We don't want neovim to become emacs

[@rupen42]

I would also avoid neovim for Android development :P But seriously, Jetbrains is too good for JVM languages to pass on. Also, if you need some more advanced web development plug-ins, vscode still has a better ecosystem for those.

[@guillermogalarza7444]

Great video. 🙌

[@majus1334]

Why does every F'ing video on KZbin has "You must listen to lo-fi hip hop" tax. Just why?

[@bitfluent]

Weeps in Kotlin

[@fabricehategekimana5350]

Did you try nushell ? It's one of the best shell that has ever existed

[@Elia90570]

6:29 im not sure but based on my experience with yazi, i think yazi is just a neovim wrapper

[@otrava88]

thats why i use emacs for almost everything ^^

[@onetwofourfive]

I don’t ever use neovim, because by default it’s not installed on any major linux/unix/bsd server distribution.

[@barry5]

How many times are you in a situation where that actually matters

[@onetwofourfive]

If you need to work on many many servers per day, I’s say a lot.

[@sutirk]

​@@onetwofourfivedepending on the servers you access, you might wanna look into sshfs. It mounts a remote filesystem using SFTP, and you can use your local vim/neovim and tools to edit files remotely. It's not perfect for every scenario, but it might be worth it if you're doing long editing sessions remotely.

[@fidgety846]

Theme? Been looking for something like it.

[@typecraft_dev]

catppuccin mocha

[@aseeralfaisalsaad]

The Ubuntu logo on ur terminal prompt did u change ur distro from arch

[@typecraft_dev]

uhhhh....... don't be mad okay?

[@CookieGod24]

heresy.

[@JohnWasinger]

Don’t use nvim for capturing the results for long compilations. The open new tab then :r!make locks things up for a bit. I think that opening a new tmux pane would provide a better approach to this? Any suggestions?

[@takennmc]

ok i can put down the pitchfork

[@mrcrackerist]

I must say I disagree about the file management oil is very nice for moving a lot of files, but for terminal I just use ctrl-z instead of tmux.

[@zeocamo]

i use neogit for the git workflow, it is way better then lazygit when you learn to use it.

[@salsar7031]

in my setup i prefer save time. So for me neovim is the tool for "saving edit time" if i need commit i use lazygit in neovim leader gg and commit like normal lazygit if i need a file i use neotree if i need manage files i use ranger but if i need to move a file only 1 file i use neotree it realy depends on the job . tldr if the job is not editing and if its big i use an other tool if job can handle quicker in neovim than i dont change the pane and come back .

[@sitecocu]

Just in time I learned to use it on iOS development, now you saying don't use it!?? why man what should I learn now maannnn

[@JohnWasinger]

You used nvim to write the script for this video didn’t ya?

[@typecraft_dev]

I might've used notion

[@TakeThisLove]

No more hyprland? Gnome is good enough? :)

[@berkes]

Unix is my IDE

[@typecraft_dev]

Hell yeah brother

[@scippio2]

yeah. I'm using lazygit... in neovim...

[@danielratiu4318]

Beside sun screen BS all good and dandy. Peace Nerd.

[@DayviSchuster]

Lazygit can run within neovim, it's in lazy neovim by default IIRC. But everything else I fully agree with

[@yeshwanthkumar7764]

you can but it's quite messy... accidentally hit esc and you lose focus of the lazygit buffer and have to :q to exit out of it... lazygit is a lot better when run directly from the terminal

[@norbertbatiuk121]

@@yeshwanthkumar7764 Totally agree! personally, I've created keymap to a script that takes me from vim to lazygit (basically switching tmux pane). Thus, it "feels" as part of NeoVim but is handled completely by tmux.

[@DayviSchuster]

@@yeshwanthkumar7764 Yea it is, but counter point, if you run it from nvim, you get to keep your nice color scheme out of the box without changing the lazygit config. But nah I get the point. it can be cumbersome and finicky at times.

[@xalium]

just bind exit for lazygit to C-q? Imo, This argument can be extended to every overlay plugin

[@yeshwanthkumar7764]

@@xalium That's true too. I just don't want to add more non-default keybinds if I can avoid it. Helps keep the config overload minimal in my head. Having said that, no shade to the lazygit.nvim plugin though... It's pretty cool and I still use it occasionally. And it inheriting the nvim colorscheme as @DayviSchuster pointed out is pretty neat. I just don't default to it as much.