From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Daniele Nicolodi <daniele@grinta.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-ref: xxx-add-bibtex-entry with an org-capture like interface
Date: Tue, 14 Apr 2020 20:19:30 -0400 [thread overview]
Message-ID: <m2k12h7g8e.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <934ea660-2aad-f450-f7a7-1ccd0195d3f0@grinta.net>
That function inserts into a bibtex file, and if you don't save it then
the new entry is not "findable", so it is somewhat critical to do that
in my mind. It could make sense to check if there is a file attached to
the buffer though, and only save in that case. That would preserve the
current behavior, and solve your problem I think. WDYT?
Daniele Nicolodi <daniele@grinta.net> writes:
> On 09-04-2020 13:43, John Kitchin wrote:
>> This is basically what doi-add-bibtex-entry does. There isn't one
>> function that does arxiv too, but there is arxiv-add-bibtex-entry. Those
>> are both commands in org-ref. These don't pop up a buffer for approval,
>> that is something you would have to build yourself.
>>
>> There are many workflows people want, the one above works for me when I
>> am writing, and just want to add entries with minimal disruption. I
>> usually polish the entries later if needed. I can see a slower, approach
>> like you describe too.
>
> Hello John,
>
> I have been able to hack something combining org-capture and the utility
> functions you mention that implements the workflow I described.
>
> There is only one issue: doi-utils-insert-bibtex-entry-from-doi contains
> a (save-buffer) call that does not play nicely when I call it on a
> temporary buffer. Why is the (save-buffer) there?
> doi-utils-insert-bibtex-entry-from-doi looks like an utility function,
> thus I think it should not try to save the current buffer. What do you
> think?
>
> Thank you.
>
> Cheers,
> Dan
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
prev parent reply other threads:[~2020-04-15 0:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 19:27 org-ref: xxx-add-bibtex-entry with an org-capture like interface Daniele Nicolodi
2020-04-09 19:43 ` John Kitchin
2020-04-10 8:11 ` Alan Schmitt
2020-04-14 17:33 ` Daniele Nicolodi
2020-04-15 0:19 ` John Kitchin [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=m2k12h7g8e.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--cc=daniele@grinta.net \
--cc=emacs-orgmode@gnu.org \
/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).