Skip to content

Emoji killing datetime #853

Closed
Closed

Description

@VagnerDomingues

Bug Report

Steps to reproduce

Just Write a datetime with :01: in hourly period anywhere in the documentation.

What is current behaviour

An emoji is appearing in the middle of datetime like the image below:

image

What is the expected behaviour

People should be able to write hourly periods with seconds in datetime objects representation in their documents, which means writing twice double dots between a number like this... :01:

Other relevant information

There should be an option to disable these emojis.

  • Bug does still occur when all/other plugins are disabled?

  • Your OS:

  • Node.js version: v7.5.0

  • npm version: 4.1.2

  • Browser version: Chrome 74.0.3729.157 (official) 64 bits

  • Docsify version: latest from cdn

  • Docsify plugins: docsify-themeable, docsify-pagination

Activity

  1. Koooooo-7 commented on May 26, 2019

    @Koooooo-7
    Member

    Hi ,
    the bug is a little bit funny 🤣 。
    it seems wrong to parse datetime as emoji syntax :emoji:
    I think it should work that making datetime in the code syntax , add ` 。
    ` 2019-05-06 10:11:12`

  2. VagnerDomingues commented on Jun 10, 2019

    @VagnerDomingues
    Author

    i can't escape it like that because it'll loose original css styling which is made for ease readings,
    i'm using it like this:

    image

    i just wanted to disable emoji feature because it will never be used in this documentation and it's already on production... cheers!

  3. VagnerDomingues commented on Jun 18, 2019

    @VagnerDomingues
    Author

    please if anyone could help i'd be very thankfull..

    you can check it on production here:
    https://fairlay.com/api/#/public/?id=examples

  4. VagnerDomingues commented on Jul 26, 2019

    @VagnerDomingues
    Author

    so... no way to get rid of emojis?

  5. Mkots commented on Aug 8, 2019

    @Mkots

    so... no way to get rid of emojis?

    You can try:
    window.$docsify = { noEmoji: true };

  6. stale commented on Feb 4, 2020

    @stale

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions