all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jorge <jorge13515@gmail.com>
To: Josiah Schwab <jschwab@gmail.com>
Cc: Jorge Morais <jorge13515@gmail.com>, Emacs-orgmode@gnu.org
Subject: Re: Bug report: org-get-property-block returns nil if the entry does not start with the property drawer
Date: Tue, 25 Aug 2015 20:59:09 -0300	[thread overview]
Message-ID: <CAJR3QnecWS19OKv_ya3Ej1TpCT-W+=91vd6dxc8jVxdQ6W5Jmg@mail.gmail.com> (raw)
In-Reply-To: <877fojqa8c.fsf@gmail.com>

On Tue, Aug 25, 2015 at 7:22 PM, Josiah Schwab <jschwab@gmail.com> wrote:
> This is the first item in the 8.3 series changelog.  There is a provided
> script to repair things.

Now I see that this new requirement is documented in Info manual
subsection 7.1 Property syntax.  I had only checked subsection 2.8
Drawers.

I didn't see the changelog because I updated through Emacs' package
menu, and I intended to update frequently (including between formal
releases), so I wouldn't check the changelog.  I now realize that
skipping the changelog is barely acceptable when you just want to use
the software, but is unacceptable when you want to report regressions.

Still, Org itself should interactively mention this change (pointing
either to manual subsection 7.1 or to orgmode.org/Changes.html)
instead of just cryptically saying "malformed drawer found".  This
slight increase in verbosity would help users like me and I don't see
any significant downside.

And please forgive any English mistake, I am Brazilian.

      reply	other threads:[~2015-08-25 23:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25 17:42 Bug report: org-get-property-block returns nil if the entry does not start with the property drawer Jorge Morais
2015-08-25 22:22 ` Josiah Schwab
2015-08-25 23:59   ` Jorge [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

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

  git send-email \
    --in-reply-to='CAJR3QnecWS19OKv_ya3Ej1TpCT-W+=91vd6dxc8jVxdQ6W5Jmg@mail.gmail.com' \
    --to=jorge13515@gmail.com \
    --cc=Emacs-orgmode@gnu.org \
    --cc=jschwab@gmail.com \
    /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.