Skip to content

When using with cmp, expanding a variable with a reference causes breakage in cmp's menu #116

@unphased

Description

@unphased

Description

I was testing with my standard console.log snippet:

snippet l
        console.log('${VISUAL}$1:'${2:, ${VISUAL}$1});

When "fancy" snippets like this are being used, interactions are poor with the cmp menu.

Steps to Reproduce

  1. l to type l. the snippet shows in cmp list
  2. <tab> to move cmp selection down to l snippet
  3. <cr> to expand the l snippet. snippy interaction starts here.
  4. ab loads up cmp completion list filled with ab... entries
  5. <tab> move the selection down to the first of the ab... entries

Typically at this point, cmp selection causes the first result to fill into buffer, e.g. abcd. This does happen, and snippy picks it up! Which is great. What happens to cmp's currently-open completion menu, however, isn't great.

Expected Result

Expect cmp's completion list not to be clobbered

Actual Result

cmp's completion list gets clobbered at this point. it was listing the full list of ab... symbols but once the complex snippet expansion happens in response to cmp filling the current tabstop, the completion list now only shows this only one that matches

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions