From: Hin-Tak Leung <htl10@users.sourceforge.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: cjk-list@nongnu.org, by@moscito.org, 25203@debbugs.gnu.org
Subject: bug#25203: [cjk] Fwd: HELP with emacs 25.1 and cjk-enc.el
Date: Fri, 16 Dec 2016 14:18:21 +0000 (UTC) [thread overview]
Message-ID: <2088662471.7284949.1481897901234@mail.yahoo.com> (raw)
In-Reply-To: <20161215000453.17313-1-htl10@users.sourceforge.net>
--------------------------------------------
On Fri, 16/12/16, Eli Zaretskii <eliz@gnu.org> wrote:
> Sorry, I don't understand the question.
Can you elaborate?
It is not a question - it is a follow-up correction to a proposed (wrong) bug fix to cjk-enc.el.
This thread was started because cjk-enc.el broke with emacs 25. So I was close
enough - and made it worse to crash with two new mesage()'s. The crash surprisingly helps, in the end.
The initial breakage was because there was already a message() (for progress reporting, which
has worked for 10+ years until 24.5) a few lines above the two new ones I added.
The relevant change in emacs 25 is, as you suggested, this:
http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=c63246628461f748d66a8a07ba008de2e00fd33a
'Obey coding-system-for-write when writing stdout/stderr in batch'
There seems to be another breakage of cjk-enc.el - somehow, `write-region in emacs 25 for big5 input
is calling cjk-encode (pre-write-conversion) more than once, and the 2nd time wrongly. This only
happens with emacs 25 and only with big5 input (i.e. not with earlier emacs nor thai/mule input).
So there is another recursion somewhere - still looking...
I added a (backtrace) to cjk-encode and the 2nd+ calls are also from write-region - so definitely needs
C-level debugging to look further ( https://debbugs.gnu.org/cgi/bugreport.cgi?bug=8108 )
Yes, the issue with crash with message() in pre-write-conversion is well-understood now,
and thanks a lot for all the help. Bug 25203 can close.
next prev parent reply other threads:[~2016-12-16 14:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <955842899.6288681.1481820009426.ref@mail.yahoo.com>
2016-12-15 0:04 ` bug#25203: 25.1; crash during message, infinite recursion Hin-Tak Leung
2016-12-15 5:29 ` Werner LEMBERG
2016-12-15 15:55 ` Eli Zaretskii
2016-12-15 16:11 ` Noam Postavsky
2016-12-15 16:57 ` Eli Zaretskii
2016-12-15 16:48 ` Werner LEMBERG
2016-12-16 8:55 ` Eli Zaretskii
2016-12-16 9:08 ` Werner LEMBERG
2016-12-16 10:48 ` Eli Zaretskii
2016-12-15 16:40 ` Hin-Tak Leung
2016-12-15 22:57 ` bug#25203: [cjk] Fwd: HELP with emacs 25.1 and cjk-enc.el Hin-Tak Leung
2016-12-16 8:02 ` Eli Zaretskii
2016-12-16 9:28 ` Andreas Schwab
2016-12-16 10:48 ` Eli Zaretskii
2016-12-15 23:02 ` Hin-Tak Leung
2016-12-16 8:04 ` Eli Zaretskii
2016-12-16 9:00 ` Werner LEMBERG
2016-12-16 14:18 ` Hin-Tak Leung [this message]
2016-12-16 14:34 ` bug#25203: 25.1; crash during message, infinite recursion Hin-Tak Leung
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=2088662471.7284949.1481897901234@mail.yahoo.com \
--to=htl10@users.sourceforge.net \
--cc=25203@debbugs.gnu.org \
--cc=by@moscito.org \
--cc=cjk-list@nongnu.org \
--cc=eliz@gnu.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).