From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: Nicolas Goaziou <mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ-wOFGN7rlS/M9smdsby/KFg@public.gmane.org
Subject: Re: [RFC] Change property drawer syntax
Date: Wed, 26 Nov 2014 15:09:51 +0100 [thread overview]
Message-ID: <867fyi59zk.fsf@example.com> (raw)
In-Reply-To: <87sihmq3dd.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org> (Nicolas Goaziou's message of "Thu, 13 Nov 2014 20:58:38 +0100")
Hello Nicoalas,
Nicolas Goaziou wrote:
> Sebastien Vauban writes:
>
>> I've done that but, now, it does not support anymore the structure I had
>> in all my Org files:
>>
>> ** TODO Show typical Org entry
>> SCHEDULED: <2014-11-08 Sat>
>> :LOGBOOK:
>> CLOCK: [2014-11-11 Tue 12:35]--[2014-11-11 Tue 14:19] => 1:44
>> :END:
>>
>> I have the planning lines and the drawers indented at the level of the
>> entry.
>>
>> On the other hand, the "body text" of the entry always begins at
>> column 0. This makes a clear distinction between "meta-stuff" and the
>> contents of the entry itself.
>
> This distinction is not known by Org.
>
> "Meta-stuff" is stuff bound to a headline: planning info and, now,
> properties drawer. OTOH, a LOGBOOK drawer is a regular drawer, which can
> be inserted anywhere within the section. As such, it belong to the body
> of the section.
Would it be a problem to bind the LOGBOOK drawer to the headline as
well (like you did for the PROPERTIES drawer)?
>> Now, with `org-adapt-indentation' set to `t', the whole "block" moves to
>> the right when demoting, and to the left when promoting.
>
> When demoting, everything, i.e., "meta-stuff" and body, is moved to the
> right. When promoting, "meta-stuff" is moved unconditionally (due to
> `org-adapt-indentation'), but line beginning at column 0 prevents the
> body from being moved.
>
> `org-adapt-indentation' is really useful if you indent everything, e.g.,
> using C-j to start new lines. Here you are using something in-between.
Did not know I wasn't conforming to the common habits...
From what I've seen,
- Planning info and drawers are typically "indented" (see Worg, the
Org-mode manual and http://doc.norang.ca/org-mode.html for different
types of drawers, sometimes including the PROPERTIES one), what makes
those info stand out from the "notes" themselves.
- Body text is often not indented (see Worg files themselves), which is
much easier for diffing different versions of the same file).
> I suggest to keep `org-adapt-indentation' to nil
OK.
> and "fix" meta stuff and logbook by indentation by hand, using
> `org-after-demote-entry-hook' and `org-after-promote-entry-hook'.
That could do it when promoting or demoting entries. But that's not
sufficient: now, whenever logging a state change (from TODO to DONE, for
example), a drawer gets created in column 0, instead of at the right
indentation level of the headline.
The same kind of problems occurred with a repeating timestamp:
--8<---------------cut here---------------start------------->8---
** TODO Noter les index de consommation
DEADLINE: <2014-11-23 Sun 20:00 ++7d -0d>
:PROPERTIES:
:LAST_REPEAT: [2014-11-25 Tue 16:46]
:END:
:LOGBOOK:
(...)
- State "DONE" from "TODO" [2014-11-17 Mon 13:36]
:END:
--8<---------------cut here---------------end--------------->8---
became (after C-c C-t d):
--8<---------------cut here---------------start------------->8---
** TODO Noter les index de consommation
DEADLINE: <2014-11-30 Sun 20:00 ++7d -0d>
:PROPERTIES:
:LAST_REPEAT: [2014-11-25 Tue 16:46]
:END:
:LOGBOOK:
(...)
- State "DONE" from "TODO" [2014-11-17 Mon 13:36]
- State "DONE" from "TODO" [2014-11-25 Tue 16:46]
:END:
--8<---------------cut here---------------end--------------->8---
^ DEADLINE in column 0.
Am I missing something?
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2014-11-26 14:09 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 14:42 [RFC] Change property drawer syntax Nicolas Goaziou
2014-10-14 14:55 ` Andreas Leha
2014-10-14 15:55 ` Nicolas Goaziou
2014-10-14 16:18 ` Eric Abrahamsen
2014-10-14 19:26 ` Nicolas Goaziou
2014-10-14 16:25 ` Michael Brand
2014-10-14 19:38 ` Nicolas Goaziou
2014-10-15 17:25 ` Michael Brand
2014-10-15 20:52 ` Nicolas Goaziou
2014-10-15 2:58 ` Eric Abrahamsen
2014-10-15 10:11 ` Nicolas Goaziou
2014-10-15 11:22 ` Eric Abrahamsen
2014-10-15 7:38 ` Rainer M Krug
2014-10-15 10:14 ` Nicolas Goaziou
2014-10-15 11:27 ` Rainer M Krug
2014-10-20 22:35 ` Rasmus
2014-10-26 15:24 ` Nicolas Goaziou
2014-10-28 13:27 ` Nicolas Goaziou
2014-11-06 10:21 ` Sebastien Vauban
2014-11-08 13:46 ` Nicolas Goaziou
2014-11-10 10:19 ` Sebastien Vauban
2014-11-10 10:41 ` Nicolas Goaziou
2014-11-10 11:04 ` Sebastien Vauban
2014-11-10 11:51 ` Nicolas Goaziou
2014-11-10 12:55 ` Sebastien Vauban
2014-11-12 10:40 ` Sebastien Vauban
2014-11-13 19:58 ` Nicolas Goaziou
[not found] ` <87sihmq3dd.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
2014-11-26 14:09 ` Sebastien Vauban [this message]
2014-10-31 13:10 ` Christian Egli
2014-10-31 16:10 ` John Hendy
2014-11-03 8:27 ` Christian Egli
2014-11-03 8:33 ` Nicolas Goaziou
2014-11-01 10:57 ` Nicolas Goaziou
2014-11-03 8:38 ` Christian Egli
2014-11-03 20:14 ` Nicolas Goaziou
2014-11-12 11:01 ` Sebastien Vauban
2014-11-12 11:11 ` Sebastien Vauban
2014-11-26 14:18 ` Sebastien Vauban
2014-11-26 23:37 ` Nicolas Goaziou
2014-11-27 9:24 ` Sebastien Vauban
2014-11-28 22:16 ` Nicolas Goaziou
2014-12-05 14:33 ` Puneeth Chaganti
2014-12-05 23:31 ` Nicolas Goaziou
2014-12-06 6:42 ` Puneeth Chaganti
2014-12-06 20:36 ` Nicolas Goaziou
2014-11-14 8:36 ` Nicolas Goaziou
[not found] ` <87ppcqnpq7.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
2014-11-14 13:58 ` Sebastien Vauban
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=867fyi59zk.fsf@example.com \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org \
--cc=public-emacs-orgmode-mXXj517/zsQ-wOFGN7rlS/M9smdsby/KFg@public.gmane.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).