From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs24 coding system problems Date: Fri, 30 Nov 2012 15:40:52 +0200 Message-ID: <83624nus2j.fsf@gnu.org> References: <20627.33570.796000.901596@gargle.gargle.HOWL> <20649.12724.125000.858979@gargle.gargle.HOWL> <83k3tizkl2.fsf@gnu.org> <20649.61758.750000.69012@gargle.gargle.HOWL> <20657.53134.989000.793074@gargle.gargle.HOWL> <874nkdrjhc.wl%%xmue@d1.dion.ne.jp> <20658.30817.183000.810770@gargle.gargle.HOWL> <831ufhz8pl.fsf@gnu.org> <20658.43946.898000.250218@gargle.gargle.HOWL> <83y5hpxc6y.fsf@gnu.org> <87zk24davy.wl%%xmue@d1.dion.ne.jp> <83txscxp21.fsf@gnu.org> <50B67F2A.4020803@gmail.com> <83y5hlul4e.fsf@gnu.org> <20664.37180.453000.739079@gargle.gargle.HOWL> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1354282879 23401 80.91.229.3 (30 Nov 2012 13:41:19 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 30 Nov 2012 13:41:19 +0000 (UTC) Cc: kzhr@d1.dion.ne.jp, monnier@IRO.UMontreal.CA, usr.vm.rocks@gmail.com, emacs-devel@gnu.org To: Uday Reddy Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 30 14:41:31 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1TeQqQ-0003DB-Bz for ged-emacs-devel@m.gmane.org; Fri, 30 Nov 2012 14:41:30 +0100 Original-Received: from localhost ([::1]:39302 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TeQqE-0004tp-SW for ged-emacs-devel@m.gmane.org; Fri, 30 Nov 2012 08:41:18 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:36757) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TeQqC-0004sp-Es for emacs-devel@gnu.org; Fri, 30 Nov 2012 08:41:17 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TeQq5-0006ic-3n for emacs-devel@gnu.org; Fri, 30 Nov 2012 08:41:16 -0500 Original-Received: from mtaout23.012.net.il ([80.179.55.175]:45694) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TeQq4-0006iT-Rj for emacs-devel@gnu.org; Fri, 30 Nov 2012 08:41:09 -0500 Original-Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0MEA00J00ZAPD100@a-mtaout23.012.net.il> for emacs-devel@gnu.org; Fri, 30 Nov 2012 15:41:06 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MEA00JWZZCICR00@a-mtaout23.012.net.il>; Fri, 30 Nov 2012 15:41:06 +0200 (IST) In-reply-to: <20664.37180.453000.739079@gargle.gargle.HOWL> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.175 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:155143 Archived-At: > Date: Fri, 30 Nov 2012 10:58:04 +0000 > From: Uday Reddy > Cc: Uday S Reddy , > kzhr@d1.dion.ne.jp, > monnier@IRO.UMontreal.CA, > emacs-devel@gnu.org > > Eli Zaretskii writes: > > > Is that strange behavior related to encoding and decoding non-ASCII > > characters in any way? > > I can't say either way definitively. > > To give a rough idea of what is happening, when I open an IMAP folder in VM, > it loads the cache folder that has only mail message headers. Then it > fetches the body of the "current message" from the IMAP server and inserts > it in folder buffer at the right place based on the markers that have been > placed there when the cache folder was first parsed, and displays it to the > user. > > The message body is getting inserted at wrong places, which means that the > markers are off somehow. If you do this on a collection of messages that don't have any non-ASCII characters, and now CR-LF style EOLs, does the problem happen then? If it does, then decoding non-ASCII characters is not the root cause.