Closed varunkumar closed 5 years ago
I agree with your comments. If you want the extension to be specific to encoded string, then it makes perfect sense. I noticed Markdown
in the list of supported languages. Hence, added support for plaintext
as it is closer.
I find it convenient to use a single extension for all my needs. So, still prefer to have the support for plain text as part of this extension. Being the maintainer of the repo, I would leave it to you to make the call.
IIRC, there was a PR for plain text support in the past which I have rejected (it could have been with my variants for Sublime Text or Atom). The purpose of this package is to insert the encoded string – hence the package name. There are plenty of packages for simple Emoji insertion. Apart from that, inserting emojis is very easy on macOS (Ctrl+Cmd+Space) and even on Windows 10 (Win+;).
However, I'm not oppose to merging the launch configuration, if you can explain what its benefits are.