From: David Frascone <dave@frascone.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Time Stamps?
Date: Mon, 3 May 2010 15:17:54 -0400 [thread overview]
Message-ID: <x2z9cf5ced21005031217n37579e99h9e307d285454bcfd@mail.gmail.com> (raw)
In-Reply-To: <87iq74yfng.fsf@gollum.intra.norang.ca>
[-- Attachment #1.1: Type: text/plain, Size: 4131 bytes --]
On Mon, May 3, 2010 at 3:00 PM, Bernt Hansen <bernt@norang.ca> wrote:
> Hi David,
>
> Answers are inline.
>
> David Frascone <dave@frascone.com> writes:
>
> > I've been using a lot of the great info at this site
> > (http://doc.norang.ca/org-mode.html) , and I have some questions:
> >
> > When using timestamps, I like the time in there too. And, I like to
> > stamp every entry, so my status looks nice. But, I'm having a couple
> > of problems:
> >
> > 1. Can I make all timestamps put the time? In other words, can I
> > make C-c ! always do the same thing as C-u C-c !
> >
>
> I use a key binding for this: f9-t which creates a timestamp like this
> at point. [2010-05-03 Mon 14:52] The binding for that is documented at
> http://doc.norang.ca/org-mode.html#sec-15_21
>
Duh. Sorry. I thought there would be a way to do it with just a command,
and, at first glance, didn't grok what you were doing with the func.
Consider it stolen. I'm going to re-map something to it. I don't like
using Function keys, because when I am using my macbook w/o a keyboard, I
have to hit a Fn button to get those. But, I'll map it to something. I do
like your f9 map, so, maybe I'll use M-9 or something like that.
>
> > 2. Where should I put the timestamp? Where do you guys think it
> > looks best? Before the text? After? Still getting a feel for
> > things.
>
> Anywhere in the body of the text works fine for me. My remember
> templates put the timestamp after the clock drawer
>
> * TODO blah
> :CLOCK:...
> [2010-05-03 Mon 14:59]
> [[link to stuff]]
>
> but anywhere will work - it's just text.
>
Right. I understand where it gets put. But, now I want to add some notes.
Where would you put it? (And, I know I'm just asking your opinion, because
it is all just text -- I just really like your setup, so I'm using it as my
starting point.
So, for example, here's an entry I took today with a call, refiled it, then
re-edited it. Names have been changed to protect the guilty
some_company.org:
-----
* Title for issue customer is having
** WAITING Phone %:name - %:Some Company -
:PHONE:WAITING:
- State "WAITING" from "" [2010-05-03 Mon 11:19] \\
Waiting on data from Customer
:CLOCK:
:END:
Got a call from Customer this am. He is having problems blah blah.
Will call him back in 10-15
Contact Info: 800-555-5555
[2010-05-03 Mon]
** Talked to Customer again.
[2010-05-03 Mon 11:19]
Conclusion: Probable Diagnosis here. Customer is going to reboot and send
me more data.
*** System Information
**** Some System
1 Gb Data File
60 Threads
Other System Data
**** Performance
9-20 Mb/Sec
**** Configuration
Raid 0 over 4 drives
16 Gb RAM
Blah Blah
**** Symptoms
computer hangs. windows Explorer hangs trying to look at filesystem.
-----
So, this was the result of two calls, captured with remember-phone, then
re-filed into the some_company.org file. I put the datestamps up top, but
I'm not sure if I like them there.
What do you think of that setup?
>
> >
> > 3. Clocking. That site does a lot of it, and I mostly like it. But,
> > I'm not sure how I should clock in in the AM. Almost always, I
> > try to enter something quickly with remember, and I haven't
> > started a clock yet. I'm considering taking out the timing stuff
> > now . . . any pointers?
>
> The first thing I do when I clock-in in the morning is hit either f9-o
> or f9-m to clock in my organization or read mail task (depending on
> which one I start first). From there remember tasks interrupt the clock
> temporarily and clocking continues on whatever I work on until I
> manually clock out.
>
>
I will re-read the clocking portion . . I really like stamping EVERYTHING,
so that I can generate weekly reports easily (This is where I wasted my
time)
I've also got to integrate, somehow, references to my livescribe pen
(annotated conference call notes). And, it'll be nice to backdate
conference calls so that even if I dont' log them, I can log them later. I
know I can . . it's just coming up with an easy way to do it.
[-- Attachment #1.2: Type: text/html, Size: 5534 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-05-03 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 15:23 Time Stamps? David Frascone
2010-05-03 19:00 ` Bernt Hansen
2010-05-03 19:17 ` David Frascone [this message]
2010-05-03 19:35 ` Bernt Hansen
2010-05-11 11:47 ` Daniel Martins
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=x2z9cf5ced21005031217n37579e99h9e307d285454bcfd@mail.gmail.com \
--to=dave@frascone.com \
--cc=bernt@norang.ca \
--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).