all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Werner LEMBERG <wl@gnu.org>
To: eliz@gnu.org
Cc: htl10@users.sourceforge.net, hintak.leung@gmail.com,
	25203@debbugs.gnu.org
Subject: bug#25203: 25.1; crash during message, infinite recursion
Date: Thu, 15 Dec 2016 17:48:57 +0100 (CET)	[thread overview]
Message-ID: <20161215.174857.2282423958048957975.wl@gnu.org> (raw)
In-Reply-To: <83fulp9oft.fsf@gnu.org>


> In fact, any I/O that might require encoding should be completely
> avoided in pre-write-conversion.

Is this documented?  If yes, I've missed it.

> So my suggestion is to fix your debugging code as indicated above.

Thanks for your analysis.  If it was only possible to debug
pre-write-conversion functions on the lisp level, I probably would
have found this by myself...


    Werner





  parent reply	other threads:[~2016-12-15 16:48 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161215.174857.2282423958048957975.wl@gnu.org \
    --to=wl@gnu.org \
    --cc=25203@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=hintak.leung@gmail.com \
    --cc=htl10@users.sourceforge.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.