"Fraga, Eric" <e.fr...@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>