Re: I had to replace gvim with neovim
Rory Campbell-Lange <[email protected]>
| Newsgroups | gmane.editors.vim |
|---|---|
| Message-ID | <[email protected]> |
On 28/02/24, Steve Litt ([email protected]) wrote: > Gary Johnson said on Wed, 28 Feb 2024 06:45:04 -0800 > > >On 2024-02-28, Steve Litt wrote: > >> The gvim program became too much of a hassle because it printed all > >> sorts of GTk errors and warnings to the terminal > > Try starting gvim this way and see if the warnings go away. > > > > $ gvim 2> /dev/null > > Thanks Gary, I should have thought of that. I followed your advice and > renamed /usr/bin/gvim to gvim.warnings, and then made a shellscript > called gvim to call it, piping stderr to /dev/null. Have you considered using console vim (eg vim-nox on Debian)? One is unlikely to get any GTk errors with that. -- -- You received this message from the "vim_use" 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_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/ZeYtUnANXBPozaXd%40campbell-lange.net.