From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Re: A file with 'org-mode rot'?
Date: Sun, 13 Apr 2014 16:53:35 +0200 [thread overview]
Message-ID: <2014-04-13T16-35-36@devnull.Karl-Voit.at> (raw)
In-Reply-To: 87zjjph03b.fsf@gmail.com
* Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> Hello,
>
> Karl Voit <devnull@Karl-Voit.at> writes:
>
>> I am still facing strange behavior and I still do think that we
>> need an org-mode-syntax-checker for Org-mode files that cause
>> problems.
>>
>> Example:
>>
>> | foo | bar | baz |
>> | 42 | | |
>> | 23 | | |
>
> I don't understand what a "syntax checker" has to do with it.
> Notwithstanding the fact that such a checker assumes all Org obeys to
> a single syntax definition, which is what I'm struggling for, but is not
> the case actually, it would report, in this case, that syntax is valid.
> How would that help?
I had some issues where time-stamps of deadlines and logbook were
written in the wrong position, messing up drawers.
A syntax checker is not a 100% sure thing, yes. However, it would
help to get information on unknown drawers, missing :END: lines,
mismatching blocks, and so forth. I am not completely sure how to
achieve this.
However, my (long) Org-mode files with the performance issues is not
a situation I am satisfied. Last week I presented Org-mode at a
Linuxdays-event here in Graz and I had to apologize for all the
weird behavior. This was somewhat embarrassing :-(
> I generated a 32000 lines long file and couldn't reproduce the problem.
> What Org version are you using?
d5484ae 2014-04-12 from the repos.
Probably it has to do with my Emacs binary as well: GNU Emacs
24.3.50.1 (x86_64-pc-linux-gnu, GTK+ Version 3.4.2)
of 2014-01-01 on gkar, modified by Debian
The Emacs on the Windows machine in the office does not show many
issues. However, my configuration is only 95% the same for both
machines.
>> Still not possible: org-agenda-list & org-agenda-write to ICS file.
>> Org-mode is working hard but is in some kind of endless loop. I
>> assume that this also would work when I would change to a small
>> Org-mode file. I can test this if it helps.
>
> It would help. So would an ECM for the reported infloop.
Pfuh, I totally understand this :-)
Wow, I am afraid this will be hard work to generate but I will
schedule it. Please be patient because I have lots of stuff to do
these days.
> Also you can try to set `toggle-debug-on-quit', C-g amid the infloop,
> and report the backtrace.
Sure. After a couple of minutes, I C-g and this is the output:
http://paste.grml.org/1898/
--
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
> get Memacs from https://github.com/novoid/Memacs <
https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github
next prev parent reply other threads:[~2014-04-13 14:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 12:41 A file with 'org-mode rot'? Sharon Kimble
2014-04-03 10:40 ` Karl Voit
2014-04-04 9:11 ` Eric S Fraga
2014-04-04 11:06 ` Eric S Fraga
2014-04-11 9:46 ` Bastien
2014-04-11 15:26 ` Nicolas Goaziou
2014-04-13 11:22 ` Karl Voit
2014-04-13 12:42 ` Nicolas Goaziou
2014-04-13 14:53 ` Karl Voit [this message]
2014-04-13 17:49 ` Nicolas Goaziou
2014-04-13 18:08 ` Erik Iverson
2014-04-15 8:18 ` Karl Voit
2014-04-14 16:34 ` Eric S Fraga
2014-11-11 16:50 ` Karl Voit
2014-11-11 20:43 ` Marco Wahl
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=2014-04-13T16-35-36@devnull.Karl-Voit.at \
--to=devnull@karl-voit.at \
--cc=emacs-orgmode@gnu.org \
--cc=news1142@Karl-Voit.at \
/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).