| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
No particular reason beyond preference; I think of these as properties
of the window itself, not the window-buffer pair, so it makes more sense
to me this way.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
From :help hidden-options:
>Not all options are supported in all versions. This depends on the
>supported features and sometimes on the system. A remark about this is
>in curly braces below. When an option is not supported it may still be
>set without getting an error, this is called a hidden option. You can't
>get the value of a hidden option though, it is not stored.
>
>To test if option "foo" can be used with ":set" use something like this:
> if exists('&foo')
>This also returns true for a hidden option. To test if option "foo" is
>really supported use something like this:
> if exists('+foo')
|
| | |
|
| |
|
|
| |
The name of this mapping was changed in commit 44bd9a8.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Including renaming big_file.vim and accompanying functions yet again, to
big_file_options.vim.
Trying to keep complex autocmd and mapping definitions on long lines
broken up semantically; definition and options on one line, patterns or
mapping key on the next, and the command to run on the last.
Also trying to make sure that <silent>, <buffer>, and <unique> are
applied in the correct places, and that all mapping commands are using
the :<C-U> idiom for the command prefix.
|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* feature/spin-vim-plug:
Rename toggle plugin again, use commands not funcs
Add short documentation for new custom plugins
Use same comment boilerplate for custom plugins
Check 'eval' feature for loading command_typos.vim
Wrap detect_background.vim func call in 'silent!'
Rename and refactor option toggle plugin
Don't suggest mappings in Vim plugin comments
Move Vim background detection logic into plugin
Specify an install-vim-autoload target
Spin 'fo' toggle out into new flag toggler plugin
Spin copyable linebreak config into new plugin
Spin stable join config out into new plugin
Use <Plug> prefix, make space strip configurable
Rename a misnamed variable in big_file.vim
Rename bigfile plugin to big_file
Move trailing space strip config into plugin
Separate command typos config to plugin
|
| | |
| |
| |
| |
| | |
Calling this one copy_linebreak.vim. Renamed both the internal function
and the plugin key.
|
| |/
|
|
|
|
|
| |
From ":help <LocalLeader>":
> In a global plugin <Leader> should be used and in a filetype plugin
> <LocalLeader>. "mapleader" and "maplocalleader" can be equal.
|
| |
|
|
| |
This was added in 52671ad, but not finished.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Using the very weird syntax:
:setlocal option! option?
We can toggle the option and print its new value in the same line. For
the line breaking options, we only show the value of the 'linebreak'
option, because otherwise we print three lines of messages, which
requires an <Enter> press, even if we put all three `option?` calls on
one :setlocal line.
|
| |
|
|
|
| |
Essentially just breaking up the big block comment at the top into
little pieces.
|
| |
|
|
|
|
| |
Because this is a version-based check and shouldn't change any runtime,
we can just calculate it once as a variable local and persistent to this
script, and then store it for reference by the toggling function.
|
| |
|
|
|
| |
It makes more sense to discuss how something wraps after configuring
whether it wraps at all.
|
| |
|
|
|
| |
Don't change the value of these options for all buffers with the \w and
\b maps, just the current one.
|
| |
|
|
|
|
| |
'linebreak', 'showbreak', 'breakindent', and 'breakindent' are only
relevant when 'wrap' is on, so it makes sense for their settings to be
grouped together.
|
| |
|
