emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Moe <mail@christianmoe.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Matt Lundin <mdl@imapmail.org>, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [ANN] org-bibtex.el --- convert between Org headings and bibtex entries
Date: Sun, 24 Apr 2011 18:53:50 +0200	[thread overview]
Message-ID: <4DB4559E.8010309@christianmoe.com> (raw)
In-Reply-To: <871v0rzp8v.fsf@gmail.com>

On 4/24/11 4:21 PM, Eric Schulte wrote:
> Matt Lundin<mdl@imapmail.org>  writes:
>> (...)
>> Eric, the more I think about this, the more my vote would be to package
>> this new functionality separately.
>>
>> IMO, hyperlinking to external data in bib files is somewhat orthogonal
>> to storing bib data within org files. In other words, the current
>> org-bibtex.el complements bibtex-mode use, whereas the new org-bibtex
>> functions, for the most part, are substitutes for bibtex-mode---i.e.,
>> they re-implement much of its configuration and basic functionality.
>>
>> By packaging the new functionality separately perhaps we could lay the
>> groundwork for internal, backend agnostic bibliographical export and
>> formatting---not unlike the way in which org-contacts.el replaces bbdb.
>>
>
> Alright, I think I agree that separate packaging would be the best way
> forward given the existing conventions wrt linking to functionality
> rather than implementing said functionality.

The *conclusion* (where Eric Schulte's new bibtex functions should go) 
is not a big concern to me, but FWIW, the *premise* strikes me as 
unnecessarily restrictive.

I submit that, for any non-Org format or application "foo", the module 
org-foo.el does not have to be restricted to providing an Org link 
type for foo. It seems a sensible namespace for e.g. foo-Org/Org-foo 
conversion functions as well. The fact that several modules so named 
*at present* only provide link functionality does not, I think, amount 
to a convention that this is all they should do.

 > By packaging the new functionality separately perhaps we could lay the
 > groundwork for internal, backend agnostic bibliographical export and
 > formatting---not unlike the way in which org-contacts.el replaces bbdb.

That's a great aim. Still, a future bibliography module (be it 
"org-bib", "org-cite" or whatever) could just as well rely, for bits 
of bibtex functionality, on some utilities packaged in org-bibtex.

Yours,
Christian

  reply	other threads:[~2011-04-24 16:48 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-19 23:52 [ANN] org-bibtex.el --- convert between Org headings and bibtex entries Eric Schulte
2011-04-20  1:01 ` Jeff Horn
2011-04-20  1:13   ` Eric Schulte
2011-04-20  7:54 ` Thomas S. Dye
2011-04-20 13:25   ` Matt Lundin
2011-04-20 14:29     ` Matt Lundin
2011-04-20 19:59     ` Eric Schulte
2011-04-20 19:00   ` Eric Schulte
2011-04-21 16:36     ` Thomas S. Dye
2011-04-21 21:06       ` Eric Schulte
2011-04-23 16:23         ` Thomas S. Dye
2011-04-23 22:59           ` Alan E. Davis
2011-04-24  0:40             ` Matt Lundin
2011-04-24 14:21               ` Eric Schulte
2011-04-24 16:53                 ` Christian Moe [this message]
2011-04-25 13:19                   ` Matt Lundin
2011-04-25 13:34                     ` Eric Schulte
2011-04-25 15:15                 ` Matt Lundin
2011-04-27 22:16                   ` Eric Schulte
2011-04-24  0:52             ` Eric Schulte
2011-04-24  4:49               ` Alan E. Davis
2011-04-24 14:29                 ` Eric Schulte
2011-04-24 20:40                   ` Alan E. Davis
2011-04-25 13:31                     ` Eric Schulte
2011-04-20  9:26 ` Christian Moe
2011-04-20 20:15   ` Eric Schulte
2011-04-20 12:10 ` Matt Lundin
2011-04-20 20:16   ` Eric Schulte
2011-04-22 14:05   ` [PATCH] " Eric Schulte
2011-04-22 15:45     ` Matt Lundin
2011-04-23  0:03       ` Matt Lundin
2011-04-23 14:07         ` Eric Schulte
2011-04-23 22:46           ` Matt Lundin

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=4DB4559E.8010309@christianmoe.com \
    --to=mail@christianmoe.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mdl@imapmail.org \
    --cc=schulte.eric@gmail.com \
    /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).