From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Cc: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Bug? SCHEDULED lines treated differently when text precedes them
Date: Fri, 06 Sep 2019 11:08:20 +1000 [thread overview]
Message-ID: <87o8zyb5a3.fsf@gmail.com> (raw)
In-Reply-To: <87v9u6am3q.fsf@neron>
maybe add org-lint to the after-save-hook - maybe something like
(untested)
(add-hook 'after-save-hook (lamda ()
(when (eq buffer-mode 'org-mode)
(org-lint))))
Christoph Groth <christoph@grothesque.org> writes:
> Nicolas Goaziou wrote:
>> Christoph Groth <christoph@grothesque.org> writes:
>>
>> > I understand now that Org does what it should. However, I find this
>> > behavior quite dangerous. It caught me after more than 10 years of
>> > using Org. If there's a list of long-term issues with Org
>> > somewhere, this problem may deserve being added to it.
>>
>> I don't think there is much to fix here. In any case, the command
>> `org-lint' warns you about this kind of error.
>
> Thanks for mentioning 'org-lint'. I just ran it on my agenda files, and
> it found multiple errors in most of my (very long) files. So at least
> for me (and likely for other Org users as well), the risk of missing
> TODO items is real - that's a rather serious problem for a task manager!
>
> My agenda files are populated using 'org-capture'. Do you have
> suggestions how to best integrate org-lint transparently into everyday
> org usage? For example, files could be linted automatically before they
> are saved, or before a new item is captured.
--
Tim Cross
next prev parent reply other threads:[~2019-09-06 1:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 12:51 Bug? SCHEDULED lines treated differently when text precedes them Christoph Groth
2019-09-05 13:00 ` Nicolas Goaziou
2019-09-05 13:38 ` Christoph Groth
2019-09-05 13:40 ` Nicolas Goaziou
2019-09-05 13:58 ` Christoph Groth
2019-09-06 1:08 ` Tim Cross [this message]
2019-09-05 14:02 ` Carsten Dominik
2019-09-06 0:52 ` Tim Cross
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=87o8zyb5a3.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).