Mercurial > vim
view runtime/ftplugin/mrxvtrc.vim @ 23810:8152b7daebad v8.2.2446
patch 8.2.2446: setting 'term' empty has different error if compiled with GUI
Commit: https://github.com/vim/vim/commit/5daa91162699e4f8b54f9d1caaaab2715038941c
Author: Bram Moolenaar <Bram@vim.org>
Date: Mon Feb 1 18:39:47 2021 +0100
patch 8.2.2446: setting 'term' empty has different error if compiled with GUI
Problem: Setting 'term' empty has different error if compiled with GUI.
Solution: Insert "else". (closes https://github.com/vim/vim/issues/7766)
| author | Bram Moolenaar <Bram@vim.org> |
|---|---|
| date | Mon, 01 Feb 2021 18:45:06 +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