From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Francis J. Monari, Esquire" <monarifj.esq@juno.com>
Cc: The Monaris <monarifjmk@verizon.net>, emacs-orgmode@gnu.org
Subject: Re: Bug: Drawers question [8.2.10 (8.2.10-30-gca21b7-elpa @ c:/USR/FJM/APP/.emacs.d/elpa/org-20150126/)]
Date: Sat, 21 Feb 2015 18:25:53 +0100 [thread overview]
Message-ID: <87k2zb18im.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <54E8A27B.7070003@juno.com> (Francis J. Monari's message of "Sat, 21 Feb 2015 10:21:31 -0500")
Hello,
"Francis J. Monari, Esquire" <monarifj.esq@juno.com> writes:
> Questions about Drawers:
> * Is it wise to have drawers with duplicate names under the same
> heading?
I don't see any problem with this.
> * I have noticed that in some respects list items identified by “- [ ] "
> are second class citizens (they have some aspects of headings, but not
> all). Is it wise or recommended (in terms of the the development of org
> mode) to place draws under these list items?
Syntax allows drawers within lists.
> * Is it possible to specify a “canonical” order for drawers?
> e.g. PROPERTIES first, LOGBOOK second, etc.
PROPERTIES always comes first, i.e., it will be invalid for a LOGBOOK to
appear before PROPERTIES in Org 8.3.
> When org mode changes the file (I have noticed this with adding notes to
> the LOGBOOK drawer), sometimes the LOGBOOK drawer “jumps” ahead of the
> PROPERTIES drawer.
> * Sometimes, when org mode changes the file (I have not noticed a
> pattern), spaces are added after the “:END:” for the drawer. Is this
> normal or expected?
These points are fixed in Org development branch.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2015-02-21 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-21 15:21 Bug: Drawers question [8.2.10 (8.2.10-30-gca21b7-elpa @ c:/USR/FJM/APP/.emacs.d/elpa/org-20150126/)] Francis J. Monari, Esquire
2015-02-21 17:25 ` Nicolas Goaziou [this message]
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=87k2zb18im.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=monarifj.esq@juno.com \
--cc=monarifjmk@verizon.net \
/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).