From: Titus von der Malsburg <malsburg@posteo.de>
To: Julian Burgos <julian@hafro.is>
Cc: John Kitchin <johnrkitchin@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: org-ref & helm-bibtex notes
Date: Wed, 17 Jun 2015 17:08:08 -0700 [thread overview]
Message-ID: <87egl9najb.fsf@posteo.de> (raw)
In-Reply-To: <87mvzzm8c8.fsf@posteo.de>
[-- Attachment #1: Type: text/plain, Size: 3382 bytes --]
On 2015-06-16 Tue 18:28, Titus von der Malsburg wrote:
> On 2015-06-16 Tue 17:39, Julian Burgos wrote:
>> Dear list,
>>
>> I have been using org-ref for a while, using reftex to insert citations in
>> my org documents. Now I am switching to helm-bibtex, which is pretty
>> awesome. I have a couple of question about the note files. Org-ref uses
>> a single file to keep notes (e.g. notes.org), but helm-bibtex assumes that
>> notes are kept in separate files, one per article. My questions are:
>>
>> a) Do you have a preference in the single file vs multiple files question?
>> Are advantages/disadvantages? I tend to prefer the single file option,
>> it makes search easy and also I can add TODO items that later I can pull
>> out in the agenda view. With multiple files this would not be as easy.
>> Do you agree?
>
> Hi, I’m the author of helm-bibtex. There was recently a discussion about
> this on Github:
>
> https://github.com/tmalsburg/helm-bibtex/issues/40
>
> Someone convinced me that storing all notes in one file is better and
> there is an experimental (and incomplete) implementation in a topic
> branch:
>
> https://github.com/tmalsburg/helm-bibtex/tree/note-files
Update: I worked on the note-files branch and as far as I’m concerned it
is ready to be merged into master. There are several changes:
When one big notes file is used:
- The new default template for notes is simpler than what org-ref uses
but it should be compatible because it uses the Custom_ID property to
store the key.
- Note templates can be defined in `helm-bibtex-notes-template`.
- The list of publications now shows a mark if notes are available for a
publication.
- Finding the correct entry is now robust because the code looks for
`Custom_ID: key` not just for the key.
Multiple note files (one for each publication):
- The template for notes is used to populate new note
files. (Previously it was only used in the case with one big notes
file.)
Julian, if you could test this branch, that would be fantastic!
Here is the code:
https://github.com/tmalsburg/helm-bibtex/tree/note-files
Titus
>
> (Multiple note files will still be possible for users who prefer that.)
>
>> b) Helm-bibtex identifies which references have a note file, adding a
>> symbol on the reference list. Can we make helm-bibtex look into a single
>> file (say the "notes.org" file), look for the :Custom_ID: properties of
>> the entries, and use that to mark the reference list? I am teaching
>> myself emacs-lisp but this is above my capacity right now.
>
> Yes, something like that needs to be included. The unresolved question
> is how BibTeX keys should be stored in the notes file. I find property
> drawers incredibly clunky and in my experience they can considerably
> slow down Emacs in large org files (that’s the reason why I don’t use
> org-contacts as much as a would like).
>
> My current favorite format for entries in the notes file is the
> following:
>
> * Author: Title (year) :BibTeXkey:
> Here are the notes …
>
> The only problem I see with this is that BibTeX allows keys to contain
> colons, and a key with a colon would break org’s tag syntax.
>
> Suggestions welcome.
>
> Titus
>
>
>>
>> Many thanks,
>>
>> Julian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
prev parent reply other threads:[~2015-06-18 0:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 0:39 org-ref & helm-bibtex notes Julian Burgos
2015-06-17 1:21 ` Tory S. Anderson
2015-06-17 1:25 ` John Kitchin
2015-06-17 11:48 ` Julian Burgos
2015-06-17 1:28 ` Titus von der Malsburg
2015-06-17 12:25 ` Julian Burgos
2015-06-18 0:08 ` Titus von der Malsburg [this message]
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=87egl9najb.fsf@posteo.de \
--to=malsburg@posteo.de \
--cc=emacs-orgmode@gnu.org \
--cc=johnrkitchin@gmail.com \
--cc=julian@hafro.is \
/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).