emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eduardo Mercovich <eduardo@mercovich.net>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: Just sharing another orgmode use: usability tests
Date: Sun, 18 Jun 2017 19:21:13 -0300	[thread overview]
Message-ID: <871sqhym1y.fsf@biologica.mercovich.net> (raw)
In-Reply-To: <87o9tmenv1.fsf@t3610>

Hi Eric.

>> The standard clocking task mechanism will do it fine.
>
> Great.
>
>> However, since there are many multiple small observations along 
>> one task, maybe a capture template is a bit overdo... 

> I find that capturing is a lightweight activity.  It all depends 
> on what
> you expect to have to do.  For instance, I log some activities 
> by simply
> typing "C-c c l COUPLE OF KEYWORDS C-c C-c" and I'm done!  The 
> entry is
> time stamped automatically and it simply allows me to note 
> something
> without really intruding into a workflow.

It could be... maybe I feel it like too much it's because some obs 
are really quite short (like 1 name/place) and I took them as 
lines, so headings or list items are more than enough.
I'll have to try it. :)

OTOH, I just found the perfect timestamping method: org-timer. 
:)))

Best...


-- 
eduardo mercovich

 Donde se cruzan tus talentos 
 con las necesidades del mundo, 
 ahí está tu vocación. 
 (Anónimo)

  reply	other threads:[~2017-06-18 22:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8d18331fde644aa79d32d60d720a8d10@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-06-16  8:25 ` Just sharing another orgmode use: usability tests Eric S Fraga
2017-06-16 14:19   ` Eduardo Mercovich
     [not found]   ` <e24c85840a894ce9bbe7c0b56cfc1d53@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-06-17 13:37     ` Eric S Fraga
2017-06-18 22:21       ` Eduardo Mercovich [this message]
2017-06-15 20:08 Eduardo Mercovich
2017-08-02 15:03 ` Karl Voit
2017-08-03  1:26   ` Eduardo Mercovich

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=871sqhym1y.fsf@biologica.mercovich.net \
    --to=eduardo@mercovich.net \
    --cc=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 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).