Less eager emoji autocompletion

Technical Support
  • Hi!

    In French typography, the rule is to put a space before colons (we write « les suivantes : » instead of "following:”). Sadly, having a space before a colon will trigger emoji autocompletion.

    This is really annoying because we keep writing 💯 everywhere and having to delete it afterward. The key combination is “space”, “colon”, “enter” because you usually put colons before a quotation or a list…

    With emoji-extended, there was a panel to set the regex. I'm not sure if that's really useful. Maybe just a 2-5 seconds timer before showing the autocompletion box would be welcome. Or maybe don't insert any emoji if enter is pressed while not having interacted with the autocompletion box in any way. Or just an option in ACP to disable autocompletion…

    I had to disable the emoji plugin entirely for now.

    Thanks for any help!

    ping @PitaJ

  • A delay is definitely not going to happen, that sounds infuriating for anyone who actually wants the emoji to show up.

    My solution will be to make it so the emoji completion will not show up until a letter is typed. For instance, : won't trigger it, but :a will. That will make spaces not trigger it either. That'll also help prevent it from showing up while writing code.

    I've create an issue: https://github.com/NodeBB/nodebb-plugin-emoji/issues/12

Suggested Topics

  • Random trollface emojis

    Unsolved Technical Support
    1 Votes
    3 Posts

    This morning I checked and the emoji image had gone, but the emoji code was still being applied whenever certain characters were used, including "£".



    I figured if it's doing a "live" replacement of those things then it must be something to do with the "Replace..." options in the plugin settings:


    So I disabled them both and did a restart / rebuild. The issue went away.

    I re-enabled them 1 by 1 to try and figure out which was causing the problem (rebuilding and restarting each time) and now, they're both re-enabled and the problem has not come back.

    So I'm a bit mystified. Evidently it was a problem with one of those options, but setting them again seems to have somehow fixed it.

  • 0 Votes
    3 Posts

    @pitaj got it! Thank you

  • 0 Votes
    8 Posts

    @PitaJ Updating to node 10 fixed the issue. Thanks

  • 0 Votes
    6 Posts

    @youhosi Following your response did an upgrade and don't know how but all the themes are working now. Minus my custom theme that I guess it has some bad code in it.

    Thank you.

  • 0 Votes
    7 Posts

    I'm having exactly the same problem.
    The solution of @yariplus does not help me, since then it generates an error when I login to the forum with Google, it tells me ops! an error has happened, our umpa loompas are working to fix it, and it won't let me login, the problem is that the forum is already in production