-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
README enhancements #1547
README enhancements #1547
Conversation
Can you add the recent lightline plugin information? Sorry I think I added that since you branched :) |
3a84a7c
to
aa1aed8
Compare
@xconverge Are you talking about the status bar colors? That's in there, but under Settings. I didn't want to put it under 'Emulated plugins', as the other under emulated plugins have really good feature parity. Happy to move it if you want, but I thought it could be a bit misleading. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR!
@@ -1,19 +1,35 @@ | |||
# Vim [![Version](http://vsmarketplacebadge.apphb.com/version/vscodevim.vim.svg)](http://aka.ms/vscodevim) [![Build Status](https://travis-ci.org/VSCodeVim/Vim.svg?branch=master)](https://travis-ci.org/VSCodeVim/Vim) [![Slack Status](https://vscodevim-slackin.azurewebsites.net/badge.svg)](https://vscodevim-slackin.azurewebsites.net) | |||
<h1 align="center"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not a big fan of embedding HTML into the markdown
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea I get it's not ideal from purity standpoint, but we're not the first to do this.
It's supported by Github and the VSCode marketplace.
README.md
Outdated
## Special Shoutouts to Cool Contributors | ||
## F.A.Q. | ||
|
||
### `j`, `k` and others keys don't repeat when I hold them down. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You had this covered in the Mac setup? Maybe delete it from here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought it might be be worth leaving it duplicated for a little while? I know I've linked to this section before getting friends up-to-speed. Happy to remove though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or reference a link to the Mac setup.
|
||
## Configuring VSCodeVim | ||
* [Quick example settings](#quick-example-settings) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think quick example settings
should fall under the settings
category.
Mac/Windows setup could be under it's own setup
/getting started category.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea good idea, I knew this section was 'off'. I'll move the quick settings into Settings, and rename this to 'Getting started', and might even include some links to some vim learning resources?
|
||
VSCodeVim is a [Visual Studio Code](https://code.visualstudio.com/) extension that enables Vim keybindings, including: | ||
|
||
* Modes: normal, insert, command, visual, visual line, visual block (with `useCtrlKeys`, see below) | ||
* Modes: normal, insert, command-line, visual, visual line, visual block |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we may want to use command
, AFAIK it's referring to ex-command.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I changed it in case there was any confusion with the next point: "Command combinations". It's also called command-line mode in the vim docs.
@@ -51,14 +87,14 @@ Below is an example of a [settings.json](https://code.visualstudio.com/Docs/cust | |||
"after": ["d", "d"] | |||
}, | |||
{ | |||
"before":["<C-n>"], | |||
"after":[], | |||
"before":["<C-n>"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's keep using 2 spaces.
] | ||
} | ||
{ | ||
"before": [":"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same here, I suppose it's changed by some indenting or formatting?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The indentation was all whacky, I re-indented it all so it was consistent. (I think there was 3 spaces here)
Just a few tiny suggestions, it looks good to me and it's way way awesome. |
Also, while you are at this, mind taking care of this? #1466 |
Ok pushed a few extra bits:
|
One last thing, mind squashing? |
We can squash when we merge too...not a big deal |
README.md
Outdated
|
||
### Vim compatibility | ||
|
||
All common Vim commands are supported. For an in-depth look at what Vim features are supported, check out the [roadmap](ROADMAP.md). Vimscript isn't supported, so you aren't able to load your `.vimrc` or use `.vim` plugins. You have to replicated this using our [Settings](#settings) and [Emulated plugins](#emulated-plugins). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
small grammar issue in last sentence "you have to replicate these"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
Sorry, not going to have the time to review this this weekend, but I'm sure I can just merge in changes directly if I notice anything is horribly wrong. :) (Which I doubt.) |
The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome
This what their repos are named, and make our README look more consistent.
It's enabled by default, and so isn't really a feature.
* Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks
They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too.
The tricks list is cooler (read: more important)
And clean up extra closing backticks
This is in-line with terminology in VSCode (i.e. `settings.json`).
And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings.
The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;)
It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section.
cde0f96
to
33a9e9b
Compare
Thanks a ton! This looks great and is definitely a solid start to build on! |
Thank you so much! |
* Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
* `gq` - on a visual selection - Reflow and wordwrap blocks of text, preserving commenting style. Great for formatting documentation comments. | ||
* `gc` - which adds another cursor on the next word it finds which is the same as the word under the cursor. | ||
* `af` - a command that I added in visual mode, which selects increasingly large blocks of text. e.g. if you had "blah (foo [bar 'ba|z'])" then it would select 'baz' first. If you pressed `af` again, it'd then select [bar 'baz'], and if you did it a third time it would select "(foo [bar 'baz'])". | ||
* `gh` - another custom VSCodeVim command. This one is equivalent to hovering your mouse over wherever the cursor is. Handy for seeing types and error messages without reaching for the mouse! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can I have this feature in nvim with any plugin or something like that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haven't used nvim seriously for a while but this might be useful: https://neovim.io/doc/user/lsp.html
Live preview
A few README enhancements. Mostly re-arranging things and, fixing up formatting and consistency problems, including:
Sorry for all the commits, happy to squash them once this is good to merge. I'd like to have another pass at proofreading over the weekend too. Let me know if there's anything you want removed/revert/fixed 👍
Thanks for an awesome plugin too