From: Bastien <firstname.lastname@example.org>
To: Leonard Randall <email@example.com>
Subject: Re: Bug: Error with org-bibtex export with tags when using custom bibtypes [8.2.5h (8.2.5h-82-gd91d4b-elpaplus @ /Users/leonardaveryrandall/.emacs.d/elpa/org-plus-contrib-20140324/)]
Date: Sat, 19 Apr 2014 20:11:51 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <CAMRQoA=jeN_+GJ7aKgHzkAt4LZkT4tjwqABP9aYXBx8ENTtr1Q@mail.gmail.com> (Leonard Randall's message of "Sat, 19 Apr 2014 16:45:22 +0100")
Leonard Randall <email@example.com> writes:
> For some reason ignoring errors doesn't work for me. The new
> function, doesn't add a keywords field to non-standard bib entry
> types, it just puts the tags before the beginning of the bibtex
> entry, which would mess up the resulting bibtex file.
Can you provide a minimal example where I reproduce this bug,
along with your Emacs and Org versions? It works fine here.
> The regexp functions I used are based on standard bibtex syntax, so
> they should work in all circumstances. I tested my fix under various
> conditions and with various variables set and it worked everywhere I
> tried it.
I trust you on that, it's just that using re-search-forward here
does not seem necessary -- also, you could send an email to the
bibtex.el maintainers about the error being cryptic anyway, and
maybe not needed at all.
> If you are worried about licensing, you could wait to apply the
> patch until I receive and sign the license, but I think that it is a
> sufficiently small change that it should not be an issue.
I'd rather wait till the paperwork is done, it gives us more time
to sort this out properly.
next prev parent reply other threads:[~2014-04-19 18:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 21:03 Bug: Error with org-bibtex export with tags when using custom bibtypes [8.2.5h (8.2.5h-82-gd91d4b-elpaplus @ /Users/leonardaveryrandall/.emacs.d/elpa/org-plus-contrib-20140324/)] Leonard Randall
2014-04-19 13:51 ` Leonard Randall
2014-04-19 14:42 ` Bastien
2014-04-19 15:45 ` Leonard Randall
2014-04-19 18:11 ` Bastien [this message]
[not found] ` <CAMRQoAni6bs8DrTRN-_esu7ck49vYa=fwES7TBMLbhcuZ9ad6Q@mail.gmail.com>
[not found] ` <firstname.lastname@example.org>
2014-04-20 15:18 ` Leonard Randall
-- strict thread matches above, loose matches on Subject: below --
2014-03-25 15:47 Leonard Randall
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 public inbox
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).