From: Bastien <bzg@altern.org>
To: Sebastien Vauban
<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: logdone enhancement
Date: Wed, 27 Feb 2013 13:22:46 +0100 [thread overview]
Message-ID: <87ehg2eyjt.fsf@bzg.ath.cx> (raw)
In-Reply-To: <86wqtu8446.fsf@somewhere.org> (Sebastien Vauban's message of "Wed, 27 Feb 2013 11:04:25 +0100")
Hi Sébastien,
"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
> But first, For me, the question comes down to: do we agree that John (in this
> case) won't be allowed anymore to write such an entry?
>
> *** NOTE Assets:Receivable:CEG
> #+begin_src sh :results value :exports results
> ledger reg --inject=Expected '^income:ceg'
> ledger reg --sort date -b 2007 receivable:CEG
> #+end_src
> :PROPERTIES:
> :ID: 8BEF6C42-8B23-495B-9421-3810B58907A1
> :VISIBILITY: folded
> :CREATED: [2010-06-18 Fri 07:37]
> :END:
No. The rule is about the SCHEDULED line, not about the :PROPERTIES:
drawer. So John is allowed to write such an entry.
`org-fixup-indentation' is just a way to _improve_ the indentation,
so it should do its best in order to align SCHEDULED cookies (and
friends) *and* drawers. If it can't align some drawers, it should
just ignore them. And be happy with what it did.
Thanks for testing,
--
Bastien
next prev parent reply other threads:[~2013-02-27 12:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 6:21 logdone enhancement Arun Persaud
2013-02-27 8:33 ` Bastien
2013-02-27 9:15 ` Sebastien Vauban
2013-02-27 9:25 ` Bastien
2013-02-27 10:04 ` Sebastien Vauban
2013-02-27 12:22 ` Bastien [this message]
2013-02-27 18:39 ` Arun Persaud
2013-02-27 19:08 ` Nick Dokos
2013-02-27 20:09 ` Arun Persaud
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=87ehg2eyjt.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
--cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.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).