emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Alan Tyree <alantyree@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: "Bruce D'Arcus" <bdarcus@gmail.com>,
	emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: How to debug a CSL problem
Date: Mon, 6 Jun 2022 11:44:12 +1000	[thread overview]
Message-ID: <CAGMsgMz=MP-uJ-Z_yAFuby2pfppuAZk2Zeti6uG70AHD67JyUQ@mail.gmail.com> (raw)
In-Reply-To: <87r1424n7v.fsf@localhost>

[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]

Thanks, Ihor. That found it.

The bibtex entry had:
author = {BIS},

Change to:
author = {{Bank for International Settlements}},

and it all works a treat.

A short random test shows that the export chokes when there is a single
name for an author. Again an example:
author = {{Wolfsberg Group}} works fine;
author = {{Wolfsberg}} chokes.

Thanks to you and to Bruce for the help.

Cheers,
Alan




On Mon, 6 Jun 2022 at 11:03, Ihor Radchenko <yantar92@gmail.com> wrote:

> Alan Tyree <alantyree@gmail.com> writes:
>
> > I guess the bad news is that the csl file validates. I also should have
> > mentioned that everything parses properly with pandoc, so I guess it is a
> > cireproc-el glitch.
> >
> > From the brief error report, it must just be choking  on a specific
> bibtex
> > entry, so it would still be helpful to be able to find it.
>
> Run M-x toggle-debug-on-error and then try to trigger the error. Then,
> you will be able to see the whole backtrace and potentially find out the
> problematic BiBTeX entry. If backtrace does not help, you may need to
> use M-x debug-on-entry and use debugger (See 19.1 The Lisp Debugger in
> Elisp manual).
>
> Best,
> Ihor
>


-- 
Alan L Tyree                    http://www2.austlii.edu.au/~alan

[-- Attachment #2: Type: text/html, Size: 2141 bytes --]

next prev parent reply	other threads:[~2022-06-06  1:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-05 22:47 How to debug a CSL problem Alan Tyree
2022-06-05 23:15 ` Bruce D'Arcus
2022-06-06  0:24   ` Alan Tyree
2022-06-06  1:03     ` Ihor Radchenko
2022-06-06  1:44       ` Alan Tyree [this message]
2022-06-06  5:34         ` András Simonyi
2022-06-06  5:56           ` Alan Tyree

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='CAGMsgMz=MP-uJ-Z_yAFuby2pfppuAZk2Zeti6uG70AHD67JyUQ@mail.gmail.com' \
    --to=alantyree@gmail.com \
    --cc=bdarcus@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@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

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).