| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| | |
* feature/vim-mutt-plug:
Move mutt_mail.vim line select logic into plugin
Add new mail_mutt.vim plugin, apply mappings
Beginnings of a buffer-to-Mutt mailer plugin
|
| |
| |
| |
| | |
This makes the configuration shorter and easier to read.
|
| |
| |
| |
| |
| | |
This plugin provides a shortcut for staring email messages in Mutt with
a range of lines.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
These flags prevent multiple messages from reading or writing multiple
files from queuing up and forcing an enter prompt. They're part of the
default, which is why I didn't notice their absence until I tried using
the setting previous to this commit and opened two files at once.
|
| |
| |
| |
| |
| | |
Most of these are actually the default; may as well explicitly set and
document them, however. t and T in particular are new.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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')
|
| | |
|
| | |
|
| |
| |
| |
| | |
For plugin-specific configuration.
|
| |
| |
| |
| |
| | |
This will allow the Windows-specific stuff in my new auto_* plugins to
quote filenames correctly.
|
| |
| |
| |
| | |
For OS-dependent config.
|
| |
| |
| |
| | |
I never use it. May as well defer to the vi default.
|
| | |
|
| |
| |
| |
| | |
'paste' is specific to the terminal only anyway.
|
| | |
|
| |
| |
| |
| | |
Clearer filename and more consistent to use the noun.
|
| |
| |
| |
| | |
A little clearer and a needless abbreviation anyway.
|
| |
| |
| |
| | |
More likely to share options this way.
|
| | |
|
| |
| |
| |
| |
| | |
More accurate given the content, and more likely to have other options
set in it.
|
| | |
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
| |
:help 'tabstop' says that setting it may be a bad idea:
> Note: Setting 'tabstop' to any other value than 8 can make your file
> appear wrong in many places (e.g., when printing it).
On thinking about it, it's actually probably better to show literal tabs
as eight screen spaces, as it will make it very obvious when there are
tabs in the file.
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* feature/vim-plug:
Add user_ftplugin.vim and user_indent.vim plugins
Use b:undo variables correctly
Update <Leader>b mapping to use new mapping name
Add commands to copy_linebreak.vim
Give copy_linebreak.vim enable/disable funcs, maps
Add :FixedJoin command
Add :StripTrailingWhitespace command
|
| |
| |
| |
| | |
The name of this mapping was changed in commit 44bd9a8.
|
| |
| |
| |
| |
| |
| | |
I think this option has become overloaded in recent versions and that
these would make more sense and be more manageable as separate but
interacting options.
|
| |
| |
| |
| | |
\d adds local time, \D adds UTC time.
|
|/ |
|
|
|
|
|
| |
We'll let toggle_option_flags.vim raise the errors, and we won't bother
with the version number testing.
|
|
|
|
|
|
|
|
| |
From what I understand from ":help if", ancient Vim and/or vim-tiny
without the 'eval' feature will simply gloss over all commands between
:if and :endif without executing them. Therefore as soon as we test a
version, we're implicitly excluding everything that doesn't have 'eval'
anyway.
|
|
|
|
| |
May as well refer to the actual command I'm using.
|
|
|
|
|
|
|
|
|
|
|
| |
The Google VimScript Guide says:
<https://google.github.io/styleguide/vimscriptfull.xml#Portability>
> Always use case-explicit operators for strings (=~# and =~?, never =~).
>
> This also applies to !~ == != > >= < and <=
> This only applies for strings. == and >= are fine for numbers, but ==#
> and >=# must be used for strings.
|
|
|
|
| |
This approach allows more flexibility from the caller's side.
|
|
|
|
| |
Just to keep related things together.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
:help version6.txt, /^Patch 6\.1\.142:
> Patch 6.1.142
> Problem: Defining paragraphs without a separating blank line isn't
> possible. Paragraphs can't be formatted automatically.
> Solution: Allow defining paragraphs with lines that end in white
> space. Added the 'w' and 'a' flags in 'formatoptions'.
> Files: runtime/doc/change.txt, src/edit.c, src/misc1.c,
> src/normal.c, src/option.h, src/ops.c, src/proto/edit.pro,
> src/proto/ops.pro, src/vim.h
|
|
|
|
|
|
| |
Put in appropriate 'eval' checks and adjust the order of evaluation so
that vim-tiny doesn't try to run all this and fail due to the absence of
'eval' for :let.
|
|
|
|
|
| |
This is implemented in the same way as done for 'fo'-'a'; testing for
the presence of the flag based on known version tests first.
|
|
|
|
|
| |
A bit clearer as the mapping was clearly called in error, and results in
not being able to do what was need.
|
| |
|
|
|
|
| |
Use the result to decide how to map <Leader>a.
|
|
|
|
| |
We'll use this in a subsequent commit to decide how to map <Leader>j.
|
|
|
|
| |
I have found it works correctly on an instance of Vim 7.0.
|
|
|
|
|
| |
If I ever care, this needs more careful testing to find the version in
which the flag was added.
|
|
|
|
| |
'InsertEnter' and 'InsertLeave' are not autocmd events in Vim 6.1.
|
|
|
|
|
|
| |
'vnoremap' also includes select mode, which I very seldom use anyway; in
this context it's not worth breaking compatibility with old Vims to use
the more accurate 'xnoremap'.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|