From: Bastien <bzg@gnu.org>
To: Leonard Randall <leonard.a.randall@gmail.com>
Cc: emacs-orgmode@gnu.org
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: <87sip9nq8o.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CAMRQoA=jeN_+GJ7aKgHzkAt4LZkT4tjwqABP9aYXBx8ENTtr1Q@mail.gmail.com> (Leonard Randall's message of "Sat, 19 Apr 2014 16:45:22 +0100")
Hi Leonard,
Leonard Randall <leonard.a.randall@gmail.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.
Thanks again,
--
Bastien
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] ` <87lhv0qzom.fsf@bzg.ath.cx>
2014-04-20 15:18 ` Leonard Randall
-- strict thread matches above, loose matches on Subject: below --
2014-03-25 15:47 Leonard Randall
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=87sip9nq8o.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=leonard.a.randall@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 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).