emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sharon Kimble <boudiccas@talktalk.net>
To: M <Elwood151@web.de>
Cc: Emacs-orgmode@gnu.org
Subject: Re: user-error: :END: line missing at position 3413
Date: Sat, 18 Jan 2014 07:32:16 +0000	[thread overview]
Message-ID: <20140118073216.61817a21@london> (raw)
In-Reply-To: <CEFFD7B9.1AA65%Elwood151@web.de>

[-- Attachment #1: Type: text/plain, Size: 4400 bytes --]

On Sat, 18 Jan 2014 07:03:21 +0100
M <Elwood151@web.de> wrote:

> > Von: Sharon Kimble <boudiccas@talktalk.net>
> > Datum: Fri, 17 Jan 2014 23:33:15 +0000
> > An: <Emacs-orgmode@gnu.org>
> > 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).

Thanks for this Martin, it set me on the right track to solving it. It
puzzled me why one particular org file would load but nowt else, so I
had a close look at it. There were no missing :END: but the goto-char
was directing me to a specific place in the file, this file was my
'organizer.org' storing all details of hospital appointments, there was
absolutely no way that it could be corrupted. And then I remembered
that I had restored the file from an autosave backup, at which point I
copied everything over to a organizer.txt, saved and restarted emacs.
And everything just loaded up so nicely, problem solved! So I then saved
the organiser.txt as organiser.org, and it still all works nicely.

Thanks
Sharon.
> 
> Kind regards
> 
> Martin
> 
> ------ Weitergeleitete Nachricht
> > Von: Bastien <bzg@gnu.org>
> > Datum: Tue, 14 Jan 2014 21:52:31 +0100
> > An: Martin Beck <elwood151@web.de>
> > Cc: emacs orgmode-mailinglist <emacs-orgmode@gnu.org>
> > 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 <bwood@berkeley.edu>
> > Organisation: UC Berkeley
> > Datum: Mon, 04 Mar 2013 13:12:56 -0800
> > An: <emacs-orgmode@gnu.org>
> > 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
> 
> 
> 



-- 
A taste of linux = http://www.sharons.org.uk
efever = http://www.efever.blogspot.com/
efever = http://sharon04.livejournal.com/
my git repo = https://bitbucket.org/boudiccas/dots
Debian testing, Fluxbox 1.3.5, LibreOffice 4.1.4.2
Registered Linux user 561944

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2014-01-18  7:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17 23:33 user-error: :END: line missing at position 3413 Sharon Kimble
2014-01-18  6:03 ` M
2014-01-18  7:32   ` Sharon Kimble [this message]

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.orgmode.org/

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

  git send-email \
    --in-reply-to=20140118073216.61817a21@london \
    --to=boudiccas@talktalk.net \
    --cc=Elwood151@web.de \
    --cc=Emacs-orgmode@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/org-mode.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).