From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Karl Voit <devnull@Karl-Voit.at>
Cc: Karl Voit <news1142@Karl-Voit.at>, emacs-orgmode@gnu.org
Subject: Re: Org-lint
Date: Thu, 28 May 2015 19:28:32 +0200 [thread overview]
Message-ID: <87k2vswr0f.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <2015-05-28T14-40-09@devnull.Karl-Voit.at> (Karl Voit's message of "Thu, 28 May 2015 14:45:52 +0200")
Hello,
Karl Voit <devnull@Karl-Voit.at> writes:
> Who do I have to contact, when I've got ideas of checks that
> corrupted my Org-mode files?
You can implement checks and send them to the ML. You can also suggest
them on the ML.
> For example, I have the issue that once upon a Org-mode-Git-
> checkout, the property drawers got corrupted over time: duplicate
> LOGBOOKs
Duplicate LOGBOOK drawers is not an error. You could, for example, use
the second one as an archive. More generally, you can have multiple
drawers with the same name in a given entry.
> and order of LOGBOOK and PROPERTIES is switched. I noticed
> it, when many drawers were already broken. I still find them in my
> files from time to time :-(
Org Lint already looks for PROPERTIES drawers not at their expected
location.
> Another one would be duplicate IDs.
Org Lint checks this already, but it proceed document-wise. It will not
find duplicate ID across files.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2015-05-28 17:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-26 23:03 Org-lint and #+call lines Thomas S. Dye
2015-04-27 6:54 ` Nicolas Goaziou
2015-04-27 7:23 ` Thomas S. Dye
2015-04-27 7:39 ` Nicolas Goaziou
2015-04-27 11:38 ` Nicolas Goaziou
2015-04-27 15:25 ` Thomas S. Dye
2015-04-28 5:44 ` Thomas S. Dye
2015-04-28 7:57 ` Nicolas Goaziou
2015-04-28 20:04 ` Thomas S. Dye
2015-04-28 20:18 ` Nicolas Goaziou
2015-05-28 12:45 ` Org-lint (was: Org-lint and #+call lines) Karl Voit
2015-05-28 17:28 ` Nicolas Goaziou [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=87k2vswr0f.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=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).