emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] PRIORITIES does not accept multi-byte unicode characters [9.6.9 (N/A @ /gnu/store/3rxpvdkn907pb1ccm2yl3ffyaz02k7d1-emacs-org-9.6.9/share/emacs/site-lisp/org-9.6.9/)]
Date: Sat, 20 Jan 2024 14:21:57 +0000	[thread overview]
Message-ID: <87le8k5blm.fsf@localhost> (raw)
In-Reply-To: <87zg1rhd0r.fsf@localhost>

Ihor Radchenko <yantar92@posteo.net> writes:

>> Expected: The lowest priority is selected: [#🇩🇪]
>>
>> Actual: Only the first byte of the lowest priority is selected: [#🇩]
>
> Try M-x describe-char on any of these emojis.
> Org mode relies on `string-to-char' to extract the priority char and
> (insert (string-to-char "🇩🇪")) ;=> 🇩
>
> So, it is a problem with Emacs. You may report it with M-x report-emacs-bug

I am looking into this now, with a different set of system fonts, and it
is now clear what is going on.

🇩🇪 is actually not a single Unicode character, but 2 characters: 🇩 and
🇪. The reason they are rendered as emoji is likely font composition
rules.

Org mode priorities _must_ be a single char.

That said, it is indeed confusing when what _appears_ to be a single
char is not under the hood.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


      reply	other threads:[~2024-01-20 14:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12 10:16 [BUG] PRIORITIES does not accept multi-byte unicode characters [9.6.9 (N/A @ /gnu/store/3rxpvdkn907pb1ccm2yl3ffyaz02k7d1-emacs-org-9.6.9/share/emacs/site-lisp/org-9.6.9/)] Dr. Arne Babenhauserheide
2023-09-12 11:00 ` Ihor Radchenko
2024-01-20 14:21   ` Ihor Radchenko [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87le8k5blm.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=arne_bab@web.de \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).