From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Kenichi Handa <handa@ni.aist.go.jp>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: [Unicode-2] `read' always returns multibyte symbol
Date: Wed, 14 Nov 2007 20:39:05 +0900 [thread overview]
Message-ID: <b4mmythcazq.fsf@jpl.org> (raw)
In-Reply-To: <b4m64054gzd.fsf@jpl.org>
[-- Attachment #1: Type: text/plain, Size: 509 bytes --]
>>>>> Katsumi Yamaoka wrote:
> I'll try using a unibyte buffer to parse active data (after the bug
> is fixed).
Handa-san, thank you for the fix in Unicode-2. I've also made a
change in the Gnus CVS trunk so that it may use a unibyte buffer.
Now it works not only with Emacs 23.0.60 but also with Emacs 22.1,
22.1.50, and 23.0.50.
BTW, I found another problem with Emacs 21 (Gnus still supports
Emacs 21, IIUC). So, I'll go on looking into it further.
The diff between Gnus trunk and Unicode-2 is here:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 1379 bytes --]
*** gnus-start.el~ Sun Nov 11 21:51:22 2007
--- gnus-start.el Wed Nov 14 11:32:28 2007
***************
*** 2106,2112 ****
(if (equal method gnus-select-method)
(gnus-make-hashtable
(count-lines (point-min) (point-max)))
! (gnus-make-hashtable 4096)))))))
;; Delete unnecessary lines.
(goto-char (point-min))
(cond
--- 2106,2113 ----
(if (equal method gnus-select-method)
(gnus-make-hashtable
(count-lines (point-min) (point-max)))
! (gnus-make-hashtable 4096))))))
! group max min)
;; Delete unnecessary lines.
(goto-char (point-min))
(cond
***************
*** 2141,2148 ****
(insert prefix)
(zerop (forward-line 1)))))))
;; Store the active file in a hash table.
! (goto-char (point-min))
! (let (group max min)
(while (not (eobp))
(condition-case ()
(progn
--- 2142,2153 ----
(insert prefix)
(zerop (forward-line 1)))))))
;; Store the active file in a hash table.
! ;; Use a unibyte buffer in order to make `read' read non-ASCII
! ;; group names (which have been encoded) as unibyte strings.
! (mm-with-unibyte-buffer
! (insert-buffer-substring cur)
! (setq cur (current-buffer))
! (goto-char (point-min))
(while (not (eobp))
(condition-case ()
(progn
[-- Attachment #3: Type: text/plain, Size: 9 bytes --]
Regards,
[-- Attachment #4: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2007-11-14 11:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 9:41 Katsumi Yamaoka
2007-11-13 12:55 ` Kenichi Handa
2007-11-13 15:10 ` Stefan Monnier
2007-11-14 4:53 ` Kenichi Handa
2007-11-14 3:56 ` Katsumi Yamaoka
2007-11-14 11:39 ` Katsumi Yamaoka [this message]
2007-11-14 14:52 ` Stefan Monnier
2007-11-14 23:52 ` Katsumi Yamaoka
2007-11-15 1:15 ` Stefan Monnier
2007-11-15 3:01 ` Katsumi Yamaoka
2007-11-15 3:39 ` Stefan Monnier
2007-11-15 10:20 ` Katsumi Yamaoka
2007-11-15 11:08 ` Kenichi Handa
2007-11-15 11:41 ` Katsumi Yamaoka
2007-11-15 14:41 ` Kenichi Handa
2007-11-15 23:31 ` Katsumi Yamaoka
2007-11-16 0:51 ` Kenichi Handa
2007-11-16 1:24 ` Katsumi Yamaoka
2007-11-16 2:51 ` Stefan Monnier
2007-11-15 15:22 ` Stefan Monnier
2007-11-16 0:29 ` Kenichi Handa
2007-11-16 10:50 ` Eli Zaretskii
2007-11-13 15:07 ` Stefan Monnier
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=b4mmythcazq.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=handa@ni.aist.go.jp \
/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).