From: Eli Zaretskii <eliz@gnu.org>
To: jsbien@mimuw.edu.pl
Cc: 32599@debbugs.gnu.org
Subject: bug#32599: 25.2; Feature request: input PUA characters by name
Date: Sun, 26 May 2019 19:51:00 +0300 [thread overview]
Message-ID: <83d0k52m8b.fsf@gnu.org> (raw)
In-Reply-To: <86y32t2p44.fsf@mimuw.edu.pl> (jsbien@mimuw.edu.pl)
> From: jsbien@mimuw.edu.pl (Janusz S. Bień)
> Cc: 32599@debbugs.gnu.org
> Date: Sun, 26 May 2019 17:48:43 +0200
>
> >> The UnicodeData.txt file is compiled into Emacs,
> >
> > I know and I'm curious whether it is really needed.
>
> It was a bad wording as I can guess it is done for efficiency.
Indeed. Both processing efficiency and (perhaps more importantly)
memory efficiency. Some of the resulting data is accessed by core
features that must be very efficient: the display engine, the regexp
search functions, etc.
> How the character data are stored and accessed?
The data is stored in char-tables of special kind. See the files
uni-*.el which are produced as part of the Emacs build process.
> > Why it cannot be loaded at the startup?
>
> Or, better, partially overriden or supplemented? Is is prohibited by the
> way the character data are stored?
You can override the char-tables at run time, of course, but first you
need to generate the new ones.
And there's the other problem I mentioned: with general treatment of
PUA codepoints.
next prev parent reply other threads:[~2019-05-26 16:51 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86sh30fg4q.fsf@mimuw.edu.pl>
2018-08-31 6:05 ` bug#32599: 25.2; Feature request: input PUA characters by name Janusz S. Bień
2018-08-31 8:05 ` Robert Pluim
2018-08-31 9:09 ` Janusz S. Bień
2018-08-31 12:34 ` Robert Pluim
2018-08-31 12:54 ` Janusz S. Bień
2019-05-26 8:10 ` Janusz S. Bień
2019-05-26 14:45 ` Eli Zaretskii
2019-05-26 15:18 ` Janusz S. Bień
2019-05-26 15:48 ` Janusz S. Bień
2019-05-26 16:51 ` Eli Zaretskii [this message]
2019-05-26 16:56 ` Eli Zaretskii
2019-05-26 17:33 ` Janusz S. Bień
2019-05-26 18:52 ` Eli Zaretskii
2019-05-27 5:48 ` Janusz S. Bień
2019-05-27 17:11 ` Eli Zaretskii
2019-05-27 17:39 ` Janusz S. Bień
2019-05-27 18:45 ` Eli Zaretskii
2019-05-28 5:18 ` Janusz S. Bień
2019-05-28 5:34 ` Eli Zaretskii
2019-05-28 5:39 ` Janusz S. Bień
2020-12-30 17:49 ` Janusz S. Bień
2020-12-30 20:52 ` Eli Zaretskii
2020-12-31 6:39 ` Janusz S. Bień
2020-12-31 7:49 ` Eli Zaretskii
2020-12-31 8:14 ` Janusz S. Bień
2020-12-31 9:06 ` Eli Zaretskii
2020-12-31 9:31 ` Janusz S. Bień
2020-12-31 10:31 ` Eli Zaretskii
2022-04-26 13:09 ` Lars Ingebrigtsen
2022-04-26 13:30 ` Janusz S. Bień
2022-04-26 13:37 ` Lars Ingebrigtsen
2022-04-26 13:44 ` Janusz S. Bień
2022-04-26 13:45 ` Lars Ingebrigtsen
2022-04-26 15:33 ` Janusz S. Bień
2022-04-26 15:49 ` Robert Pluim
2022-04-26 16:09 ` Janusz S. Bień
2022-04-26 16:44 ` Eli Zaretskii
2022-04-26 18:22 ` Janusz S. Bień
2022-04-27 11:51 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83d0k52m8b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32599@debbugs.gnu.org \
--cc=jsbien@mimuw.edu.pl \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.