From: Sergei Pokrovsky <pok@none.nowhere.invalid>
Subject: Re: hexadecimal unicode input ?
Date: Wed, 08 Oct 2003 18:35:34 +0700 [thread overview]
Message-ID: <uuk77gezcp.fsf@nbsp.nsk.su> (raw)
In-Reply-To: bm0ekd$9di$00$1@news.t-online.com
>>>>> "Thomas" == Thomas Langen <langen@langensoft.de> writes:
Thomas> Maybe some extended help on the mule-ucs function
Thomas> "insert-ucs-character" would be useful.
BTW, does it make sense to install mule-ucs in Emacs-21.3 ?
Looks like most of its capabilities are there out of the box, while
mule-ucs was not updated since April 2001.
--
Sergei
next prev parent reply other threads:[~2003-10-08 11:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 17:49 hexadecimal unicode input ? Thomas Langen
2003-10-07 22:14 ` Eli Zaretskii
[not found] ` <mailman.1288.1065565418.21628.help-gnu-emacs@gnu.org>
2003-10-08 7:33 ` Thomas Langen
2003-10-08 8:58 ` Oliver Scholz
2003-10-08 10:33 ` Eli Zaretskii
2003-10-08 11:35 ` Sergei Pokrovsky [this message]
[not found] ` <mailman.1314.1065609331.21628.help-gnu-emacs@gnu.org>
2003-10-08 13:45 ` Thomas Langen
-- strict thread matches above, loose matches on Subject: below --
2003-10-07 19:36 Thomas Langen
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=uuk77gezcp.fsf@nbsp.nsk.su \
--to=pok@none.nowhere.invalid \
/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.
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).