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

Emoji entered with Windows Emoji Selector shown as "Unknown Glyph" #7547

Closed
esarver opened this issue Mar 9, 2022 · 10 comments
Closed

Emoji entered with Windows Emoji Selector shown as "Unknown Glyph" #7547

esarver opened this issue Mar 9, 2022 · 10 comments

Comments

@esarver
Copy link

esarver commented Mar 9, 2022

Describe the bug
When entering an emoji using the Windows symbol selection popup (accessed with META+.), the emoji is inserted but appears as the "unknown glyph" indicator (diamond shape with a ? inside). If an emoji already exists in a document, it is displayed as expected. If Vim mode is disabled, the emoji are correctly inserted.

To Reproduce
Steps to reproduce the behavior:
On Windows (not tested on other platforms):

  1. Enable Vim mode
  2. Enter insert mode
  3. META+., select any emoji to insert.
  4. Unicode was entered, but "unknown glyph" was shown.

Expected behavior
The emoji should be shown.

Screenshots
Selecting Emoji
Unknown Glyphs

Environment (please complete the following information):

  • Extension (VsCodeVim) version: 1.22.2
  • VSCode version: 1.65.1
  • OS: Windows 10 Enterprise 1909
@esarver
Copy link
Author

esarver commented Mar 9, 2022

Just tried copy and paste of an emoji and that seems to work correctly.

@marekjedrzejewski
Copy link

Same happens on Linux with Gnome - ctrl + . shrug space enter and instead of 🤷️, which is visible after clicking space I get the question marks and cursor between them.
Copy-pasting works. And if I disable vscodevim it also works.

@pieterdd
Copy link

@esarver I can confirm that copy/pasting works fine on my Windows machine. The problem seems to occur specifically with the OS' emoji keyboard.

@kartinul
Copy link

kartinul commented Jul 6, 2022

Same here...
bug

@pohy
Copy link

pohy commented Jul 9, 2022

I have the same issue on Windows 10 using the Windows Emoji keyboard.
But! The same emojis render correctly when inserted through the Emoji Snippets extension.
Code_2022-06-28_10-59-40

@pieterdd
Copy link

pieterdd commented Jul 9, 2022

That's an interesting workaround.

Small caveat: this does not seem to work with the Plain Text file type. For those use cases, you may want to switch to the Markdown file type.

@MyriaCore
Copy link

bump! I've been annoyed by the lack of emojis for a while now, didn't think it was coming from this extension though given how popular it is

@pieterdd
Copy link

pieterdd commented Sep 7, 2022

I noticed that this plugin has ~1300 open issues, so I think you're more likely to get the issue solved by contributing a patch than by poking the maintainers.

Alternatively - this is what I did - you can install Neovim and a VSCode plugin for Neovim. Neovim can be embedded into other applications, which is exactly what this VSCode plugin does. Thanks to this feature, Neovim cam provide a real Vim experience, where VSCodeVim is only an emulator. Neovim does not seem to have trouble with emojis.

There's a bit of configuration involved. Here's what to do:

  • Uninstall VSCodeVim to prevent conflicts.
  • Install Neovim and VSCode Neovim.
  • Go to VSCode's settings and enter @ext:asvetliakov.vscode-neovim executable in the search bar.
  • For the setting matching your operating system, enter the full path to the Neovim executable on your system. I had to enter C:\Program Files\Neovim\bin\nvim.exe under 'Neovim Executable Paths: Win32'.
  • (Optional) You may want to configure VSCode Neovim to use different a settings file than your regular Neovim. If so, 'Neovim Init Vim Paths' is the setting you're looking for. Again, check that you have the right setting for your OS.
  • Restart VSCode.

So far this seems to be working smoothly for me. Since it is native (but embedded) Vim, I also expect that will fix an occasional bug with the undo function that I experienced.

@Ya2gLu
Copy link

Ya2gLu commented Sep 21, 2022

The author said you don’t free-rider, contribute to the code🤣

@J-Fields
Copy link
Member

Duplicate of #6046; should be fixed by #7977

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

No branches or pull requests

8 participants