all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: emacs-orgmode@gnu.org
Subject: Re: agenda mode overlapping dates
Date: Sat, 17 Jun 2017 19:09:33 +0100	[thread overview]
Message-ID: <87o9tmcwpu.fsf@t3610> (raw)
In-Reply-To: <839132fa8ab24958b451e39bdf274625@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> (Uwe Brauer's message of "Sat, 17 Jun 2017 16:39:15 +0000")

[-- Attachment #1: Type: text/plain, Size: 792 bytes --]

On Saturday, 17 Jun 2017 at 16:39, Uwe Brauer wrote:
>    > On Friday, 16 Jun 2017 at 21:05, Uwe Brauer wrote:
>    > [...]
>
>
>    > The v c sequence invokes the clock checking code.  It has nothing to do
>    > with timestamps but looks instead for gaps and overlaps in your
>    > clocking.  If you clock those projects, you will have the information
>    > that this special check is for.
>
> Thanks but could you provide me with a working example?

Difficult to provide an example (if you meant an org file).  Try the
following: pick a task and clock in.  Work on it.  Clock out.  Go have a
coffee (substitute drink of choice :-)).  Come back.  Clock in to same
or different task.  Bring up agenda view and do "v c".

-- 
: Eric S Fraga via Emacs 26.0.50, Org release_9.0.8-563-g27c2ae

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

  parent reply	other threads:[~2017-06-17 18:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <28765412b4464f86bf61bb788c2c19d0@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-06-17 13:41 ` agenda mode overlapping dates Eric S Fraga
2017-06-17 16:39   ` Uwe Brauer
     [not found]   ` <839132fa8ab24958b451e39bdf274625@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-06-17 18:09     ` Eric S Fraga [this message]
2017-06-16 21:05 Uwe Brauer

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o9tmcwpu.fsf@t3610 \
    --to=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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.