emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: David Rogers <davidandrewrogers@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: Can Org warn me if I create a time conflict?
Date: Tue, 17 Dec 2019 14:05:38 -0800	[thread overview]
Message-ID: <85B12EB9-0B93-456A-AAA5-6A49356E1F4F@gmail.com> (raw)

It's currently possible for me to create two meeting times, one from 8:00-10:00 tomorrow and the other from 9:00-11:00 tomorrow. 

When both are mentioned in the same sentence, as above, it's easy to recognize that the two meetings are probably incompatible. But org-mode allows agenda items to be created at different times and in different files; it's possible to create Meeting #1 far in advance, have enough time to forget that Meeting #1 exists, and then create Meeting #2 covering the same period of time. (Compare this with the wall calendar made of paper, where if I try to add Meeting #2 I'll be forced to write it in the same physical space, and therefore automatically be alerted before making the error.)

Is there any method to get org-mode to alert me (by an error message, or a red mark in the agenda, or whatever) that I've created a conflict - specifically, a method that doesn't involve me having to remember to perform any type of conflict-checking myself? If I could remember to do things like conflict checks, I wouldn't really need org-agenda anyway. :-)

I realize that it's likely some situations *do* require timed events to happen concurrently - but I don't believe that they're the usual case for an individual. Having an "ignore conflict" or "accept anyway" type of option would make sense to me for such situations. 

-- 
Thanks
David

             reply	other threads:[~2019-12-17 22:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-17 22:05 David Rogers [this message]
2019-12-18  6:20 ` Can Org warn me if I create a time conflict? Fraga, Eric
2019-12-18  8:02 ` Allen Li
2019-12-18 16:38   ` Mikhail Skorzhinskiy
2019-12-19  6:10     ` David R
2019-12-19  8:23     ` David R

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=85B12EB9-0B93-456A-AAA5-6A49356E1F4F@gmail.com \
    --to=davidandrewrogers@gmail.com \
    --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).