Conemu: Alternative font unicode range does not accept codepoints outside of BMP

Created on 20 Dec 2016  路  13Comments  路  Source: Maximus5/ConEmu

Versions

ConEmu build: 161206 x32
OS version: Windows 7 Enterprise Service Pack 1 x64 (6.1.7601)
Used shell version: powershell

Problem description

In Settings -> Main -> Alternative font -> Unicode ranges:

<EDIT>

If you enter a number with more than 4 digits (Unicode codepoint outside of BMP), it is not used. After "Apply", "Save Settings" and restarting ConEmu, the number is gone.

Note: I edited this issue instead of creating a new one, because this issue is already labeled with "enhancement", which only applies to the more-than-4-digit-problem.

The original problem is now solved (in preview and alpha):
</EDIT>

If you enter the range or number only, it doesn't get applied. One has to enter some name or string followed by a collon and a space. After that, the unicode range is accepted.

Steps to reproduce

  1. echo a character in conemu. (I used powershell: [char]::ConvertFromUtf32(0x25c4))
  2. Settings -> Main
    2.1 Enable checkbox Alternative font (pseudographics, CJK, etc.)
    2.2 Set different fonts for Main and Alternative font (eg. Main: 'Consolas', Alternative: 'Segoe UI Symbol')
    2.3 Delete content in field Unicode ranges, the default is "2013-25C4;", click Apply Button
    Result: previously echoed character is displayed in main font. -> Correct
    after step 2 3
    2.4 Enter number of previously echoed character (e.g. 25c4) into field, click Apply Button
    Result: previously echoed character is still displayed in main font. -> Wrong
    after step 2 4
    2.5 Enter some random string + : + space + number of previously echoed character
    (e.g. foobar: 25c4) into field, click Apply Button
    Result: previously echoed character is now displayed in alternative font. -> Correct
    after step 2 5

Actual results

Alternative font unicode range is only accepted, when preceded by some characters+: + space

Expected results

Alternative font unicode range is also accepted, if you just enter hexadecimal nummers or ranges.

drawing type-enhancement

Most helpful comment

Adding my voice to this too - emojis are becoming insanely useful for a variety of reasons, one such is using them for git commit messages so to make it easy to see at a glance what the purpose of a particular commit was, but it's impossible to do so in ConEmu, meaning falling back to another terminal or GUI to do so - a bit of a thorn in the side of the wonderful workflow ConEmu provides.

All 13 comments

@TSlivede I can't apply or save a custom range even with the random prefix. Testing Segoe UI Emoji with 馃悎.

Hint states that only four digits are supported

Ugh, bummer. So, no way to have fancy emojis in ConEmu?

It would be an enhancement

@Maximus5 any idea if this is going to be implemented?

i know there's bigger fish to fry but this would be nice to have...

Adding another voice to this, I'd really like to see emoji's. I'm a windows user and I'm using ConEmu for my terminal for Vim and having custom emojis for my gutter would greatly improve my vim experience. Cheers.

+1 for emoji. I just moved to Windows from Mac/Unix and like having extra emoji for use in git prompts, etc.

Adding my voice to this too - emojis are becoming insanely useful for a variety of reasons, one such is using them for git commit messages so to make it easy to see at a glance what the purpose of a particular commit was, but it's impossible to do so in ConEmu, meaning falling back to another terminal or GUI to do so - a bit of a thorn in the side of the wonderful workflow ConEmu provides.

This would be awesome!

+1 on this. Would be really nice and add quite a bit of polish :)

Native Emoji support (among lots of other improvements) is inbound for Win 10's CLI, soon鈩笍: https://blogs.msdn.microsoft.com/commandline/2018/11/15/windows-command-line-unicode-and-utf-8-output-text-buffer/

If you鈥檙e running Windows 10 October 2018 Update (build 1809), you鈥檙e already running this new buffer!

We tested the new buffer prior to including it quietly in Insider builds in the months leading-up to 1809 and made some key improvements before 1809 was shipped.
[...]
Are we there yet?
Not quite!

I wish I have more time to work on ConEmu codebase.

Was this page helpful?
0 / 5 - 0 ratings