From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: uudecoding bug?
Date: 08 Nov 1998 00:38:33 +0100 [thread overview]
Message-ID: <m3zpa3rs3q.fsf@sparky.gnus.org> (raw)
In-Reply-To: Vladimir Volovich's message of "07 Nov 1998 22:56:50 +0300"
Vladimir Volovich <vvv@vvv.vsu.ru> writes:
> Just one more very strange result:
>
> (string-match "Шрифт" "Шрифт")
> nil
>
> Looks like a bug in Emacs. ;-(
Yes. You could report this to RMS just to be sure, but I think I
brought a related issue up with him, and he said it way supposed to be
fixed in the latest pretest. But I haven't tested it myself yet.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1998-11-07 23:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-30 21:23 Vladimir Volovich
1998-11-07 13:37 ` Lars Magne Ingebrigtsen
1998-11-07 15:08 ` Vladimir Volovich
1998-11-07 15:44 ` Lars Magne Ingebrigtsen
1998-11-07 17:33 ` Vladimir Volovich
1998-11-07 17:46 ` Vladimir Volovich
1998-11-07 19:56 ` Vladimir Volovich
1998-11-07 23:38 ` Lars Magne Ingebrigtsen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3zpa3rs3q.fsf@sparky.gnus.org \
--to=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.
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 NNTP newsgroup(s).