Need way to escape/disable emoji in GitLab Flavored Markdown

I created an issue in our internal GitLab issue and cited a time format string consisting of "hh", a colon ":", "hh", a colon ":", "ss"

GFM converted the colon-mm-colon sequence into an emoji ()

• hh:mm:ss

I need some way to escape or disable this:

None of the quoting/escaping I tried worked:

• use \ before each colon yields: hh:mm:ss
• use : instead of a colon yields: hh:mm:ss
• use &#58 (closed); instead of a colon yields: hh:mm:ss

Using a zero-space delimiter ‌ around the colons does visibly render correctly, but it adds extra text that should not really be there - i.e. you cannot copy/paste this and get the desired text:

• hh‌:‌mm‌:‌ss

As you can see, we also need a way to escape the autolinking to GitLab issues, I don't want a link to issue # 58 when I use "&#53 (closed)" and I can't use # in GFM to get just a #

hh‌ :‌mm:‌ ss <- doesn't seem to turn into emoji for me, but you can escape text by surrounding with backticks or three backticks ``` for the whole line - see https://gitlab.com/help/markdown/markdown#code-and-syntax-highlighting

This should also work to stop autolinking issues too:

This will autolink: #537 (closed)

This will not (surrounded by backticks): #537

This also will not (three backticks code block):

#537

Screenshot of the source of this comment:

Trying a response with backticks, hh:mm:ss renders with[out] emoji. Without the backticks, hh:mm:ss renders with emoji.

Mike Hall - your comment did not render emoji because you have a zero-width space around the : characters. If I copy/paste your text, I see (od -c dump):

0000000   h   h 342 200 214       : 342 200 214   m   m   : 342 200 214
0000020       s   s
0000023

Added markdown label

mentioned in issue #2470 (closed)

Added ~480950 ~159098 ~12980 labels

Added ~874211 and removed ~480950 labels

The backticks may make the colons render properly, however, the popup for selecting emoji is impossible to dismiss. If I want a space or hard return following the colon (as is common when writing, say, python) I have to either type the colon followed by a four letter word that doesn't match any emoji, then hard return, then go back and remove the four letter word. Or, type the colon, hit escape, then cancel out of the dialog asking if I want to abandon my comment. At the very least, I should think the typeahead menu for things like emojis and autolink should not be triggered while typing inside (or after) a single or triple backtick. Otherwise, a way to escape out of the menu without selecting from it is necessary (I expected space to do so, but it selects the currently highlighted menu item juts like enter does).

moved to gitlab#3850

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue

mentioned in merge request !14785