dawikur / algorithm-mnemonics.vim

🚀 Vim snippets for https://github.com/tommybennett/algorithm-mnemonics

algorithm-mnemonics.vim's Issues

Allow snippet parameterization

In many places there is code like:

auto pos = std:: ... ();

We should be able to decide what is the actual type of pos object:

auto pos ... ;
const auto pos ... ;
auto const pos ... ;

There are also lambdas with parameter like auto const value. We can parameterize:

auto value
auto const value
const auto element
...

For now it should be OK to give 3 options for return objects:

// const on:
auto <obj> // None
auto const <obj> // Right
const auto <obj> // Left

// lambda parameter:
[] (<lambda_parameter>)

Use UltiSnips Visual Placeholder

As suggested by @kiryph in tommybennett/algorithm-mnemonics#7 it would be nice to use those visual placeholders.

More: https://github.com/SirVer/ultisnips/blob/master/doc/UltiSnips.txt#L774

Prefix all vim helpfile tags

Vim's documentation http://vimhelp.appspot.com/helphelp.txt.html#help-writing says

The tag-name should be different from all the Vim help tag names and ideally
should begin with the name of the Vim plugin.

Since the plugin name is too long, I would consider a different prefix following common rules:

For instance, vim-latex includes a latex-help.txt file with the tag prefix latex-.

http://vimhelp.appspot.com/filetype.txt.html#ftplugin-docs would suggest something like
ft-cpp-snippets-stl-

Examples from http://vimhelp.appspot.com/filetype.txt.html#filetypes

[...] To search for help on a filetype prepend "ft-" and optionally append
"-syntax", "-indent" or
"-plugin". For example:
:help ft-vim-indent
:help ft-vim-syntax
:help ft-man-plugin

Note, the help command matches partials :h partial. You can still open with :h partial_sort_copy but :h stl-copy would open the description of the stl-snippet, but with :h copy you get the default vim help.