6 ms·

I generally recommend to exit either via :xa (save all & exit) or :qa! (discard all and exit), bound to ZZ or ZA respectively. If you exit via :q or :wq, it jus

I generally recommend to exit either via :xa (save all & exit) or :qa! (discard all and exit), bound to ZZ or ZA respectively. If you exit via :q or :wq, it just closes the current buffer, and moves to the next one. E.g. if you have a neotree open along with the editor, you type :wq, it closes the editor buffer and moves you into the file tree, which can be very confusing for beginners.

pwillia7 1y ago
just do :wq :wq :wq :wq etc :P
- Izkata 1y ago
  :wqa is the same as :xa and is probably easier to remember
  - opan 1y ago
    Are you sure? IIRC :x only writes the file again if there's a change where :w(q) always writes again (which takes longer when editing a remote file via scp://). For a non-exiting version of :x there is :up. I bound :up to <leader>fs after I learned about it. I used to have :w on the same keybind so it was a straight upgrade. Now I can just quick hit it at any time and there's no waiting around if the file hadn't changed. Saves some time and annoyances.
    - Izkata 1y ago
      Yes, through ":help wqa" which lists it as such and double checking with a quick test. It doesn't write unchanged files, same as :xa instead of being an exact "all" version of :wq
- MikeTheGreat 1y ago
  What does the :P command do? /s
  - nthdeui 1y ago
    :P :Print :[range]P[rint] [count] [flags] Just as ":print". Was apparently added to Vi for people that keep the shift key pressed too long... This command is not supported in Vim9 script. Note: A user command can overrule this command. See ex-flags for [flags].
- yakshaving_jgt 1y ago
  Noooooooo! Make some key bindings. Bind leader to space, and make a leader mapping for writing to the file, and another mapping to quit. Avoid chords.
- johnisgood 1y ago
  That is what I do. I thought I was the only genius.
- mmahemoff 1y ago
  Or do ZZZZZZZZZZ
nurple 1y ago
Neotree `close_if_last_window` config setting is helpful for this case.
prmoustache 1y ago
There are cases where you would not necessarily want to save all buffers. To me it is an eletrical term.

pwillia7 1y ago

just do :wq :wq :wq :wq etc :P

Izkata 1y ago
:wqa is the same as :xa and is probably easier to remember
- opan 1y ago
  Are you sure? IIRC :x only writes the file again if there's a change where :w(q) always writes again (which takes longer when editing a remote file via scp://). For a non-exiting version of :x there is :up. I bound :up to <leader>fs after I learned about it. I used to have :w on the same keybind so it was a straight upgrade. Now I can just quick hit it at any time and there's no waiting around if the file hadn't changed. Saves some time and annoyances.
  - Izkata 1y ago
    Yes, through ":help wqa" which lists it as such and double checking with a quick test. It doesn't write unchanged files, same as :xa instead of being an exact "all" version of :wq
MikeTheGreat 1y ago
What does the :P command do? /s
- nthdeui 1y ago
  :P :Print :[range]P[rint] [count] [flags] Just as ":print". Was apparently added to Vi for people that keep the shift key pressed too long... This command is not supported in Vim9 script. Note: A user command can overrule this command. See ex-flags for [flags].
yakshaving_jgt 1y ago
Noooooooo! Make some key bindings. Bind leader to space, and make a leader mapping for writing to the file, and another mapping to quit. Avoid chords.
johnisgood 1y ago
That is what I do. I thought I was the only genius.
mmahemoff 1y ago
Or do ZZZZZZZZZZ

nurple 1y ago

Neotree `close_if_last_window` config setting is helpful for this case.

prmoustache 1y ago

There are cases where you would not necessarily want to save all buffers. To me it is an eletrical term.