From: Colin Baxter <m43cap@yandex.com>
To: "Tamulis, Andrius" <andriust@att.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: malformed property drawers [8.3.6 (8.3.6-3-gf46b92-elpa @ c:/Users/atamulis/.emacs.d/elpa/org-20160919/)]
Date: Sun, 02 Oct 2016 08:14:09 +0100 [thread overview]
Message-ID: <871szz6x4u.fsf@yandex.com> (raw)
In-Reply-To: <e6d2b849-3510-9691-c9af-3733e532f3c7@att.net> (Andrius Tamulis's message of "Wed, 28 Sep 2016 16:14:12 -0500")
On Wed, Sep 28 2016, Tamulis, Andrius wrote:
--------- Snip -------------
>
> But the better idea is to forget "fixing" these drawers. Is it truly that important to have the
> SCHEDULED and DEADLINE in the line below the heading, and the PROPERTIES drawer directly
> beneath? I see no programming advantage, since you need to search for these strings anyway. And I
> don't like the way it looks: I use org-mode to keep todo lists and notes, I need to read the notes and
> instructions I wrote to myself. These notes and instructions often are longer than the headline, so I
> naturally keep reading from the headline to the line below - and then I have to skip lines with code in
> them. And I'm not the only one who does not like this setup: there's code out there to completly hide
> the PROPERTIES drawer so that it does not interrupt your reading.
> (http://stackoverflow.com/questions/17478260/completely-hide-the-properties-drawer-in-org-mode).
>
> So: put SCHEDULED, DEADLINE, and drawers anywhere in the item! And stop fixing the drawers!
>
Having experienced the same problem, I totally agree.
Colin.
next prev parent reply other threads:[~2016-10-02 7:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dff14d39-03e3-3bf7-3285-637b9047b2e1@att.net>
2016-09-28 21:14 ` Bug: malformed property drawers [8.3.6 (8.3.6-3-gf46b92-elpa @ c:/Users/atamulis/.emacs.d/elpa/org-20160919/)] Tamulis, Andrius
2016-10-02 7:14 ` Colin Baxter [this message]
2016-10-02 7:32 ` Nicolas Goaziou
2016-10-03 4:52 ` Tamulis, Andrius
2016-10-03 5:43 ` Colin Baxter
2016-10-03 16:31 ` Nicolas Goaziou
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=871szz6x4u.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=andriust@att.net \
--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).