unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "समीर सिंह Sameer Singh" <lumarzeli30@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rpluim@gmail.com, emacs-devel@gnu.org
Subject: Re: Unicode 15
Date: Fri, 16 Sep 2022 00:03:33 +0530	[thread overview]
Message-ID: <CAOR1sLxjV+2_ZJE16VT-TuokkEAhRxFbHjsb90fCD7HjBcPieA@mail.gmail.com> (raw)
In-Reply-To: <837d24ze5h.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]

>
> Suppose you tell what exactly did you do with "C-x 8 RET" that didn't
> work?


After typing "C-x 8 RET" I type the names of the newly added characters
such as "kawi",
"nag mundari" etc in the prompt and then try to TAB autocomplete it but
they do not appear,
also when describe-char-ing these characters
their unicode name also does not show up in Character code properties

On Thu, Sep 15, 2022 at 11:57 PM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: समीर सिंह Sameer Singh <lumarzeli30@gmail.com>
> > Date: Thu, 15 Sep 2022 23:03:16 +0530
> > Cc: rpluim@gmail.com, emacs-devel@gnu.org
> >
> > No :/ is this related to mule-cmds.el? Because I did not update it,
> because I could not understand it
> > for example why are some ranges commented out and some are missing.
>
> mule-cmds.el needs to be updated only if ranges of codepoints marked
> as "unused" have changed, so some of their codepoints are now used for
> characters.  The commented-out ranges are those whose names either
> don't exist (because they are unused) or are meaningless, like those
> in the various ideographic blocks.
>
> Suppose you tell what exactly did you do with "C-x 8 RET" that didn't
> work?
>

[-- Attachment #2: Type: text/html, Size: 1976 bytes --]

  reply	other threads:[~2022-09-15 18:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14  0:56 Unicode 15 समीर सिंह Sameer Singh
2022-09-14  2:39 ` Eli Zaretskii
2022-09-14 12:24   ` समीर सिंह Sameer Singh
2022-09-14 12:52     ` Eli Zaretskii
2022-09-14 16:26       ` समीर सिंह Sameer Singh
2022-09-14 16:42         ` Eli Zaretskii
2022-09-14 16:45           ` समीर सिंह Sameer Singh
2022-09-14 16:54             ` Eli Zaretskii
2022-09-15  1:26               ` समीर सिंह Sameer Singh
2022-09-15  5:56                 ` Eli Zaretskii
2022-09-15 12:00                   ` समीर सिंह Sameer Singh
2022-09-15 12:37                     ` Robert Pluim
2022-09-15 13:13                       ` समीर सिंह Sameer Singh
2022-09-15 13:30                         ` Robert Pluim
2022-09-15 17:05                           ` समीर सिंह Sameer Singh
2022-09-15 17:11                             ` Eli Zaretskii
2022-09-15 17:33                               ` समीर सिंह Sameer Singh
2022-09-15 18:27                                 ` Eli Zaretskii
2022-09-15 18:33                                   ` समीर सिंह Sameer Singh [this message]
2022-09-15 19:04                                     ` Eli Zaretskii
2022-09-16  0:01                                       ` समीर सिंह Sameer Singh
2022-09-16  4:34                                         ` समीर सिंह Sameer Singh
2022-09-16  6:53                                           ` Robert Pluim
2022-09-16 16:30                   ` Peter Oliver

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.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=CAOR1sLxjV+2_ZJE16VT-TuokkEAhRxFbHjsb90fCD7HjBcPieA@mail.gmail.com \
    --to=lumarzeli30@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rpluim@gmail.com \
    /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.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).