From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-pretest-bug@gnu.org, yamaoka@jpl.org, id.brep@gmail.com,
ding@gnus.org
Subject: Re: `.newsrc.eld' saves chinese group name in wrong coding
Date: Tue, 24 Oct 2006 06:17:58 +0200 [thread overview]
Message-ID: <uu01uuz2h.fsf@gnu.org> (raw)
In-Reply-To: <jwviriaepg0.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Mon, 23 Oct 2006 16:49:59 -0400)
> Cc: yamaoka@jpl.org, emacs-pretest-bug@gnu.org, id.brep@gmail.com,
> ding@gnus.org
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Mon, 23 Oct 2006 16:49:59 -0400
>
> >> My point was simply if you stay 100% within multibyte, it all works, and if
> >> you stay 100% in unibyte it all works
>
> > The former is true, the latter isn't, AFAIK. ``Normal'' Emacs
> > primitives and subroutines always do TRT with multibyte strings, while
> > with unibyte you need to be careful which ones you call.
>
> Care to give an example of what you're thinking about, where purely unibyte
> strings and buffers are not properly handled?
Are you talking about a unibyte Emacs session? If so, that's not what
I had in mind. I'm talking about using unibyte strings in a multibyte
session.
next prev parent reply other threads:[~2006-10-24 4:17 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ufydnay6j.fsf@gmail.com>
2006-10-19 2:54 ` Chong Yidong
2006-10-19 3:56 ` Katsumi Yamaoka
2006-10-19 4:11 ` Katsumi Yamaoka
2006-10-19 8:33 ` Reiner Steib
2006-10-19 9:03 ` Katsumi Yamaoka
2006-10-20 3:39 ` Chong Yidong
2006-10-20 4:06 ` Katsumi Yamaoka
2006-10-20 5:18 ` Katsumi Yamaoka
2006-10-20 6:04 ` Eli Zaretskii
2006-10-20 6:21 ` Katsumi Yamaoka
2006-10-20 6:38 ` Eli Zaretskii
2006-10-20 8:59 ` Katsumi Yamaoka
2006-10-21 2:03 ` Richard Stallman
2006-10-22 23:28 ` Katsumi Yamaoka
2006-10-23 11:45 ` Richard Stallman
2006-10-20 19:19 ` Stefan Monnier
2006-10-20 20:30 ` Eli Zaretskii
2006-10-20 22:06 ` Stefan Monnier
2006-10-21 9:22 ` Eli Zaretskii
2006-10-23 3:55 ` Stefan Monnier
2006-10-23 4:16 ` Eli Zaretskii
2006-10-23 19:11 ` Stefan Monnier
2006-10-23 20:06 ` Eli Zaretskii
2006-10-23 20:49 ` Stefan Monnier
2006-10-24 4:17 ` Eli Zaretskii [this message]
2006-10-24 15:22 ` Stefan Monnier
2006-10-24 17:27 ` Eli Zaretskii
2006-10-24 18:03 ` Stefan Monnier
2006-10-25 18:02 ` Richard Stallman
2006-10-25 20:22 ` Eli Zaretskii
2006-10-26 8:52 ` Richard Stallman
2006-10-27 8:05 ` Eli Zaretskii
2006-10-27 13:33 ` Richard Stallman
2006-10-27 14:27 ` Stefan Monnier
2006-10-28 18:13 ` Richard Stallman
2006-10-28 10:28 ` Eli Zaretskii
2006-10-29 18:45 ` Richard Stallman
2006-10-23 11:45 ` Richard Stallman
2006-10-23 19:16 ` Stefan Monnier
2006-10-24 17:43 ` Richard Stallman
2006-10-24 18:14 ` Stefan Monnier
2006-10-25 18:03 ` Richard Stallman
2006-10-25 18:03 ` Richard Stallman
2006-10-27 2:48 ` Kenichi Handa
2006-10-21 1:01 ` Kenichi Handa
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=uu01uuz2h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ding@gnus.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=id.brep@gmail.com \
--cc=yamaoka@jpl.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).