Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Insert emojis directly #16

Open
wants to merge 15 commits into
base: master
Choose a base branch
from
Open

Insert emojis directly #16

wants to merge 15 commits into from

Conversation

eugenesvk
Copy link
Contributor

@eugenesvk eugenesvk commented Apr 9, 2024

This is an experiment to allow inserting emojis directly without adding extra prefixes like @ and : but insteas using ,comma in a name as a substitute
For example, for git emojis:

  • @⭾boo:bookmark:
  • @⭾,boo → 🔖 (comma as a second prefix, but only after autocompletion event has been started)
  • @⭾book, → 🔖 (comma as a suffix so you can think about what you want to insert later after finding the right name, which I think might be a better option)
    The downside is that the list of emoji is more polluted now with dupes, so added dedicated prefix variant as well for testing
  • !⭾book → 🔖(git emojis)
  • |⭾book → 📖 (regular emojis)

This also includes

  • updates of the emoji datasets-
  • adding gitmojis data https://github.com/carloscuesta/gitmoji (they have more emojis
    • it's a bit more verbose, e.g.
      • ["🚧\tWIP", ":construction:"] is Work in progress (though wip sill works in search due to fuzzy matching)
    • some emojis are mismatched
    • ["🚨\ttests", ":rotating_light:"] used for a fix, 🧪 used for tests
    • ["📚\tdocumentation", ":books:"], 📝
    • ["🐎\tperformance", ":racehorse:"], ⚡️
    • or missing ["📇\tmetadata", ":card_index:"]
      )
  • cleaning up ST3 variant so it was easier to test config without an extra set of dupe emojis
  • removed the previous duplication with @ which I don't think was needed in a pure ST4 variant

!!!: due to ↑ this can't be merged as is and the repo would need to register support for different ST version with package control with different repo tags (e.g., 2.0.0-st3 and 2.0.0-st4 or something)

  • the build script is updated to generate the full GithubEmoji.sublime-settings config

closes #15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

FR: Option to insert the Emoji itself and not the GitHub Code
1 participant