From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Richard <theonewiththeevillook@yahoo.fr>
Subject: Bug: (bisected) org-meta-return makes an error at end of a buffer
 [8.0.3 (release_8.0.3-239-g269c5f @ /home/youngfrog/sources/org-mode/lisp/)]
Date: Tue, 25 Jun 2013 12:08:51 +0200
Message-ID: <87r4fq8pu4.fsf@yahoo.fr>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:44319)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <theonewiththeevillook@yahoo.fr>) id 1UrQB9-0004V1-L9
	for emacs-orgmode@gnu.org; Tue, 25 Jun 2013 06:08:52 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <theonewiththeevillook@yahoo.fr>) id 1UrQB8-0002Jc-3V
	for emacs-orgmode@gnu.org; Tue, 25 Jun 2013 06:08:51 -0400
Received: from mxin.ulb.ac.be ([164.15.128.112]:7227)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <theonewiththeevillook@yahoo.fr>) id 1UrQB7-0002JQ-U9
	for emacs-orgmode@gnu.org; Tue, 25 Jun 2013 06:08:50 -0400
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: emacs-orgmode@gnu.org

Hello,

Evalling
(progn
  (switch-to-buffer "org-test.org")
  (org-mode)
  (insert "* good day\n") ; no "\n" implies no error.
  (setq debug-on-error t)
  (org-meta-return))
makes an error

git bisect says: 
,----
| 3c933adaf627bc8a58cfefb62ff0f2d5df640673 is the first bad commit
`----

That commit simply introduced (org-element-at-point) into
(org-at-property-p), so I also ran a git bisect session with
(org-element-at-point) instead of (org-meta-return) in the above because
I guess org-element-at-point shouldn't actually make an error. Here is
the result:

,----
| 94bcc7e2828a42d5448757ab28cadbf663c9ff6d is the first bad commit
| commit 94bcc7e2828a42d5448757ab28cadbf663c9ff6d
| Author: Nicolas Goaziou <n.goaziou@gmail.com>
| Date:   Mon Feb 11 14:42:16 2013 +0100
| 
|     org-element: Fix parsing of orphaned keyword at the end of an element
|     
|     * lisp/org-element.el (org-element--current-element): Add a limit
|       argument.
|     (org-element--collect-affiliated-keywords): Fix parsing of orphaned
|     keyword at the end of an element.
|     * testing/lisp/test-org-element.el: Add test.
| 
| :040000 040000 180072bc91d21e7c3c893792e9a162268068477e e0e8d22d8a06f0601a585010be45d40dbb91b866 M	lisp
| :040000 040000 ce3fa869b4f17ed3b3edce74f38cfdce8e70d4f4 58c55594d5f851eb8a8a19eaf12b3a6bd6884cfe M	testing
| bisect run success
`----

I don't know what the solution is because I don't understand the link
between affiliated keywords and the fact that (>= (point) limit) (this
is the clause which is entered in the cond in
org-element--current-element)

-- 
Nico.