From mboxrd@z Thu Jan 1 00:00:00 1970 From: M Subject: Re: user-error: :END: line missing at position 3413 Date: Sat, 18 Jan 2014 07:03:21 +0100 Message-ID: References: <20140117233315.04106f91@london> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40206) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W4P0G-0005Nd-De for Emacs-orgmode@gnu.org; Sat, 18 Jan 2014 01:03:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W4P0B-000658-MQ for Emacs-orgmode@gnu.org; Sat, 18 Jan 2014 01:03:32 -0500 Received: from mout.web.de ([212.227.17.12]:53564) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W4P0B-00064w-CQ for Emacs-orgmode@gnu.org; Sat, 18 Jan 2014 01:03:27 -0500 Received: from [192.168.2.13] ([91.45.157.249]) by smtp.web.de (mrweb002) with ESMTPSA (Nemesis) id 0MJTDf-1W1v5r1sXz-0038Bk for ; Sat, 18 Jan 2014 07:03:25 +0100 In-Reply-To: <20140117233315.04106f91@london> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Emacs-orgmode@gnu.org Cc: Sharon Kimble > Von: Sharon Kimble > Datum: Fri, 17 Jan 2014 23:33:15 +0000 > An: > Betreff: [O] user-error: :END: line missing at position 3413 > > I've updated my emacs to 'Emacs 24.3.50.1' 2014-01-01 on prometheus, > modified by Debian, and updated org from ELPA. > > But now I cant get it to load because it always shows > 'user-error: :END: line missing at position 3413'. I asked about it on > #emacs on IRC, and was told this is something to do with org-mode. So, > can you help me track it down please? Hi Sharon, I had the same problem several times. Somehow, I seemed to have deleted the :END: line of a Log Drawer in org-mode. It recently helped me to start Emacs with the debug-init option like this: emacs --debug-init Then in the Messages log, I found a trace to the corresponding org-file and then after opening the file in a buffer you can jump to the line where the problem occurs with M-x goto-char 3413 (in your case) There were 2 other solutions proposed which I have not tested yet (see attached messages below). Kind regards Martin ------ Weitergeleitete Nachricht > Von: Bastien > Datum: Tue, 14 Jan 2014 21:52:31 +0100 > An: Martin Beck > Cc: emacs orgmode-mailinglist > Betreff: Re: File mode specification error: (error ":END: line missing at > position 63362") > > Hi Martin, > > maybe you can use this helper function: > > (defun bzg-find-corrupted-property-drawers () > "Find corrupted property drawers." > (interactive) > (let (msgs) > (save-excursion > (goto-char (point-min)) > (while (search-forward ":PROPERTIES:" nil t) > (let ((search-end (save-excursion (org-end-of-subtree t)))) > (if (not (search-forward ":END:" search-end t)) > (push (format "Missing :END: at %d in %s\n" > (point) (buffer-name)) > msgs))))) > (if (not msgs) > (message "No corrupted property drawers") > (switch-to-buffer-other-window " *Org missing :END:") > (mapcar 'insert msgs)))) > > A bit rought at the edges, but perhaps useful. > > -- > Bastien ------ Ende der weitergeleiteten Nachricht ------ Weitergeleitete Nachricht > Von: Brian Wood > Organisation: UC Berkeley > Datum: Mon, 04 Mar 2013 13:12:56 -0800 > An: > Betreff: Re: [O] [OT]: Search for missing :END: > > I just found a few of these errors in *Messages* and since I have > 20 > .org files, I used this approach > > cd ~/orgmode > > # this gives me the byte offset & the filename for each matching line > grep -br 'CLOCK: ' * > ~/tmp/org-missing-end.txt > > #this searches within a few bytes of the byte offset reported by emacs > grep -E ":3007.:" ~/tmp/org-missing-end.txt > > Searching within a few bytes was not necessary. In my case I found a > ":CLOCK:" string at the byte-offset in the error message. > > -- > Brian Wood > Applications Programmer > UC Berkeley IST > > ------ Ende der weitergeleiteten Nachricht