all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55342@debbugs.gnu.org, Kaushal Modi <kaushal.modi@gmail.com>
Subject: bug#55342: 29.0.50; org-cite-basic--get-field: Wrong value for ENTRY-OR-KEY: nil
Date: Tue, 10 May 2022 12:52:52 +0800	[thread overview]
Message-ID: <871qx2kmzf.fsf__32751.5489816264$1652158651$gmane$org@localhost> (raw)
In-Reply-To: <83czgmt93n.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Kaushal Modi <kaushal.modi@gmail.com>
>> Date: Mon, 9 May 2022 17:41:32 -0400
>> 
>> Exporting an Org file with citations on Emacs 29 now throws the error
>> "Wrong value for ENTRY-OR-KEY: nil". This error can be reproduced with
>> the Org version shipped with Emacs on the master branch.
>
> Shouldn't this be reported to Org developers first?

It has been.
However, part of the problem lies in the bibtex-map-entries:

          ;; If we have invalid entries, ensure that we have forward
          ;; progress so that we don't infloop.
          (if (= (point) prev)
              (forward-line 1)

The code above always skips a bibtex entry starting at bob.
Hence, the provided example bibliography is parsed as empty, which is
not expected by Org.

While handling empty bibfiles should be fixed on Org side, the current
behaviour of bibtex-map-entries should indeed be fixed on Emacs side.

Best,
Ihor





  reply	other threads:[~2022-05-10  4:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09 21:41 bug#55342: 29.0.50; org-cite-basic--get-field: Wrong value for ENTRY-OR-KEY: nil Kaushal Modi
2022-05-10  2:27 ` Eli Zaretskii
2022-05-10  4:52   ` Ihor Radchenko [this message]
2022-05-10  4:52   ` Ihor Radchenko
2022-05-10  5:06     ` Lars Ingebrigtsen
2022-05-10 15:08       ` Kaushal Modi
2022-05-10 15:08       ` Kaushal Modi
2022-05-10 12:08     ` Eli Zaretskii
2022-05-10 12:08     ` Eli Zaretskii

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='871qx2kmzf.fsf__32751.5489816264$1652158651$gmane$org@localhost' \
    --to=yantar92@gmail.com \
    --cc=55342@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=kaushal.modi@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.