From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Uday Reddy Newsgroups: gmane.emacs.devel Subject: Emacs24 unpredictable behaviour [Was: coding system problems] Date: Sun, 2 Dec 2012 00:46:09 +0000 Message-ID: <20666.42193.203000.238289@gargle.gargle.HOWL> 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> <83624nus2j.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1354409203 12386 80.91.229.3 (2 Dec 2012 00:46:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 2 Dec 2012 00:46:43 +0000 (UTC) Cc: monnier@IRO.UMontreal.CA, Uday Reddy , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Dec 02 01:46:55 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 1Texhr-0001WA-IQ for ged-emacs-devel@m.gmane.org; Sun, 02 Dec 2012 01:46:51 +0100 Original-Received: from localhost ([::1]:47699 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Texhg-0004cv-4B for ged-emacs-devel@m.gmane.org; Sat, 01 Dec 2012 19:46:40 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:51248) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Texhc-0004cf-TB for emacs-devel@gnu.org; Sat, 01 Dec 2012 19:46:37 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Texhb-00021E-Sr for emacs-devel@gnu.org; Sat, 01 Dec 2012 19:46:36 -0500 Original-Received: from sun60.bham.ac.uk ([147.188.128.137]:61868) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Texhb-000215-MU; Sat, 01 Dec 2012 19:46:35 -0500 Original-Received: from [147.188.128.127] (helo=bham.ac.uk) by sun60.bham.ac.uk with esmtp (Exim 4.72) (envelope-from ) id 1TexhY-0000Kv-Pk; Sun, 02 Dec 2012 00:46:32 +0000 Original-Received: from mx1.cs.bham.ac.uk ([147.188.192.53]) by bham.ac.uk (envelope-from ) with esmtp (Exim 4.72) id 1TexhY-00004k-Fj using interface smart1.bham.ac.uk; Sun, 02 Dec 2012 00:46:32 +0000 Original-Received: from gromit.cs.bham.ac.uk ([147.188.193.16] helo=MARUTI.cs.bham.ac.uk) by mx1.cs.bham.ac.uk with esmtp (Exim 4.51) id 1TexhY-0000v0-O5; Sun, 02 Dec 2012 00:46:32 +0000 In-Reply-To: <83624nus2j.fsf@gnu.org> X-Mailer: VM 8.2.0b under 24.2.1 (i386-mingw-nt5.1.2600) X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 147.188.128.137 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:155166 Archived-At: Eli Zaretskii writes: > 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. Messages are always made of ASCII characters. So, that is not an issue. The folder I am working with has Unix line endings. The folder is loaded into a unibyte buffer. (VM always does that.) Here is a sample piece of code that I inserted into the middle of VM, to figure out how Emacs24 is behaving: (defun vm-test-retrieve (mm) (save-current-buffer (set-buffer (vm-buffer-of mm)) (goto-char (vm-text-of mm)) (debug nil (list (point) (marker-position (vm-text-of mm)) (= (point) (marker-position (vm-text-of mm))) )) (debug nil (= (point) (marker-position (vm-text-of mm)))) )) Since goto-char is going to (vm-text-of mm), the first debug should print two identical numbers and `t' for the comparison. However, here is an instance where it doesn't: Debugger entered: ((99947 98744 nil)) vm-test-retrieve([[# # nil # # #]...]) Even more crazily, for another message, the first debug prints this: Debugger entered: ((104925 104925 t)) vm-test-retrieve([[# # nil # # #]...]) and the second debug prints this: Debugger entered: (nil) vm-test-retrieve([[# # nil # # #]...]) How does the point change from one debug to the next? I have no idea. -------- The good news is that these problems may not have anything to do with the buffer-file-type changes. I see them as far as back as revision 107968. Cheers, Uday