emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Org-lint (was: Org-lint and #+call lines)
Date: Thu, 28 May 2015 14:45:52 +0200	[thread overview]
Message-ID: <2015-05-28T14-40-09@devnull.Karl-Voit.at> (raw)
In-Reply-To: m2egn6pk4q.fsf@tsdye.com

* Thomas S. Dye <tsd@tsdye.com> wrote:
>
> Org-lint is a big help picking up an old project.  Thanks Nicolas.

Hey, I missed org-lint so far.

However, I was desperately asking for an Org-mode syntax validation
multiple times for a long time.[1]

Who do I have to contact, when I've got ideas of checks that
corrupted my Org-mode files? 

For example, I have the issue that once upon a Org-mode-Git-
checkout, the property drawers got corrupted over time: duplicate
LOGBOOKs 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 :-(

Another one would be duplicate IDs.

[1] http://thread.gmane.org/gmane.emacs.orgmode/84494/focus=84864
    and others

-- 
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

  parent reply	other threads:[~2015-05-28 12:46 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 ` Karl Voit [this message]
2015-05-28 17:28   ` Org-lint Nicolas Goaziou

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=2015-05-28T14-40-09@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).