Skip to content

How to trigger the new shiny progress bars? #1324

Description

@agilesteel

Hi,

I've been a Fira Code user for years so I'm not a noob. I downloaded the latest release and tried typing sth. like [##..] to see the new shiny progress bars but couldn't get them to work.

What are the exact requirements for it to work?

I'm on win10, vs code, fira code 6.1

PS

Fira Code is awesome!
Thanks for the hard work!

Activity

  1. wopian commented on Dec 4, 2021

    @wopian
    Contributor

    The program outputting the progress bars needs to use the private-range unicode characters in this picture:

    image

  2. agilesteel commented on Dec 4, 2021

    @agilesteel
    Author

    Oh, these seem to be rare though. I've seen several progress bars today which use the "regular" brackets [, ]. Of course they won't render beautifully. I wonder why it was constrained as such. 😞

  3. agilesteel commented on Dec 4, 2021

    @agilesteel
    Author

    I just realized that you are talking about the outputting program. Well I tried vs code and windows terminal. Both didn't work. Is there a list of programs which work?

  4. tonsky commented on Dec 4, 2021

    @tonsky
    Owner

    These are not automatically enabled anywhere. I will try to ligaturize existing progress bars in #1183 where possible.

    What v6 brings are few new characters that could be used to draw progress bars. Unlike [##..], these are specifically designed for that purpose.

    You can write your own program that outputs these and see them if using Fira Code. Hopefully, other fonts will join and it becomes a standard, kind of like powerline did. Then you might expect those being used in the wild.

  5. alexeyten commented on Dec 4, 2021

    @alexeyten

    Hopefully, other fonts will join and it becomes a standard, kind of like powerline did.

    https://github.com/be5invis/Iosevka/releases/tag/v11.2.0

    Add Fira Code V6's progress bar symbols.

    👍

  6. agilesteel commented on Dec 4, 2021

    @agilesteel
    Author

    Oh I see. I guess this issue can be closed in this case. Thanks again for the hard work!

  7. added a commit that references this issue on May 11, 2026
  8. added a commit that references this issue on May 14, 2026
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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions