Vim has markers such as 'a 'B etc - but scripts such as snippet engines are likely to want to place markers without messing with markers used by the user.
AFAIK UltiSnips has tried to reimplement such feature using python with all pros/cons.
I still think it would be worthwhile adding
There are actually two issues here: first ist that Vim should offer programmatic markers that do not conflict with the user visible ones. The second is that Vim markers only track the line they are in, but the column is not moved with the text.
One more related issue is #174.
This is unlikely to be addressed now, so I'm closing. Feel free to open another when we have advanced more in the project.
Suggestion: add a textfile called "future-maybe-ideas.txt" or such and reference such ideas there. This does not take much time, doesn't get into your way, but makes a difference: Issues which get closed don't memorize the state "closed due to future/maybe item or closed because of fixed". I think having arbitrary markers is useful for many applications, snippets being only one of them.
Maybe we could use a issue label like "revisit-later" for this.
Following @stefan991's suggestion, l created 'reopen-later' label
Merge pull request #169 from xanderdunn/master
Add scalastyle checker
This is addressed by #5031