From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leonard Randall 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 16:45:22 +0100 Message-ID: References: <87zjjhnzyf.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c20e2a72b1fe04f7672723 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33696) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WbXSG-00073T-GL for emacs-orgmode@gnu.org; Sat, 19 Apr 2014 11:45:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WbXSF-0006ED-Gu for emacs-orgmode@gnu.org; Sat, 19 Apr 2014 11:45:24 -0400 Received: from mail-ob0-x22b.google.com ([2607:f8b0:4003:c01::22b]:38192) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WbXSF-0006E9-Bs for emacs-orgmode@gnu.org; Sat, 19 Apr 2014 11:45:23 -0400 Received: by mail-ob0-f171.google.com with SMTP id uy5so2852889obc.30 for ; Sat, 19 Apr 2014 08:45:22 -0700 (PDT) In-Reply-To: <87zjjhnzyf.fsf@bzg.ath.cx> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: Bastien Cc: emacs-orgmode@gnu.org --001a11c20e2a72b1fe04f7672723 Content-Type: text/plain; charset=UTF-8 Hi Bastien, Bastien wrote: > I fixed this by ignoring the error, since the field is inserted > anyway. 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. 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. 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. All best, Leonard --001a11c20e2a72b1fe04f7672723 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Bastien,


> I fixed this b= y ignoring the error, since the field is inserted
> anyway.

For some reason ignoring errors doesn&#= 39;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 th= e bibtex entry, which would mess up the resulting bibtex file.=C2=A0

The regexp functions I used are based on standard bibte= x syntax, so they should work in all circumstances. I tested my fix under v= arious conditions and with various variables set and it worked everywhere I= tried it.=C2=A0

If you are worried about licensing, you could wait =C2= =A0to apply the patch until I receive and sign the license, but I think tha= t it is a sufficiently small change that it should not be an issue.=C2=A0

All best,

Leonard



--001a11c20e2a72b1fe04f7672723--