ebib-users Mailing List for Ebib (Page 5)
Brought to you by:
joostkremers
You can subscribe to this list here.
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(14) |
Sep
(5) |
Oct
(9) |
Nov
(4) |
Dec
(2) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2007 |
Jan
|
Feb
(7) |
Mar
(18) |
Apr
(11) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
(12) |
Dec
|
2008 |
Jan
(2) |
Feb
(1) |
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
(5) |
Jul
|
Aug
|
Sep
(3) |
Oct
(7) |
Nov
(2) |
Dec
(7) |
2011 |
Jan
|
Feb
|
Mar
(11) |
Apr
|
May
|
Jun
|
Jul
(5) |
Aug
(1) |
Sep
(30) |
Oct
(2) |
Nov
(2) |
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(9) |
Jul
(1) |
Aug
(30) |
Sep
(10) |
Oct
(4) |
Nov
(1) |
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
(2) |
Feb
|
Mar
(8) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(3) |
Aug
|
Sep
(10) |
Oct
(5) |
Nov
|
Dec
|
2017 |
Jan
(2) |
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
(3) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: <ts...@ts...> - 2012-06-03 19:22:15
|
Aloha Joost, I ran into a problem with ebib having to do with entering an author whose surname begins with a special LaTeX character. The author's name is Mehmet \"{O}zdo\u{g}an, and my setup generates this key for the entry: \oxdogan06:_hypot_approac_realit. After I enter Mehmet's article, the key appears in the Ebib-index buffer, but the information isn't shown in the Ebib-entry buffer. In fact, the index is corrupted at \oxdogan06:_hypot_approach_realit. Each key from there on points to the following entry in the file, i.e., the third key points to the fourth entry, the fourth key to the fifth entry, etc. This problem seems to show up with this failed search: ebib-search-key-in-buffer: Search failed:"^\\oxdogan06:_hypot_approac_realit", which is the result of pressing E with the cursor in the Ebib-index buffer on the key \oxdogan06:_hypot_approac_realit. Let me know if you have any questions. All the best, Tom P.S. Thanks again for ebib. I rely on it heavily in my work now and find it a joy to use. -- T.S. Dye & Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com |
From: <ts...@ts...> - 2011-11-19 19:46:30
|
Aloha Joost, This might be a lot of work, but I wonder if it would be possible to make ebib aware of git? When I edit a bibliography in BibTeX mode, emacs knows that my bibliography is associated with a git repository and I can use magit to commit changes to the repository with a few keystrokes. I'm finding ebib so useful I rarely work in BibTeX mode, so I'm missing the handy functionality of magit. Of course, I'm looking for the best of both worlds! Thanks for ebib. What a handy tool. All the best, Tom -- T.S. Dye & Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com |
From: <ts...@ts...> - 2011-11-02 02:36:58
|
Joost Kremers <joo...@fa...> writes: > Hi Thomas, > >> When adding the cross reference field to an incollection entry, the >> title of the book ends up in the title field, rather than the booktitle >> field. I looked for a way to change this through the customize menu, >> but couldn't find it. Is there a way to have the book title cross >> referenced correctly? > > No, there isn't... The crossref mechanism is rather simplistic: it simply looks > for the contents of field of the same name as the x-reffing entry. The main > reason for that is that BibTeX does it that way. It doesn't read the title field > of the x-reffed entry when it needs to fill the booktitle field of the x-reffing > entry. > > Note, though, that it is possible to copy the contents of a x-reffed field. So > in a situation like this, you can simply go to the title field, hit 'c', go to > the booktitle field and hit 'y'. Thanks Joost, I hadn't thought to do it this way, which is quick and easy. All the best, Tom > > It shouldn't be difficult to have Ebib do this automatically, though. If I find > some time, I'll have a look at it. > > Best, > > Joost -- T.S. Dye & Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com |
From: Joost K. <joo...@fa...> - 2011-10-31 11:18:58
|
Hi Thomas, > When adding the cross reference field to an incollection entry, the > title of the book ends up in the title field, rather than the booktitle > field. I looked for a way to change this through the customize menu, > but couldn't find it. Is there a way to have the book title cross > referenced correctly? No, there isn't... The crossref mechanism is rather simplistic: it simply looks for the contents of field of the same name as the x-reffing entry. The main reason for that is that BibTeX does it that way. It doesn't read the title field of the x-reffed entry when it needs to fill the booktitle field of the x-reffing entry. Note, though, that it is possible to copy the contents of a x-reffed field. So in a situation like this, you can simply go to the title field, hit 'c', go to the booktitle field and hit 'y'. It shouldn't be difficult to have Ebib do this automatically, though. If I find some time, I'll have a look at it. Best, Joost -- Joost Kremers Life has its moments |
From: <ts...@ts...> - 2011-10-30 20:01:59
|
Hi Joost, When adding the cross reference field to an incollection entry, the title of the book ends up in the title field, rather than the booktitle field. I looked for a way to change this through the customize menu, but couldn't find it. Is there a way to have the book title cross referenced correctly? All the best, Tom -- T.S. Dye & Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com |
From: Joost K. <joo...@fa...> - 2011-09-21 21:43:25
|
On Wed, Sep 21, 2011 at 11:19:14PM +0200, Piter_ wrote: > Is there any trick to enable virtual database editing? The only way (for the moment) is to save the virtual database as a normal database, which you can do by selecting "Save database as..." from the Ebib menu (or by typing `M-x ebib-write-database'). That will save the virtual database as a .bib file. It is currently not possible to edit a virtual database directly, with the changes being made to the underlying real database. I am currently working on rewriting Ebib to separate the database code from the UI code, which should make it easier to add this functionality. I don't know when that will be ready, however... -- Joost Kremers Life has its moments |
From: Piter_ <x....@gm...> - 2011-09-21 21:19:22
|
Hi here. Is there any trick to enable virtual database editing? Thanks. Petro. |
From: Piter_ <x....@gm...> - 2011-09-21 21:07:18
|
Thanks :) On Mon, Aug 8, 2011 at 3:07 PM, Joost Kremers <joo...@fa...> wrote: > Hi Petr, > >> Cant figure out how to exit from multiline editing. C-x b tries to >> switch buffers :( > > The multiline edit buffer was changed to a minor mode, so that the key bindings > had to be changed as well. The relevant key bindings are now C-c | q (save and > quit), C-c | s (save) and C-c | c (cancel edit). I admit they're a bit > cumbersome, but because mulitline-edit-mode is a minor mode, there isn't much I > can do about it, since minor modes are only allowed to use key bindings that > start with C-c plus some non-alphabetic character. You can, however, redefine > the second character of the key sequences by putting something like the > following into your .emacs: > > (ebib-key multiline "&") > > This changes the key bindings to C-c & q, C-c & s and C-c & c, respectively. You > can also choose some letter, if you prefer that. > > All of this is described in the manual, by the way, although I should update the > version that appears on the website... > > > -- > Joost Kremers > Life has its moments > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > The must-attend event for mobile developers. Connect with experts. > Get tools for creating Super Apps. See the latest technologies. > Sessions, hands-on labs, demos & much more. Register early & save! > http://p.sf.net/sfu/rim-blackberry-1 > _______________________________________________ > Ebib-users mailing list > Ebi...@li... > https://lists.sourceforge.net/lists/listinfo/ebib-users > |
From: Joost K. <joo...@fa...> - 2011-09-20 16:06:29
|
Hi Tom, > This is a follow-up on the weird problem I reported earlier with the > mastersthesis type. See the attached message from the Org-mode > list. It looks like the problem was as you thought, an interaction with > other software, in this case org-bibtex. I can confirm that I have > org-bibtex loaded and that the file where the problem occurred had > org-bibtex entries. Aha! Thanks for forwarding that! In Ebib, the type of an entry is stored in a field named type* (note the asterisk) for exactly this reason. Glad you found out where the problem lies. Best, Joost -- Joost Kremers Life has its moments |
From: <ts...@ts...> - 2011-09-14 22:36:57
|
Joost Kremers <joo...@fa...> writes: > On Wed, Sep 14, 2011 at 10:49:03AM -1000, Thomas S. Dye wrote: >> > Glad I could help. I'm beginning to like this functionality myself too, BTW. I >> > just customized a bunch of bibtex-* variables so that bibtex-generate-autokey >> > generates keys according to the system I use and it's working quite nicely. >> >> Good to hear! Don't forget to announce to the list if you make >> automatic key generation an option :) > > I've just uploaded a commit to do just that. Well, not the announcement, just > the autogenerating of keys. There's a new user option 'Ebib Autogenerate Keys'. > If you set this, a new entry is automatically given a temporary key, which is > updated with an autogenerated key once you leave the entry buffer. > > Of course, 'K' also still works, in case you want to change or update the key > manually. > > Joost Hi Joost, What a pleasure! It is very nice to have 'K' still there for the times I make a mistake with author, title, or year. Now, I just edit away the mistake, bounce back to the index buffer, and hit 'K' for an up-to-date key. I'm not sure how I'd do that with other software I've been using. All the best, Tom -- T.S. Dye & Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com |
From: Joost K. <joo...@fa...> - 2011-09-14 21:20:05
|
On Wed, Sep 14, 2011 at 10:49:03AM -1000, Thomas S. Dye wrote: > > Glad I could help. I'm beginning to like this functionality myself too, BTW. I > > just customized a bunch of bibtex-* variables so that bibtex-generate-autokey > > generates keys according to the system I use and it's working quite nicely. > > Good to hear! Don't forget to announce to the list if you make > automatic key generation an option :) I've just uploaded a commit to do just that. Well, not the announcement, just the autogenerating of keys. There's a new user option 'Ebib Autogenerate Keys'. If you set this, a new entry is automatically given a temporary key, which is updated with an autogenerated key once you leave the entry buffer. Of course, 'K' also still works, in case you want to change or update the key manually. Joost -- Joost Kremers Life has its moments |
From: <ts...@ts...> - 2011-09-14 20:49:15
|
Joost Kremers <joo...@fa...> writes: > On Wed, Sep 14, 2011 at 09:18:16AM -1000, Thomas S. Dye wrote: >> Joost Kremers <joo...@fa...> writes: >> > I forgot to add a (require 'bibtex) to Ebib, which I've now fixed. If bibtex.el >> > isn't loaded, autogenerating keys won't work. However... >> >> Yes, this fixed the problem on emacs 23.1.95. I pulled the latest ebib, >> compiled ebib.elc, restarted emacs, opened my test bibliography, hit 'K' >> in the index and the key changed to one formatted as I expected. > > <whew> ;-) Glad it works. > >> Emacs 24 doesn't work for me, though. It still throws the stringp, nil >> error. I don't consider this much of a test, though. I don't compile >> emacs 24 here, but occasionally download a nightly build from a web site >> that offers emacs for OS X. I typically find that a few things I use >> regularly don't work, so I give up and go back to emacs 23. > > I guess that means it's also not a big deal for you if it doesn't work in Emacs > 24? Then I won't have to worry about it. ;-) Yep, I'm good with emacs 23. > >> Thanks very much for adding this functionality. I'm eager to explore >> the possibility of integrating ebib into the regular workflow of my >> colleagues. > > Glad I could help. I'm beginning to like this functionality myself too, BTW. I > just customized a bunch of bibtex-* variables so that bibtex-generate-autokey > generates keys according to the system I use and it's working quite nicely. Good to hear! Don't forget to announce to the list if you make automatic key generation an option :) Tom > > Best, > > Joost -- T.S. Dye & Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com |
From: Joost K. <joo...@fa...> - 2011-09-14 20:32:23
|
On Wed, Sep 14, 2011 at 09:18:16AM -1000, Thomas S. Dye wrote: > Joost Kremers <joo...@fa...> writes: > > I forgot to add a (require 'bibtex) to Ebib, which I've now fixed. If bibtex.el > > isn't loaded, autogenerating keys won't work. However... > > Yes, this fixed the problem on emacs 23.1.95. I pulled the latest ebib, > compiled ebib.elc, restarted emacs, opened my test bibliography, hit 'K' > in the index and the key changed to one formatted as I expected. <whew> ;-) Glad it works. > Emacs 24 doesn't work for me, though. It still throws the stringp, nil > error. I don't consider this much of a test, though. I don't compile > emacs 24 here, but occasionally download a nightly build from a web site > that offers emacs for OS X. I typically find that a few things I use > regularly don't work, so I give up and go back to emacs 23. I guess that means it's also not a big deal for you if it doesn't work in Emacs 24? Then I won't have to worry about it. ;-) > Thanks very much for adding this functionality. I'm eager to explore > the possibility of integrating ebib into the regular workflow of my > colleagues. Glad I could help. I'm beginning to like this functionality myself too, BTW. I just customized a bunch of bibtex-* variables so that bibtex-generate-autokey generates keys according to the system I use and it's working quite nicely. Best, Joost -- Joost Kremers Life has its moments |
From: <ts...@ts...> - 2011-09-14 19:45:13
|
Hi Joost, Joost Kremers <joo...@fa...> writes: > Hi Tom, > > I forgot to add a (require 'bibtex) to Ebib, which I've now fixed. If bibtex.el > isn't loaded, autogenerating keys won't work. However... Yes, this fixed the problem on emacs 23.1.95. I pulled the latest ebib, compiled ebib.elc, restarted emacs, opened my test bibliography, hit 'K' in the index and the key changed to one formatted as I expected. Emacs 24 doesn't work for me, though. It still throws the stringp, nil error. I don't consider this much of a test, though. I don't compile emacs 24 here, but occasionally download a nightly build from a web site that offers emacs for OS X. I typically find that a few things I use regularly don't work, so I give up and go back to emacs 23. Thanks very much for adding this functionality. I'm eager to explore the possibility of integrating ebib into the regular workflow of my colleagues. All the best, Tom > > On Wed, Sep 14, 2011 at 06:10:03AM -1000, Thomas S. Dye wrote: >> This doesn't work for me. I pulled from git, removed the old ebib.elc, >> started ebib, added a new entry, returned to the Ebib-index buffer with >> point at the temporary key, and hit 'K'. The key did not change. In >> Emacs 23 two white bars, one at the top and the other at the bottom, >> flashed briefly. In Emacs 24, which I don't use regularly, a white >> rectangle flashed briefly and a message appeared: Wrong type argument: >> stringp, nil. > > ... that is not the error one would expect. (It would say 'Symbol's function > definition is void: bibtex-generate-autokey'.) > > I'm using Emacs 23.2.1 and it works fine. (I haven't tested on Emacs 24, which I > don't have installed). > > Could you replace the definition of ebib-generate-autokey with the following: > > ==================== > > (defun ebib-generate-autokey () > "Automatically generate a key for the current entry. > This function uses the function BIBTEX-GENERATE-AUTOKEY to > generate the key, see that function's documentation for details." > (interactive) > (ebib-execute-when > ((real-db entries) > (let ((new-key > (with-temp-buffer > (ebib-format-entry (ebib-cur-entry-key) ebib-cur-db nil) > (goto-char (point-min)) > (bibtex-generate-autokey)))) > (message "New key: %s" new-key) > (if (member new-key (edb-keys-list ebib-cur-db)) > (error (format "Key `%s' already exists" new-key)) > (ebib-update-keyname new-key)))) > ((default) > (beep)))) > > ==================== > > (Just copy&paste into the *scratch* buffer, position the cursor after the last > parenthesis and do C-x C-e. That'll load the new function definition, there's no > need to edit ebib.el.) > > That should output the new key in the minibuffer when you hit 'K'. That should > at least make clear whether bibtex-generate-autokey has done its work... > > Joost -- T.S. Dye & Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com |
From: Joost K. <joo...@fa...> - 2011-09-14 18:19:27
|
Hi Tom, I forgot to add a (require 'bibtex) to Ebib, which I've now fixed. If bibtex.el isn't loaded, autogenerating keys won't work. However... On Wed, Sep 14, 2011 at 06:10:03AM -1000, Thomas S. Dye wrote: > This doesn't work for me. I pulled from git, removed the old ebib.elc, > started ebib, added a new entry, returned to the Ebib-index buffer with > point at the temporary key, and hit 'K'. The key did not change. In > Emacs 23 two white bars, one at the top and the other at the bottom, > flashed briefly. In Emacs 24, which I don't use regularly, a white > rectangle flashed briefly and a message appeared: Wrong type argument: > stringp, nil. ... that is not the error one would expect. (It would say 'Symbol's function definition is void: bibtex-generate-autokey'.) I'm using Emacs 23.2.1 and it works fine. (I haven't tested on Emacs 24, which I don't have installed). Could you replace the definition of ebib-generate-autokey with the following: ==================== (defun ebib-generate-autokey () "Automatically generate a key for the current entry. This function uses the function BIBTEX-GENERATE-AUTOKEY to generate the key, see that function's documentation for details." (interactive) (ebib-execute-when ((real-db entries) (let ((new-key (with-temp-buffer (ebib-format-entry (ebib-cur-entry-key) ebib-cur-db nil) (goto-char (point-min)) (bibtex-generate-autokey)))) (message "New key: %s" new-key) (if (member new-key (edb-keys-list ebib-cur-db)) (error (format "Key `%s' already exists" new-key)) (ebib-update-keyname new-key)))) ((default) (beep)))) ==================== (Just copy&paste into the *scratch* buffer, position the cursor after the last parenthesis and do C-x C-e. That'll load the new function definition, there's no need to edit ebib.el.) That should output the new key in the minibuffer when you hit 'K'. That should at least make clear whether bibtex-generate-autokey has done its work... Joost -- Joost Kremers Life has its moments |
From: <ts...@ts...> - 2011-09-14 16:37:01
|
Hi Joost, Joost Kremers <joo...@fa...> writes: > Hi Tom, > > On Tue, Sep 13, 2011 at 09:41:39AM -1000, Thomas S. Dye wrote: >> I'm finding ebib very useful for projects that are designed to be >> distributed outside of my circle of colleagues as reproducible >> research. These projects require a bib file that includes just the >> references cited by the project. ebib makes it very easy to accomplish >> this. Still, I want to contribute to our master bibliography file and >> comply with our agreement to use autogenerated keys. > > I've added a function to Ebib that will automatically generate a (new) key for > the current entry, using bibtex-generate-autokey. This means that all the > customisation options for that function are available and you should be able to > autogenerate keys that match the keys generated by your colleagues. > > What I haven't done (yet) is to allow a workflow where the keys are generated > for you. Instead, you have to first provide a temporary key and fill in the > field values. When you're done, return to the index buffer and hit 'K' (capital > K, that is). That will then replace the temp key with an autogenerated key. This doesn't work for me. I pulled from git, removed the old ebib.elc, started ebib, added a new entry, returned to the Ebib-index buffer with point at the temporary key, and hit 'K'. The key did not change. In Emacs 23 two white bars, one at the top and the other at the bottom, flashed briefly. In Emacs 24, which I don't use regularly, a white rectangle flashed briefly and a message appeared: Wrong type argument: stringp, nil. > > If I have some more time, I will add an option to have Ebib create a temp key > and automatically replace it with an autogenerated key when leaving the entry > buffer (or something to that effect: let me know if you have any wishes/ideas on > that). That way you can simply enter field values without having enter a key > name at all. > That sounds great. The 'K' option would work nicely for me, though. Tom > Hope this works for you. Do let me know if you find any bugs! > > Joost -- T.S. Dye & Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com |
From: Joost K. <joo...@fa...> - 2011-09-14 10:03:04
|
Hi Tom, On Tue, Sep 13, 2011 at 09:41:39AM -1000, Thomas S. Dye wrote: > I'm finding ebib very useful for projects that are designed to be > distributed outside of my circle of colleagues as reproducible > research. These projects require a bib file that includes just the > references cited by the project. ebib makes it very easy to accomplish > this. Still, I want to contribute to our master bibliography file and > comply with our agreement to use autogenerated keys. I've added a function to Ebib that will automatically generate a (new) key for the current entry, using bibtex-generate-autokey. This means that all the customisation options for that function are available and you should be able to autogenerate keys that match the keys generated by your colleagues. What I haven't done (yet) is to allow a workflow where the keys are generated for you. Instead, you have to first provide a temporary key and fill in the field values. When you're done, return to the index buffer and hit 'K' (capital K, that is). That will then replace the temp key with an autogenerated key. If I have some more time, I will add an option to have Ebib create a temp key and automatically replace it with an autogenerated key when leaving the entry buffer (or something to that effect: let me know if you have any wishes/ideas on that). That way you can simply enter field values without having enter a key name at all. Hope this works for you. Do let me know if you find any bugs! Joost -- Joost Kremers Life has its moments |
From: <ts...@ts...> - 2011-09-13 19:41:54
|
Joost Kremers <joo...@fa...> writes: > On Mon, Sep 12, 2011 at 06:19:41AM -1000, Thomas S. Dye wrote: >> Joost Kremers <joo...@fa...> writes: >> Eric Schulte added this functionality to org-bibtex a while back. I >> think this might be the appropriate part of org-bibtex.el: >> >> (require 'bibtex) >> (eval-when-compile >> (require 'cl)) >> >> (defvar description nil) ; dynamically scoped from org.el >> (defvar org-id-locations) >> >> (declare-function bibtex-beginning-of-entry "bibtex" ()) >> (declare-function bibtex-generate-autokey "bibtex" ()) > > Hmmm... I see, thanks. So how is your colleague's workflow exactly, if I may > ask? bibtex-generate-autokey reads a bibtex entry from a buffer and then > generates a key. But that seems to imply that there is already a properly > formatted bibtex entry, that is, one with a key. Do you provide temporary keys, > which are then replaced as the fields are filled? > > That wouldn't be difficult to duplicate in Ebib, I think. Instead of having to > type a key, Ebib would provide a temporary key, which is then replaced with an > autogenerated key when the fields are filled in. Hi Joost, At the moment, I'm the only one using ebib and org-mode. My colleagues all work in emacs with the standard LaTeX helper modes--AucTeX, reftex, bibtex. We share a master bibliography file that is updated and distributed periodically. A typical project uses the master bibliography file and a separate local bibliography file, which is merged with the master file at the end of the project, after the editor has had a chance to make sure it is clean. We rely on key autogeneration to reduce the number of duplicate entries in the master file. Before we agreed to use autogenerated keys we found the master file often contained several versions of the same reference, each with a different key, and often with some slight differences in content. I'm finding ebib very useful for projects that are designed to be distributed outside of my circle of colleagues as reproducible research. These projects require a bib file that includes just the references cited by the project. ebib makes it very easy to accomplish this. Still, I want to contribute to our master bibliography file and comply with our agreement to use autogenerated keys. As for the mechanics of how Eric S. accomplished this in org-bibtex, I need to refer you to the org-bibtex.el source, which I presume has the answer. From the org-bibtex user's perspective, fields are filled out in response to queries and when this is done the bibtex information is placed in an Org-mode property drawer with the autogenerated key. All the best, Tom -- T.S. Dye & Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com |
From: Joost K. <joo...@fa...> - 2011-09-13 12:57:34
|
On Mon, Sep 12, 2011 at 06:19:41AM -1000, Thomas S. Dye wrote: > Joost Kremers <joo...@fa...> writes: > Eric Schulte added this functionality to org-bibtex a while back. I > think this might be the appropriate part of org-bibtex.el: > > (require 'bibtex) > (eval-when-compile > (require 'cl)) > > (defvar description nil) ; dynamically scoped from org.el > (defvar org-id-locations) > > (declare-function bibtex-beginning-of-entry "bibtex" ()) > (declare-function bibtex-generate-autokey "bibtex" ()) Hmmm... I see, thanks. So how is your colleague's workflow exactly, if I may ask? bibtex-generate-autokey reads a bibtex entry from a buffer and then generates a key. But that seems to imply that there is already a properly formatted bibtex entry, that is, one with a key. Do you provide temporary keys, which are then replaced as the fields are filled? That wouldn't be difficult to duplicate in Ebib, I think. Instead of having to type a key, Ebib would provide a temporary key, which is then replaced with an autogenerated key when the fields are filled in. -- Joost Kremers Life has its moments |
From: <ts...@ts...> - 2011-09-12 16:19:59
|
Joost Kremers <joo...@fa...> writes: > Hi Tom, > > On Fri, Sep 09, 2011 at 06:34:32AM -1000, Thomas S. Dye wrote: >> It would be great to have an automatically generated key. I work in an >> environment where several of us contribute to a master bibliography >> file. We've come to rely on the keys that AucTeX (I believe) supplies. > > Do you happen to know how this works exactly? I took a (quick) look through the > AUCTeX and RefTeX docs, but didn't find anything useful. Eric Schulte added this functionality to org-bibtex a while back. I think this might be the appropriate part of org-bibtex.el: (require 'bibtex) (eval-when-compile (require 'cl)) (defvar description nil) ; dynamically scoped from org.el (defvar org-id-locations) (declare-function bibtex-beginning-of-entry "bibtex" ()) (declare-function bibtex-generate-autokey "bibtex" ()) hth, Tom -- T.S. Dye & Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com |
From: Joost K. <joo...@fa...> - 2011-09-12 15:42:23
|
Hi Tom, On Fri, Sep 09, 2011 at 06:34:32AM -1000, Thomas S. Dye wrote: > It would be great to have an automatically generated key. I work in an > environment where several of us contribute to a master bibliography > file. We've come to rely on the keys that AucTeX (I believe) supplies. Do you happen to know how this works exactly? I took a (quick) look through the AUCTeX and RefTeX docs, but didn't find anything useful. -- Joost Kremers Life has its moments |
From: <ts...@ts...> - 2011-09-09 17:01:26
|
Joost Kremers <joo...@fa...> writes: > Hi Tom, > > On Wed, Sep 07, 2011 at 05:54:07AM -1000, Thomas S. Dye wrote: >> Joost Kremers <joo...@fa...> writes: >> > $ emacs -Q -l /path/to/ebib.el >> > >> > then start Ebib with 'M-x ebib'. >> >> This works as you describe it. There is no extraneous 'type' field >> added during the save operation. > [...] >> There is no type field there. >> >> So, it must be a customization (sigh). I'll keep my eye on this and let >> you know if I track down the culprit. > > If there's anything I can do to help, then just let me know. It's a really > strange phenomenon, it could be that Ebib is interfering with something else. > >> In the meantime, thanks for looking into the mystery. I'm getting >> addicted to ebib. With a little practice, it is an easy and efficient >> way to manage bibliographies. > > Thanks. :-) If you find anything that could be improved, or something that might > be added to make it better, just let me know. > Hi Joost, Since you asked ... It would be great to have an automatically generated key. I work in an environment where several of us contribute to a master bibliography file. We've come to rely on the keys that AucTeX (I believe) supplies. We use them to weed out duplicate entries. This isn't a big deal and I recognize that it goes against the ebib work flow, which asks for the key before the citation information. Thanks again for ebib. Tom > Thanks, > > Joost -- T.S. Dye & Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com |
From: Joost K. <joo...@fa...> - 2011-09-09 10:09:28
|
Hi Tom, On Wed, Sep 07, 2011 at 05:54:07AM -1000, Thomas S. Dye wrote: > Joost Kremers <joo...@fa...> writes: > > $ emacs -Q -l /path/to/ebib.el > > > > then start Ebib with 'M-x ebib'. > > This works as you describe it. There is no extraneous 'type' field > added during the save operation. [...] > There is no type field there. > > So, it must be a customization (sigh). I'll keep my eye on this and let > you know if I track down the culprit. If there's anything I can do to help, then just let me know. It's a really strange phenomenon, it could be that Ebib is interfering with something else. > In the meantime, thanks for looking into the mystery. I'm getting > addicted to ebib. With a little practice, it is an easy and efficient > way to manage bibliographies. Thanks. :-) If you find anything that could be improved, or something that might be added to make it better, just let me know. Thanks, Joost -- Joost Kremers Life has its moments |
From: <ts...@ts...> - 2011-09-07 16:21:11
|
Hi Joost, Joost Kremers <joo...@fa...> writes: > Hi Tom, > > On Tue, Sep 06, 2011 at 05:11:26AM -1000, Thomas S. Dye wrote: >> Joost Kremers <joo...@fa...> writes: >> > Could you send me a copy of the relevant .bib file and also a list of the Ebib >> > customisations you made? TBH, I haven't got a clue what might be going on, but >> > I'll try and figure it out. :-) >> >> Here are the ebib entries in custom.el: >> >> '(ebib-file-associations (quote (("pdf" . "/Applications/Skim.app/Contents/MacOS/Skim") ("ps" . "/Applications/Preview.app/Contents/MacOS/Preview")))) >> '(ebib-file-search-dirs (quote ("~/Desktop/reprints/"))) >> '(ebib-insertion-commands (quote (("cite" 1 nil) ("citep" 1 nil) ("citet" 1 nil)))) >> '(ebib-preload-bib-files (quote ("/Users/dk/Public/projects/bibliography/bib/bib/tsd.bib"))) > > These shouldn't have any effect on how the .bib file is saved, so... > >> I've attached the .bib file after a save with ebib (so the 'type' field >> is added to @mastersthesis). > > Thanks. However, there doesn't seem to be anything in the .bib file that causes > your problem. If I load it, change something, save it, then manually remove the > 'type = {masterstesis}' fields from the bib file and reload it, change something > else, then save it, the type fields are not there. > > Ebib stores each entry in a hash table, where each field name is a key. There is > a special key 'type*' (note the asterisk) that stores the entry type (article, > book, mastersthesis, etc.) This type* key is not saved as a field into the bib > file, but (obviously) as the entry type (@book, @article, etc.) But if for some > reason the key 'type*' in the hash table is replaced with a key 'type', then > Ebib will save it as a normal field. > > The one thing I cannot figure out, though, is how this key 'type' is created. > And why it only happens with the mastersthesis entries. That to me just doesn't > make any sense. > > Does this happen with a completely fresh Emacs session as well? What if you > start Emacs with: > > $ emacs -Q -l /path/to/ebib.el > > then start Ebib with 'M-x ebib'. This works as you describe it. There is no extraneous 'type' field added during the save operation. > > What happens if you start Emacs and Ebib this way, then load the relevant .bib > file (with the 'type = {mastersthesis}' lines removed), lower Ebib again, then > type 'M-x ielm' (to get an interactive Elisp prompt) and at the prompt type > (copy/paste) the following: > > (gethash "wilson76:_o_posses_marker_hawaiian" (edb-database ebib-cur-db)) > > That should show some info about the hash table that stores the relevant entry, > together with a list of all the fields. There shouldn't be a type field there. > If there is, there's definitely something weird going on. There is no type field there. So, it must be a customization (sigh). I'll keep my eye on this and let you know if I track down the culprit. In the meantime, thanks for looking into the mystery. I'm getting addicted to ebib. With a little practice, it is an easy and efficient way to manage bibliographies. All the best, Tom -- T.S. Dye & Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com |
From: Joost K. <joo...@fa...> - 2011-09-07 12:20:01
|
Hi Tom, On Tue, Sep 06, 2011 at 05:11:26AM -1000, Thomas S. Dye wrote: > Joost Kremers <joo...@fa...> writes: > > Could you send me a copy of the relevant .bib file and also a list of the Ebib > > customisations you made? TBH, I haven't got a clue what might be going on, but > > I'll try and figure it out. :-) > > Here are the ebib entries in custom.el: > > '(ebib-file-associations (quote (("pdf" . "/Applications/Skim.app/Contents/MacOS/Skim") ("ps" . "/Applications/Preview.app/Contents/MacOS/Preview")))) > '(ebib-file-search-dirs (quote ("~/Desktop/reprints/"))) > '(ebib-insertion-commands (quote (("cite" 1 nil) ("citep" 1 nil) ("citet" 1 nil)))) > '(ebib-preload-bib-files (quote ("/Users/dk/Public/projects/bibliography/bib/bib/tsd.bib"))) These shouldn't have any effect on how the .bib file is saved, so... > I've attached the .bib file after a save with ebib (so the 'type' field > is added to @mastersthesis). Thanks. However, there doesn't seem to be anything in the .bib file that causes your problem. If I load it, change something, save it, then manually remove the 'type = {masterstesis}' fields from the bib file and reload it, change something else, then save it, the type fields are not there. Ebib stores each entry in a hash table, where each field name is a key. There is a special key 'type*' (note the asterisk) that stores the entry type (article, book, mastersthesis, etc.) This type* key is not saved as a field into the bib file, but (obviously) as the entry type (@book, @article, etc.) But if for some reason the key 'type*' in the hash table is replaced with a key 'type', then Ebib will save it as a normal field. The one thing I cannot figure out, though, is how this key 'type' is created. And why it only happens with the mastersthesis entries. That to me just doesn't make any sense. Does this happen with a completely fresh Emacs session as well? What if you start Emacs with: $ emacs -Q -l /path/to/ebib.el then start Ebib with 'M-x ebib'. What happens if you start Emacs and Ebib this way, then load the relevant .bib file (with the 'type = {mastersthesis}' lines removed), lower Ebib again, then type 'M-x ielm' (to get an interactive Elisp prompt) and at the prompt type (copy/paste) the following: (gethash "wilson76:_o_posses_marker_hawaiian" (edb-database ebib-cur-db)) That should show some info about the hash table that stores the relevant entry, together with a list of all the fields. There shouldn't be a type field there. If there is, there's definitely something weird going on. -- Joost Kremers Life has its moments |