Suggestion: not preceded by space

[davidpiano]

I've seen at least a couple of issues asking essentially the same thing: how to expand a key without putting a space before it, because the desired output must not contain a space at the place where the snippet is being added. Clearly, this isn't possible.

Obviously, a snippet replaces its key, and doesn't just appear beside the key; this means every snippet already deletes characters from the buffer.

Here's my suggestion: is there an easy way to make certain snippets delete one more character than they currently do? "Space-gobbling snippets" might solve a problem by removing the unwanted space after the fact.

[monnier]

Here's my suggestion: is there an easy way to make certain snippets delete one more character than they currently do? "Space-gobbling snippets" might solve a problem by removing the unwanted space after the fact.

Hmm... is a space really always present? I don't use YASnippet enough to know, but I'd expect that YASnippets can be expanded even if placed right after an open paren, for example. Also, YASnippet usually (re)indents the code resulting from the expansion, so it will already insert/delete space at the beginning in some of those cases. IOW, I think it would help if you could collect/list some examples where an extra space is needed to perform expansion (and would benefit from being deleted afterwards).

[davidpiano]

monnier ***@***.***> writes:

> Here's my suggestion: is there an easy way to make certain > snippets delete > one more character than they currently do? "Space-gobbling snippets" might > solve a problem by removing the unwanted space after the fact. Hmm... is a space really always present? I don't use YASnippet enough to know, but I'd expect that YASnippets can be expanded even if placed right after an open paren, for example. Also, YASnippet usually (re)indents the code resulting from the expansion, so it will already insert/delete space at the beginning in some of those cases. IOW, I think it would help if you could collect/list some examples where an extra space is needed to perform expansion (and would benefit from being deleted afterwards). - Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.*Message ID: ***@***.***>

Scenario: typing the text trigger for a snippet, but the snippet in question is meant to directly follow the previous character without a space between them. But if I really type the snippet trigger without putting a space before it, it isn't the trigger anymore. Am I only asking this question because I've misunderstood something?

…

-- David

[monnier]

Scenario: typing the text trigger for a snippet, but the snippet in question is meant to directly follow the previous character without a space between them.

No, no, I meant a concrete scenario: - in which major mode? - which specific snippet(s)? - what would the text just (which doesn't end in a space) before typically look like? Stefan

[ghost-of-freedom]

yas-key-syntaxes governs how the keys are ``gobbled''. It's a list where functions are called without arguments, and are expected to put the cursor at the start of the key, and strings are passed to skip-syntax-backwards. You can probably just make a function that saves the current point, goes back a word, gets the string between the two points, looks it up in a list or a table of keys that should have the space deleted, and if there's a match, backspaces a single character (which is assumed to be a space.) That should make yasnippet happy, because you put the cursor at the location of the start of the key, and you happy, because there's no space.

There might be an even better way of utilizing this variable, but this is the simplest solution that comes to mind.