buffer close but quit on last buffer

[ghost]

I mapped
q = ":buffer-close"
Q = ":buffer-close!"
but when i am pressing q while it is on last buffer, helix is creating a new scratch buffer removing the original one

[woojiq]

I think this is a useless improvement as there are other commands like qa for your purposes. Imagine that you are writing something in a editor with gui (for example, vscode). If you want to exit completely, you press the top X button and do not close all open files one by one. Same thing: quit-all is your GUI X button and buffer-close is the X next to the file name. You do not close the program, if you have closed all the files, the welcome screen just opens.

Also, if it was the last buffer and you didn't notice, you can simply open another file and the lsp will continue to work. However with your suggestion, you will have to wait tens of seconds again to wait the lsp.

[ghost]

Yeah I know, there is quit-all command but typing out commands is slow and boring
I use z for write and q for quit if I used the mannual way I would have used esc : w q ret and a sometimes to quit all

[gabydd]

The above explains why this is the intended behaviour well, I will convert this to discussion so you can discuss alternatives but I don't think we want to change the behaviour of buffer-close, those commands are for managing open buffers changing it shouldn't quit the editor that's better left for other commands

[ghost]

I am not saying to change the behaviour of buffer-close, just add another command like buffer-close-and-quit and also same for force quit buffer-close-and-quit!. It will work very similar to less command if you map buffer-close-and-quit to q

[Cloudef]

I'd love to have this too. Just recently moved to hx from vim/neovim and even on there having this feature cleanly is annoying (but doable).