From: J <lixichen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Inserting citations into text editors
Date: Fri, 6 Jan 2023 04:54:58 -0800 (PST) [thread overview]
Message-ID: <c8032379-cd82-4001-93ba-1e155b364bcdn@googlegroups.com> (raw)
In-Reply-To: <948aa732-6996-44b2-a400-8798e5ba3f61-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 3384 bytes --]
Could you suggest what set of tools you ended up with to easily insert
citations into markdown text ? :D
On Thursday, September 21, 2017 at 6:03:51 AM UTC+8 MK wrote:
> This looks like a great set of tools! Unfortunately, I use Papers, and I
> tend to manage my citations with just a .bib file that Papers generates. I
> might try and adapt some of this to work with that though, and to use
> Launchbar. Not too much work I hope...
>
>
> On Sunday, September 17, 2017 at 9:50:48 AM UTC-5, iandol wrote:
>>
>> Well, you don't say which reference manager you use, but if you use
>> Bookends, and you'd consider using Alfred (I switched from Quicksilver),
>> I've curated a set of Alfred tools including one which searches the
>> database, and inserts your Pandoc formatted [@citation] in any text editor
>> or word processor:
>>
>> https://github.com/iandol/bookends-tools — becite tool
>>
>> You bring up Alfred, type in an author and get an inline list of
>> references in the Alfred window, then ⌘enter to paste the citation. I use
>> it with Scrivener, which already has excellent integration with Bookends
>> (⌘Y quick switches you between text⬄ref), when I know exactly the paper I
>> want to cite.
>>
>> On Saturday, 9 September 2017 01:15:34 UTC+8, Mendel Kranz wrote:
>>>
>>> I've been using a number of different writing programs recently, and
>>> each time I make a switch I always run into the same problem, how to easily
>>> insert citations. Most recently I've been satisfied with Sublime Text and
>>> this plugin <https://github.com/sjpfenninger/citebibtex> that reads my
>>> .bib file and easily inserts the pandoc citation. Now I'm fiddling with
>>> Ulysses, and I've run into the problem again: how to easily access and
>>> insert my citations. I plan on continuing to use a .bib file and convert
>>> with pandoc.
>>>
>>> Since I use Launchbar, I thought that if there were a way to search
>>> through my .bib file with that and insert my citation, this would make the
>>> issues disappear. However, I'm really not sure how to do it. Essentially
>>> I'm looking for the same functionality of that plugin just not tied to
>>> sublime text. Any thoughts would be appreciated!
>>>
>>> One related problem I run into with other options, is that I often have
>>> one author with multiple books which can make searching through citekeys
>>> difficult. For instance I may have 5 cite keys listed as @foo123, @foo345,
>>> @foo678, etc. So if, when searching, it could display the author name and
>>> book, and then insert the citekey that would be the best!
>>>
>>> PS I've seen some options such as this one by David Sanson
>>> <https://github.com/dsanson/bibdesk-pandoc-export-templates> which uses
>>> bibdesk, and this one which uses text expander
>>> <https://github.com/andrewheiss/pandoc-citekeys>, both of which I've
>>> found a little awkward.
>>>
>>
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/c8032379-cd82-4001-93ba-1e155b364bcdn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 5118 bytes --]
next prev parent reply other threads:[~2023-01-06 12:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 17:15 Mendel Kranz
[not found] ` <97a91bc5-d1da-45ba-8763-1617c8760f88-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-17 14:50 ` iandol
[not found] ` <a422ae0b-1a19-4c4f-82a0-048a71e9c3c9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-20 22:03 ` Mendel Kranz
[not found] ` <948aa732-6996-44b2-a400-8798e5ba3f61-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-01-06 12:54 ` J [this message]
[not found] ` <c8032379-cd82-4001-93ba-1e155b364bcdn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-01-06 16:05 ` Albert Krewinkel
[not found] ` <875ydj4osy.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-01-06 17:03 ` Joseph Reagle
2023-01-07 17:34 ` Pedro P. Palazzo
[not found] ` <e4b2b848-8b7f-4f8d-ade5-0ddc1b95fc42n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-01-08 10:52 ` John Carter Wood
[not found] ` <4e64b509-7781-4511-856c-723daf2aae4fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-01-08 20:36 ` John Purnell
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c8032379-cd82-4001-93ba-1e155b364bcdn@googlegroups.com \
--to=lixichen-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).