From: Ihor Radchenko <yantar92@posteo.net>
To: "Fraga, Eric" <e.fraga@ucl.ac.uk>
Cc: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: is LOCATION not a valid property? org-lint complains!
Date: Tue, 01 Aug 2023 16:22:04 +0000 [thread overview]
Message-ID: <878raupwb7.fsf@localhost> (raw)
In-Reply-To: <873512zrek.fsf@ucl.ac.uk>
"Fraga, Eric" <e.fraga@ucl.ac.uk> writes:
> I don't use org-lint very often but it is indeed an excellent tool when
> an org file somehow gets corrupted in some way. I recently had problems
> adding a new entry into my "diary" file, the file that has all of my
> meetings & appointments [1].
>
> I don't know if this is something new or I simply have never used
> org-lint on a file that has entries similar to those in my diary file
> but, when I do, I get output like this:
>
> : 52 low Potentially misspelled option "LOCATION". Consider "EXPORT_LOCATION".
>
> Should I be using EXPORT_LOCATION? If so, why? That is, why does org
> mode care what property I define? Seems rather strange, to me, somehow.
ox-koma-letter, which you likely use, understands EXPORT_LOCATION
property, but not LOCATION.
This is indeed false-positive in your case.
> I also get quite a few lines like this one:
>
> : 60 low Potentially malformed timestamp. Recognized: <2021-01-29 Fri 16:00-17:00>
>
> I have no idea what is malformed about that timestamp. Am I missing
> something obvious or very subtle?
May you give an example of a timestamp at "60"?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-08-01 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 15:57 is LOCATION not a valid property? org-lint complains! Fraga, Eric
2023-08-01 16:22 ` Ihor Radchenko [this message]
2023-08-01 16:35 ` Fraga, Eric
2023-08-02 6:34 ` Ihor Radchenko
2023-08-02 7:27 ` Fraga, Eric
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=878raupwb7.fsf@localhost \
--to=yantar92@posteo.net \
--cc=e.fraga@ucl.ac.uk \
--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).