emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Daniel Clemente <n142857@gmail.com>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Bug in clocking in: the list becomes corrupted by the CLOCK drawer
Date: Wed, 11 Feb 2009 14:02:24 +0100	[thread overview]
Message-ID: <87wsbxjfdr.fsf@CPU107.opentrends.net> (raw)
In-Reply-To: <7B2A6D57-FF26-4BA6-92F6-D520183410A9@uva.nl> (Carsten Dominik's message of "Wed, 11 Feb 2009 13:21:33 +0100")

>>  Of course, if the user uses indentation at the first line,
> The true problem here is:  I am such a user. :-)

  There are also users who write lists after entries... and the default behaviour is wrong for them. I don't think it's needed to change their habits and force them to write a blank line.
  I agree that it's difficult because it's not very clear where the metadata section (CLOCK/DEADLINE/SCHEDULE, drawers, …) ends.
  Maybe it can be made that: a list (of any tipe) at line beginning (no indentation) will break the metadata section and start the content section.

-- Daniel

* learn the alphabet
  CLOCK: [2009-01-26 dl 17:04]--[2009-01-26 dl 18:04] =>  1:00
- a
- b
- c
- d


  parent reply	other threads:[~2009-02-11 13:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09 15:04 Bug in clocking in: the list becomes corrupted by the CLOCK drawer Daniel Clemente
2009-02-11 10:34 ` Carsten Dominik
2009-02-11 11:09   ` Daniel Clemente
2009-02-11 12:21     ` Carsten Dominik
2009-02-11 12:24       ` Manish
2009-02-11 13:02       ` Daniel Clemente [this message]
2009-02-11 14:10         ` Carsten Dominik
2009-02-12 10:49           ` Daniel Clemente
2009-02-11 15:03   ` Bernt Hansen
2009-02-11 15:18     ` Carsten Dominik
2009-02-11 15:31       ` Bernt Hansen
2009-02-11 15:27     ` Bernt Hansen

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:

  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=87wsbxjfdr.fsf@CPU107.opentrends.net \
    --to=n142857@gmail.com \
    --cc=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \


* 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


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).