Mercurial > vim
view runtime/ftplugin/mrxvtrc.vim @ 23750:d98dcbc57f7f v8.2.2416
patch 8.2.2416: may get stuck in command line window state
Commit: https://github.com/vim/vim/commit/bed72df3e61a8908ed6324212595118f305dded0
Author: Bram Moolenaar <Bram@vim.org>
Date: Wed Jan 27 20:34:29 2021 +0100
patch 8.2.2416: may get stuck in command line window state
Problem: May get stuck in command line window state.
Solution: Reset "cmdwin_type" when editing buffer fails. Make arglist test
pass on MS-Windows.
| author | Bram Moolenaar <Bram@vim.org> |
|---|---|
| date | Wed, 27 Jan 2021 20:45:04 +0100 |
| parents | 2ad54fcf37e3 |
| children |
line wrap: on
line source
" Created : Wed 26 Apr 2006 01:20:53 AM CDT " Modified : Fri 28 Apr 2006 03:24:01 AM CDT " Author : Gautam Iyer <gi1242@users.sourceforge.net> " Description : ftplugin for mrxvtrc if exists("b:did_ftplugin") finish endif let b:did_ftplugin = 1 let b:undo_ftplugin = "setl com< cms< fo<" " Really any line that does not match an option is a comment. But use '!' for " compatibility with x-defaults files, and "#" (preferred) for compatibility " with all other config files. " " Comments beginning with "#" are preferred because Vim will not flag the " first word as a spelling error if it is not capitalised. The '!' used as " comment leaders makes Vim think that every comment line is a new sentence. setlocal comments=:!,:# commentstring=#\ %s setlocal formatoptions-=t formatoptions+=croql