emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Marcin Borkowski <mbork@amu.edu.pl>
Cc: Org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Clocking in on non-org files
Date: Tue, 05 Nov 2013 18:16:45 +0100	[thread overview]
Message-ID: <87y5526a6a.fsf@bzg.ath.cx> (raw)
In-Reply-To: <20131006095638.6069d50d@aga-netbook> (Marcin Borkowski's message of "Sun, 6 Oct 2013 09:56:38 +0200")

Hi Marcin,

Marcin Borkowski <mbork@amu.edu.pl> writes:

> I have a bunch of TODO items connected with LaTeX files (in general:
> projects) I'm working on.  I was wondering whether it might be possible
> and/or wise to set things up so that I could clock in (C-c C-x C-i) in
> a buffer containing such a file.

I have this capture template :

(setq org-capture-templates
      '(

        ("IC" "Information read (keep clocking)" entry
         (file+headline "~/org/garden.org" "Infos")
         "* TODO %?%a :Read:\n  :PROPERTIES:\n  :CAPTURED: %U\n  :END:\n\n%i"
         :prepend t :clock-in t :immediate-finish t :clock-keep t :jump-to-captured t)

       ))

which I use in such cases: capturing does not take longer than
clocking in, and I have both the capture and the running clock.

Hope this helps,

-- 
 Bastien

  reply	other threads:[~2013-11-05 17:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-06  7:56 Clocking in on non-org files Marcin Borkowski
2013-11-05 17:16 ` Bastien [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-10-06 12:07 Marcin Borkowski
2013-10-06 15:11 ` Suvayu Ali
2013-10-06 21:26   ` Marcin Borkowski
2014-08-16 12:12     ` Marcin Borkowski
2014-08-16 12:31       ` Marcin Borkowski
2014-08-16 13:47         ` Marcin Borkowski
2014-08-16 14:37           ` Marcin Borkowski
2014-08-16 14:01       ` Thorsten Jolitz
2014-08-16 14:42         ` Marcin Borkowski
2014-08-16 15:02           ` Thorsten Jolitz
2014-08-16 15:13             ` Marcin Borkowski
2014-08-16 15:35               ` Thorsten Jolitz

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=87y5526a6a.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=mbork@amu.edu.pl \
    /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).