all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: "Janusz S. Bień" <jsbien@mimuw.edu.pl>
Cc: 32599@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#32599: 25.2; Feature request: input PUA characters by name
Date: Tue, 26 Apr 2022 17:49:25 +0200	[thread overview]
Message-ID: <87fslzalq2.fsf@gmail.com> (raw)
In-Reply-To: <874k2fsvu6.fsf@mimuw.edu.pl> ("Janusz S. Bień"'s message of "Tue, 26 Apr 2022 17:33:37 +0200")

>>>>> On Tue, 26 Apr 2022 17:33:37 +0200, Janusz S. Bień <jsbien@mimuw.edu.pl> said:

    Janusz> On Tue, Apr 26 2022 at 15:45 +02, Lars Ingebrigtsen wrote:
    >> Janusz S. Bień <jsbien@mimuw.edu.pl> writes:
    >> 
    >>>> (unless ucs-names
    >>>> (ucs-names))
    >>>> (setf (gethash "LATIN ABBREVIATION SIGN SMALL DE" ucs-names) #xF159)
    >>> 
    >>> Debugger entered--Lisp error: (wrong-type-argument hash-table-p nil)
    >>> puthash("LATIN ABBREVIATION SIGN SMALL DE" 61785 nil)
    >> 
    >> Did you eval the `unless' form first?

    Janusz> I thought I did but I used the wrong command :-(

    Janusz> Thank you very much for your solution.

    Janusz> So yes, my original problem is solved and you can close the bug report.

    Janusz> This is however not the end of the story. I would like describe-char to
    Janusz> produce the correct name of the PUA character instead of "the
    Janusz> character’s canonical name and other properties defined by the Unicode
    Janusz> Data Base;". I understand this should posted as a separate feature
    Janusz> request.

(put-char-code-property #xf159 'name "LATIN ABBREVIATION SIGN SMALL DE")

(PUA characters donʼt have canonical names).

Robert
-- 





  reply	other threads:[~2022-04-26 15:49 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
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 [this message]
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=87fslzalq2.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=32599@debbugs.gnu.org \
    --cc=jsbien@mimuw.edu.pl \
    --cc=larsi@gnus.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 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.