Most "full" GUIs (programs which can be used _only_ as GUIs) respond in very similar manner to similar commands: on Linux, Ctrl-Q, and often but less reliably clicking the [x] at the end of the window titlebar, will make them exit gracefully.
For interactive console programs it is different: to exit bash you type exit<Enter>, which brings you back to the calling shell if there was one, or logs you out if there wasn't. To exit Lynx you hit q to exit with an are-you-sure prompt, or Q to exit immediately. To exit ftp you type quit<Enter> or exit<Enter> or bye<Enter> Vim is both a GUI and a console program and runs identically in both; in fact I suspect that Vim (and vi) were developed first as console editors, and that GUI mode was added afterwards, which explains why gvim could be regarded as a console-mode program running in its own GUI-like console. So you exit gvim or vim the same way, and it happens to be :qa<Enter> (which will prompt you if you have unsaved files) or :qa!<Enter> (if you want to |abandon| anything unsaved). In order to use Vim efficiently, you have to learn how to. For this, you need a willingness to run the vimtutor suite and enough curiosity to peruse the online help (which is the best available help system for personal computer utilities AFAIK). Vim was developed over the years, based on Vi which evolved over previous years from a time when the usual interface with a computer was a teletype console which could not move backward. So it has it own quirks, which, after some time, feel "natural" to people who have taken the time to learn them. So what if Vim behaves differently than Notepad or geditf course it does! It can do a lot of things that Notepad or gedit cannot, so it's just natural that it should be different. Best regards, Tony. On Fri, May 26, 2017 at 6:45 AM, vim-dev ML <[email protected]> wrote: > Why can't you use nano like other people who don't understand vi or vim? > > On Thu, 25 May 2017, R0b0t1 wrote: > >> I hate to beat a dead horse, but this analysis of the question is >> rather interesting: >> >> https://stackoverflow.blog/2017/05/23/stack-overflow-helping-one-million-developers-exit-vim/. >> >> It seems like it supports the idea that despite the question's >> popularity, most people can figure out how to exit the editor and it >> is only certain demographics that have problems with the editor. >> However, they still find the answer. >> >> A far more interesting but harder to find statistic is how many people >> resort to closing the terminal emulator or killing the vim process >> from another virtual terminal. I have heard of this happening but the >> number is likely vanishingly small. >> >> > > -- > Hisashi T Fujinaka - [email protected] > BSEE + BSChem + BAEnglish + MSCS + $2.50 = coffee > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > > -- > -- > You received this message from the "vim_dev" maillist. > Do not top-post! Type your reply below the text you are replying to. > For more information, visit http://www.vim.org/maillist.php > > --- > You received this message because you are subscribed to the Google Groups > "vim_dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
