| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* 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
|
| |
| |
| |
| |
| |
| | |
This method makes a bit more sense, and amounts to slightly less verbose
mapping commands. It does really on the +user_commands feature being
available, however.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I'm using the plugin_name.txt syntax suggested by the Vim documentation.
That may change in future as I study plugins written by experienced
authors like Tim Pope.
There will almost certainly be a lot more detail to add to each of
these.
|
| |
| |
| |
| | |
A brief explanation, an author name, and the license should do fine.
|
| |
| |
| |
| |
| | |
I strongly suspect the presence of 'user_commands' implies it, but I'm
not sure.
|
| |
| |
| |
| |
| |
| | |
This prevents older versions of Vim like 6.2 from throwing "E1017:
Missing braces" on merely parsing this code, even though they don't
evaluate it.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Renamed to flag_toggle.vim and placed in autoload using the namespaced
autoload function syntax.
I'm not sure this is the right approach yet, but I seem to pretty rarely
use a Vim earlier than 7.1 these days.
|
| |
| |
| |
| | |
Pretty useless, really.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is an experimental new plugin that provides a command to toggle
individual single-character flags in an option with a value of a set of
such flags, in my case 'formatoptions'.
A fair bit of evil eval()ing via :execute here, but I've tried to
control it with some strict patern matching.
|
| |
| |
| |
| |
| | |
Calling this one copy_linebreak.vim. Renamed both the internal function
and the plugin key.
|
| |
| |
| |
| |
| | |
Again using the <Plug> mapping abstraction and not defining the mapping
for the user.
|
| |
| |
| |
| |
| |
| | |
This properly abstracts out the StripTrailingWhitespace mapping rather
than forcing it to <leader>x within the plugin itself. A bit nicer this
way.
|
| |
| |
| |
| | |
The word "size" was added to this variable's name unnecesarily.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Just for consistency with the other plugins I'm making.
I don't think I really like the cutesy names given to Vim plugins. I
prefer the slightly longer and maybe even namespaced names like Perl
distributions and modules have. Let's see how well this works.
|
| | |
|
| |
| |
| |
| |
| | |
Tentatively named command_typos.vim. I've just moved this as-is for now,
but it will need review, especially the hardcoded mappings.
|
| |
| |
| |
| |
| | |
This was causing a tiny build of Vim to raise errors about :let being
an unavailable command.
|
| |
| |
| |
| | |
Runs `vint -s`; the -s includes stylistic suggestions.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`vint -s` says:
vim/config/leader.vim:2:5: Make the scope explicit like
`g:mapleader` (see Anti-pattern of vimrc (Scope of identifier))
vim/config/leader.vim:3:5: Make the scope explicit like
`g:maplocalleader` (see Anti-pattern of vimrc (Scope of identifier))
This does still seem to work with the prefixes, despite not being the
way the documentation specifies the variables.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This should allow me to mentally separate actions specific to a buffer
type from actions that apply to buffers in general. It also removes the
overlap of <leader>l for 'list' toggling and filetype linting.
From ":help maplocalleader":
> <LocalLeader> is just like <Leader>, except that it uses
> "maplocalleader" instead of "mapleader". <LocalLeader> is to be used
> for mappings which are local to a buffer. Example:
>
> :map <buffer> <LocalLeader>A oanother line<Esc>
>
> In a global plugin <Leader> should be used and in a filetype plugin
> <LocalLeader>. "mapleader" and "maplocalleader" can be equal.
> Although, if you make them different, there is a smaller chance of
> mappings from global plugins to clash with mappings for filetype
> plugins. For example, you could keep "mapleader" at the default
> backslash, and set "maplocalleader" to an underscore.
|
| |
| |
| |
| |
| | |
The commands to use in this case are dependent on the particular shell
being used.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This mapping mirrors the one for Perl that passes the content of the
buffer through a program to tidy it (i.e. not merely check but actively
change it).
The tidy(1) option chosen here, -quiet, is the bare minimum to make this
invocation useful. We would never want the boilerplate it otherwise
emits to be in the buffer after a call. Everything else should be
applied in a configuration file, which I'll do in a separate feature.
|
| | |
|
| |
| |
| |
| |
| |
| | |
That is, apply <buffer> and <silent> to each of them, to make them only
apply to the current buffer and to prevent them from echoing the command
they're running.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a much better method of calling external programs on the
buffer's contents, not just because it avoids the mess of :execute
evaluation but also because it doesn't require that there actually be a
filename for the current buffer.
This drastically simplifies the HTML tidy(1) call in particular.
|
| |
| |
| |
| | |
We should probably avoid this sort of abbreviation in scripts.
|
| |
| |
| |
| |
| | |
It doesn't seem to be in very old Vims; worth testing for to avoid
errors if I try to use the function.
|
| |
| |
| |
| |
| |
| |
| |
| | |
I thought text objects were introduced to Vim a lot later than they
actually were; this works fine even in Vim 6, so I'll leave it as it's
nicer.
This reverts commit ffb5cbc7c681e2fdcb780dbdc51cf3458a937791.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Tidy up the 'normal!' commands and comment them in appropriate groups.
Take advantage of the natural command-termination at the end of a
'normal!' string to end insert mode.
It would be better to do all of this with pure VimL functions, but I
don't know how yet.
|
| |
| |
| |
| | |
Saves some backslashing, just like in shell and Perl!
|
| |
| |
| |
| |
| | |
Move the logic into a script function. Use single quotes for the
strings, too, since we don't need interpolation.
|
| |
| |
| |
| |
| |
| |
| | |
From ":help <LocalLeader>":
> In a global plugin <Leader> should be used and in a filetype plugin
> <LocalLeader>. "mapleader" and "maplocalleader" can be equal.
|
|\ \
| | |
| | |
| | |
| | |
| | | |
* hotfix/v0.4.2:
Require eval feature for netrw opts assignment
Bump version number to 0.4.2
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Tiny builds of Vim that exclude the eval feature throw errors at the
:let commands in this file:
$ vim.tiny
Error detected while processing /home/tom/.vim/config/netrw.vim:
line 2:
E319: Sorry, the command is not available in this version: let g:netrw_banner = 0
line 5:
E319: Sorry, the command is not available in this version: let g:netrw_silent = 1
line 8:
E319: Sorry, the command is not available in this version: let g:netrw_liststyle = 3
line 11:
E319: Sorry, the command is not available in this version: let g:netrw_list_hide = '^\.$,^tags$'
Press ENTER or type command to continue
This code was not being run on such builds before commit 538b71c,
because it was in an "after" directory for the netrw plugin and would
have been skipped.
Wrapping a check for has('eval') around this whole file fixes the
problem. netrw.vim won't run without this feature anyway.
|
|\| |
| |/
|/|
| |
| |
| | |
* hotfix/v0.4.1:
Don't show search option state on mode changes
Bump version number to 0.4.1
|
| |
| |
| |
| |
| |
| |
| | |
Commit 92f2c78 added these suffixes to the option settings to show the
value of the option after it had been set, but this isn't actually
appropriate for the autocmd here; it means the value of 'hlsearch' is
echoed every time insert mode is entered or left.
|
|/
|
|
|
| |
Looks like this was added in a1ee04d for v0.4.0 and was intended to
replace the file in its correct path at vim/config/comment.vim.
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* feature/vim-plugin:
Have bigfileturn local syntax off (configurably)
Make bigfile 'synmaxcol' setting configurable
Refactor plugin function for dependency injection
Rename variable and autocmd to use plugin prefix
Make bigfile size variable an option with default
Expand comment header for bigfile.vim
Move Vim big file options config into plugin
|
| | |
|
| |
| |
| |
| |
| | |
Defaults to 256 columns and only sets it if the option's value isn't
already lower than that.
|
| |
| |
| |
| |
| |
| |
| | |
Pass the filename to check and the size limit into the function directly
from the autocmd hook.
Improve commenting and spacing as we go.
|
| |
| |
| |
| |
| |
| | |
Just removing an underscore from the variable name so that
g:big_file_size becomes g:bigfile_size, and remove the "dotfiles" prefix
from the autocmd.
|
| |
| |
| |
| |
| | |
This arranges for g:big_file_size only to set itself to 10 MiB if the
variable is not already set, presumably by the user in their vimrc.
|
| |
| |
| |
| | |
Include some author and license metadata.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Created targets install-vim-doc and install-vim-plugin with accompanying
subdirectories of "vim".
Added a very short summary of what the plugin does to bigfile.txt.
I intend to spin off at least a couple of the blocks of my Vim
configuration that are starting to coalesce into distinct plugins unto
themselves, and will place the files in these directories.
|
| |
| |
| |
| |
| | |
Since it pertains to the casing of text, and there are potentially other
items that could go in here too.
|