You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
autocomplete-snippets does show this snippet when period (.) is typed, but it disappears when anything is typed beyond the initial period. Similar behavior is seen when a period appears in midst of a snippet's prefix (see #57). The reason of this behavior is probably that autocomplete-plus probably provides it's consumer packages with prefixes based on alphanumeric characters and characters - and _ only.
My concern is that if atom-snippets allows snippets with periods/punctuation... then so should autocomplete-snippets. This can be fixed at the level of autocomplete-plus too, but I think implementing a fix in this package could be simpler, and cause fewer conflicts.
The text was updated successfully, but these errors were encountered:
Most of (La)TeX commands (control sequences in TeX's terminology) starts with a backslash. Therefore, we would greatly appreciate it if non-letter prefixes are supported and there seems to be a prototype for this.
e.g consider the following snippet provided by https://github.com/joseramonc/rails-snippets :
autocomplete-snippets
does show this snippet when period (.) is typed, but it disappears when anything is typed beyond the initial period. Similar behavior is seen when a period appears in midst of a snippet's prefix (see #57). The reason of this behavior is probably thatautocomplete-plus
probably provides it's consumer packages with prefixes based on alphanumeric characters and characters - and _ only.My concern is that if
atom-snippets
allows snippets with periods/punctuation... then so should autocomplete-snippets. This can be fixed at the level ofautocomplete-plus
too, but I think implementing a fix in this package could be simpler, and cause fewer conflicts.The text was updated successfully, but these errors were encountered: