emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Dominik Schrempf <dominik.schrempf@gmail.com>
Cc: Emacs Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: Feature Request: Time Line in Lab Book
Date: Tue, 5 Apr 2016 14:34:20 +0100	[thread overview]
Message-ID: <87shz0yyar.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87egaktd26.fsf@gmail.com> (Dominik Schrempf's message of "Tue, 05 Apr 2016 15:12:01 +0200")

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

On Tuesday,  5 Apr 2016 at 15:12, Dominik Schrempf wrote:
> Do I make myself clear now?

Yes and I think the key would be to ensure that every note etc. has a
heading.  This avoids all the problems you have with non-terminated
entries.  Avoid a flat structure and org works very well.

For instance, if you use a capture rule based on a date-tree, you can
easily add to the end of the file while still add notes later to any
previous entry.  Plus you have the advantage of knowing when notes were
added.  See screenshot where I have added three notes and then went and
added some text to the first note I took today.


[-- Attachment #2: screendump-20160405142955.png --]
[-- Type: image/png, Size: 48293 bytes --]

[-- Attachment #3: Type: text/plain, Size: 149 bytes --]


The notes were added using my journal capture rule posted earlier.

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.92.1, Org release_8.3.4-668-g809a83

  reply	other threads:[~2016-04-05 13:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-31  8:12 Feature Request: Time Line in Lab Book Dominik Schrempf
2016-03-31  8:36 ` Eric S Fraga
2016-03-31 10:53   ` Dominik Schrempf
2016-03-31 10:58 ` Nick Dokos
2016-03-31 19:44 ` John Hendy
2016-04-05 13:12   ` Dominik Schrempf
2016-04-05 13:34     ` Eric S Fraga [this message]
2016-04-05 20:18       ` Charles Millar
2016-04-05 22:23     ` John Hendy

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=87shz0yyar.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=dominik.schrempf@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).