unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jameson Graef Rollins <jrollins@finestructure.net>
To: "Rainer M. Krug" <Rainer@krugs.de>
Cc: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: Xapers
Date: Tue, 16 Apr 2013 02:14:19 -0700	[thread overview]
Message-ID: <87r4iasuqc.fsf@servo.finestructure.net> (raw)
In-Reply-To: <87txn6lvpd.fsf@krugs.de>

[-- Attachment #1: Type: text/plain, Size: 961 bytes --]

On Tue, Apr 16 2013, "Rainer M. Krug" <Rainer@krugs.de> wrote:
> It would be quite important to be able to do something along the lines
> of
>
>   xapers import --bib=TheBibtexFile.bib

Hi, Rainer:

Xapers does currently do something similar to this.  The following takes
the first bibtex entry from bibtex.bib and creates a new Xapers
document:

  xapers add --source=bibtex.bib

However, I suspect you're looking for a way to import a full bibtex
database with multiple entries, and create a new Xapers document for
each.  This shouldn't be difficult to implement.  Particularly if there
is a standard bibtex field for specifying associated file paths.
Patrick mentioned that jabref uses something, so maybe I can start with
that.

> Is there a mailing list or place where you anounce new versions?

It does look like there might be a need.  I'll look into putting
something together.

In the mean time I'm hanging out on #xapers on irc.freenode.net.

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2013-04-16  9:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15  8:07 Xapers Jameson Graef Rollins
2013-04-15 17:18 ` Xapers Jameson Graef Rollins
2013-04-15 18:46   ` Xapers Patrick Totzke
2013-04-15 19:07     ` Xapers Jameson Graef Rollins
2013-04-16  8:35       ` Xapers Rainer M. Krug
2013-04-16  9:14         ` Jameson Graef Rollins [this message]
2013-04-16 10:05           ` Xapers Rainer M. Krug
2013-05-31 19:04   ` Xapers Jameson Graef Rollins

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://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r4iasuqc.fsf@servo.finestructure.net \
    --to=jrollins@finestructure.net \
    --cc=Rainer@krugs.de \
    --cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).