all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
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 09:32:02 +0200	[thread overview]
Message-ID: <877f9rw6j1.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <e6d2b849-3510-9691-c9af-3733e532f3c7@att.net> (Andrius Tamulis's message of "Wed, 28 Sep 2016 16:14:12 -0500")

Hello,

"Tamulis, Andrius" <andriust@att.net> writes:

> There is a problem even if I want to "fix" these drawers by hand.
> There are many, many drawers, and the fix is long and tedious:

It isn't. ORG-NEWS file provide a function to do the fixing for you.

> I think that you should possible go back to the way it was before the
> "fix the properties" patch. If it is terribly important to fix the
> drawers, create a new function that fixes them as intelligently as
> possible (copying existing drawers into the correct place).

See above.

> 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?

Yes, it is. This subject was discussed on the ML already. Once fixed, it
is not much of an annoyance however.


Regards,

-- 
Nicolas Goaziou

  parent reply	other threads:[~2016-10-02  7:32 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
2016-10-02  7:32   ` Nicolas Goaziou [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877f9rw6j1.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.