#1005936 Problem entering unicode characters

Package:
mate-terminal
Source:
mate-terminal
Description:
MATE terminal emulator application
Submitter:
Jos Nouwen
Date:
2026-07-16 17:53:01 UTC
Severity:
normal
#1005936#5
Date:
2022-02-16 11:09:51 UTC
From:
To:
When I try to enter unicode characters via the documented way( hold
<ctrl><shift>, enter 'u', enter hex offset, eg 2103 for degrees Celsius,
then release <ctrl><shift>), this is working perfectly in mate-terminal.
Except when the unicode hex offset contains hex character 'f' (e.g.
U+1F660 (or most other smil, because that triggers the 'Find' tool in
mate-terminal. I suggest to change the trigger key for 'Find' from
<ctrl><shift>f to something else, make it configurable, or make it
possible to switch that off.

#1005936#10
Date:
2026-07-16 15:03:22 UTC
From:
To:
Hi,
Where is it documented?

I tried as you mentioned and can confirm pressing 'f' triggers 'find'. However, I randomly tried and found that we don't have to (or probably should not) keep 'Ctrl+Shift' pressed when entering unicode characters. That is why I asked where is it documented. If it is official guide, we may have to correct it?!

Here is how to type unicode characters (including ones with 'f' in them):
- Type `Ctrl` + `Shift` + `u`. (Press and hold `Ctrl` and `Shift`, and hit `u`.)- *Release* `Ctrl` and `Shift` keys.- Type (unicode) characters. (Characters are *not* displayed.)
- Hit any key (even `Ctrl` or `Shift` work but preferably `Enter` or `Spacebar`) and the character is displayed.

I am on mate-terminal 1.26.1 btw.

Unless we have to correct the documentation somewhere, I think we can close this issue.

#1005936#15
Date:
2026-07-16 16:46:44 UTC
From:
To:
Sui,

Please make sure the bug description is included in the subject line.
Otherwise, people might need to look up the bug number to understand
what you're replying to.

Also, you need to CC the bug reporter (etc.) if you want them to see
your replies. Debian doesn't subscribe people to bugs they report or
reply to by default.

Thank you,
Jeremy Bícha

#1005936#20
Date:
2026-07-16 17:51:00 UTC
From:
To:
Hi Jeremy,
Noted on both points. Now that you mentioned, I see every other correspondence has subject.
Just to let you know, if you are checking today's bug emails, I have also replied to another bug #963118 same way, without subject and without keeping reporter in Cc.

Will correct from next correspondence.
Thank you for pointing out and explaining.