aboutsummaryrefslogtreecommitdiff
path: root/vim/ftplugin
Commit message (Collapse)AuthorAgeFilesLines
* Use case-sensitive operators to appease vim-vintTom Ryder2019-05-231-3/+3
|
* Add foldexpr function deletion to undoTom Ryder2019-05-231-1/+1
|
* Give credit to Tim PopeTom Ryder2019-05-231-2/+2
|
* Adopt heading-based Markdown foldingTom Ryder2019-05-231-15/+13
| | | | | | This is just me adapting Tim Pope's original code a little to fit with how I normally write Vim script. We'll try this fold method out and see if it suits.
* Remove redundancies from 'formatoptions' settingTom Ryder2019-05-231-3/+1
|
* Break apart 'comments' definitionsTom Ryder2019-05-231-2/+5
|
* Use variable assignment for complex patternTom Ryder2019-05-231-1/+1
|
* Correct definition for b:undo_ftpluginTom Ryder2019-05-231-1/+1
|
* Refactor undo_ftplugin lines for Markdown ftpluginTom Ryder2019-05-231-6/+2
|
* Break up Markdown ftplugin option settingsTom Ryder2019-05-231-2/+8
| | | | Just for readability.
* Adjust header/footer for Markdown ftpluginTom Ryder2019-05-231-7/+3
|
* Remove HTML ftplugin import from Markdown ftpluginTom Ryder2019-05-231-2/+0
| | | | | I never liked this much. Removing it from my own copy of the ftplugin allows me to remove my working around it in the after script.
* Move my after ftplugin for Markdown into mainTom Ryder2019-05-231-0/+44
|
* Add Tim Pope's Markdown ftpluginTom Ryder2019-05-231-0/+50
| | | | | | I disagree with just enough of this that I think it's worth writing it out my own way. Adding the file as it is for now so I can track and document what I change.
* Replace text.vim ftplugin entirelyTom Ryder2019-05-111-5/+8
| | | | | This makes more sense than dancing around the potential availability of the stock one.
* Set up custom ftplugin for plain text filesTom Ryder2019-05-111-0/+14
|
* Remove unnecessary g: prefixes to Vim variablesTom Ryder2019-05-091-1/+1
|
* Remove unneeded leading pipe from b:undo_ftpluginTom Ryder2019-03-281-1/+1
|
* Add textarea filetypeTom Ryder2019-03-281-0/+10
| | | | | | | | This custom filetype is just a hook to hang functionality for TextEditorAnywhere documents under Windows. Most of the time, it's me writing email, or comments that benefit from email formatting, so I've configured <LocalLeader>f to switch to the mail filetype. This switching could probably benefit from a plugin, actually.
* Choose regex character classes for some filetypesTom Ryder2018-12-291-0/+4
|
* Set b:did_ftplugin flag in Vim ftpluginsTom Ryder2018-11-296-0/+6
|
* Add missing left angle bracket to filetype undoTom Ryder2018-11-141-1/+1
|
* Add my own ftplugin for awkTom Ryder2018-07-171-0/+9
| | | | | An official one only got added in early 2016, and it does almost nothing; may as well implement my own instead.
* Add ftplugin for tmuxTom Ryder2018-07-121-0/+9
| | | | | Just with comment formatting rules--there's no stock ftplugin in Vim at the moment, just a syntax file.
* Move after/ftplugin/sed.vim to ftplugin/sed.vimTom Ryder2018-07-101-0/+9
| | | | | Vim doesn't have a stock ftplugin for sed at all (just syntax), so this can be our base one.
* Clean up existing ftplugins a bitTom Ryder2018-07-103-5/+9
|
* Add comments to vim ftpluginsTom Ryder2018-06-303-0/+9
|
* Add CSV, TSV, and password file filetypesTom Ryder2018-06-303-0/+15
|
* Remove ftplugin overrides for html/markdownTom Ryder2018-06-302-10/+0
| | | | No longer needed
* Review vim/ftplugin and vim/indent filesTom Ryder2018-06-302-51/+2
|
* Correct Vim 'formatlistpat' def for MarkdownTom Ryder2018-06-231-2/+2
|
* Correct an exists() call in markdown ftpluginTom Ryder2018-06-231-1/+1
| | | | Evidently copy-pasted from documentation.
* Consistently require 'nocompatible' for ftpluginsTom Ryder2018-06-162-26/+2
|
* Check for 'formatlistpat' option existenceTom Ryder2018-06-061-3/+5
|
* Restore ftplugin extras to vim/after dirTom Ryder2018-06-053-186/+0
| | | | | This reverts commit a14bc50. Changed my mind; decided it's tidier this way.
* Add ftplugin infrastructure and commentsTom Ryder2018-06-051-6/+16
| | | | Preparing for spinoff release
* Add global options for markdown_autoformat.vimTom Ryder2018-06-051-13/+19
|
* Use += shorthand in Vim ftpluginTom Ryder2018-06-051-1/+1
| | | | | We're already very dependent on Vim >=7 for this ftplugin, so we may as well use all its syntactic sugar.
* Pass in mapped key directly, not a flagTom Ryder2018-06-051-8/+4
| | | | This seems obvious now.
* Use correct function for function existence checkTom Ryder2018-06-041-3/+3
|
* Move Markdown and PHP ftplugins from after dirTom Ryder2018-06-043-0/+174
| | | | | | | Because we use our own private copies of the primary filetype plugins, they'll get loaded in the correct order from here. Also adjust Makefile to accommodate the extra level.
* Make private copy of ftplugin/markdown.vimTom Ryder2018-06-041-0/+43
|
* Correct a comment in ftplugin/php.vimTom Ryder2018-06-041-1/+1
|
* Replace ftplugin/php.vim with custom versionTom Ryder2018-02-011-0/+38
| | | | | | | Per the comment in the new file, this is to avoid loading in HTML ftplugins as well, a curiosity of the stock ftplugin/php.vim file that's probably a well-intentioned way of accommodating templated files with a mix of PHP and HTML in them.
* Move lots of local Vim config into vim/afterTom Ryder2017-11-127-141/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a relatively drastic change that should have been done progressively, but I got carried away in ripping everything out and putting it back in again. Reading the documentation for writing a Vim script (:help usr_41.txt), I am convinced that all of the content that was in the vim/ftplugin directory and some of the vim/indent directory actually belonged in vim/after/ftplugin and vim/after/indent respectively. This is because the section on filetypes makes the distinction between replacing the core filetype or indent plugins and merely adding to or editing them after the fact; from :help ftplugin: > If you do want to use the default plugin, but overrule one of the > settings, you can write the different setting in a script: > > setlocal textwidth=70 > > Now write this in the "after" directory, so that it gets sourced after > the distributed "vim.vim" ftplugin after-directory. For Unix this > would be "~/.vim/after/ftplugin/vim.vim". Note that the default > plugin will have set "b:did_ftplugin", but it is ignored here. Therefore, I have deleted the user_indent.vim and user_ftplugin.vim plugins and their documentation that I wrote, and their ftplugin.vim and indent.vim shims in ~/.vim, in an attempt to make these plugins elegantly undo-ready, and instead embraced the way the documentation and $VIMRUNTIME structure seems to suggest. I broke the ftplugin files up by function and put them under subdirectories of vim/after named by filetype, as the 'runtimepath' layout permits. In doing so, I also carefully applied the documentation's advice: * Short-circuiting repeated loads * Checking for existing mappings using the <Plug> prefix approach * Avoiding repeated function declarations overwriting each other * Guarding against 'cpotions' mangling things (by simply short-circuiting if 'compatible' is set). I've made the b:undo_ftplugin and b:undo_indent commands less forgiving, and append commands to it inline with the initial establishment of the setup they're reversing, including checking that the b:undo_* variable actually exists in the first place. For the indentation scripts, however, three of the four files originally in vim/indent actually do belong there: 1. csv.vim, because it doesn't have an indent file in the core. 2. tsv.vim, because it doesn't have an indent file in the core. 3. php.vim, because it does what ftplugins are allowed to do in preventing the core indent rules from running at all. The indent/vim.vim rules, however, have been moved to after/indent/vim.vim, because the tweaks it makes for two-space indentation are designed to supplement the core indent rules, not replace them. Finally, I've adjusted Makefile targets accordingly for the above, given the vim/ftplugin directory is now empty and there are three new directories in vim/after to install. We wrap these under a single `install-vim-after` parent target for convenience. The `install-vim-after-ftplugin` target accommodates the additional level of filetype directories beneath it.
* Correct prefix for b:undo_* variableTom Ryder2017-11-081-1/+1
| | | | This was causing nasty errors whenever I started editing a Perl file.
* Use "nunmap" not "unmap" for b:undo_* varTom Ryder2017-11-082-5/+5
| | | | We only want to remove the normal mode mapping, since that's all we set.
* Remove null command from b:undo_* variablesTom Ryder2017-11-083-6/+6
| | | | | I didn't realise that a null command at the front of .e.g '|cmd|cmd2' printed the current line! Removed that.
* Use consistent/thorough ftplugin/indent unloadingTom Ryder2017-11-087-7/+32
| | | | Unload all maps too, with silent! in case they don't exist.
* Break a long conditional in vim/ftdetect/sh.vimTom Ryder2017-11-081-1/+2
| | | | Just for legibility.
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-25 09:01:50 +0000