Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should be everything for 1.2 #98

Merged
merged 43 commits into from
Aug 27, 2017
Merged

Should be everything for 1.2 #98

merged 43 commits into from
Aug 27, 2017

Conversation

benknoble
Copy link
Owner

@benknoble benknoble commented Aug 27, 2017

Description

See the commits

Related Issue

All the ones covered by commits/1.2

Motivation and Context

Part of 1.2 feature set

How Has This Been Tested?

Used by me daily

Behavior

It behaves. I've never had to punish it.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have tested my feature as described in CONTRIBUTING.

Give mappings a 3s timeout.

Learn Vimscript Hardway
Learn Vimscript Hardway
With Q mapped to gq, pressing QQ quickly (forgetting to let go of shift)
causes vim to gqQ, which is NOT gqq or gqgq (format line). Simple fix.

Learn Vimscript Hardway
Learn Vimscript Hardway
Cursorline makes it quite difficult to see some of the things I am
typing while in insert mode, and at any rate I shouldn't really lose the
cursor while I'm typing text.

Solution: autocommands
Indirectly related to 3892a30, keeping marks
cf. 8ae938c -- Caused some issues when typing <Space>p in Insert mode
Prelim work on fixing my autofold feature

This should probably eventually turn into it's own plugin.
The pattern ?* requires there to be an actual character in the filename,
I believe, as it wasn't matching when I do :new.

The fix to reset belloff was that I simply didn't understand eval option
syntax.
Now it has parameters that control what to set foldcolumn to, and
returns the value for you to use rather than setting foldcolumn itself.

This could be extended into a plugin Auto Fold Column, with autoloaded functions
that detect folds, return the right values (based on global variables,
options passed in, and sane defaults), and easy to set up with a simple

:call AutoFoldColumn() " Use defaults or global vars
:call AutoFoldColumn(col, def) " Use the variables passed in

AutoFoldColumn would set up the auto command.

Need to google if Vim has a concept of default parameters.
No need to show fancy whitespace in man pages

Had to be in the after directory, because otherwise runtime
ftplugin/man.vim would catch my plugin, rather than the vim distro
plugin.
Fix #92

All "augroups" defined in my vimrc are now prefixed with
vimrc_$groupname, to make them easier to identify if needed later. They
are also organized more topically.
So I can more easily work with C files (hopefully)
Like things in/around () and {}

Learn Vimscript Hardway
Learn Vimscript Hardway
This gets really annoying when you want to follow links
Learn Vimscript Hardway
Triggered with <Leader>g, greps for the text covered by the motion in
the current project

Learn Vimscript Hardway
cn and cp are also mapped with Leader, so cl is easier than c by itself
@benknoble benknoble self-assigned this Aug 27, 2017
@benknoble benknoble added the vim label Aug 27, 2017
@benknoble benknoble added this to the Version 1.2 milestone Aug 27, 2017
@benknoble benknoble merged commit d5e70bb into dev-1.2 Aug 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant