From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Bib module produces no output
Date: Tue, 04 Jan 2005 18:00:24 +0100 [thread overview]
Message-ID: <41DACBA8.80202@wxs.nl> (raw)
In-Reply-To: <20050104103432.GA2231@erik.fi.muni.cz>
David Antos wrote:
> On Tue, Jan 04, 2005 at 11:00:51AM +0100, Christopher Creutzig wrote:
>
>> Definitely not. I don't know about you, but I'd very much prefer to
>>use the same .bib file for different articles/texts. Numerous groups
>>in this and other universities even use a collective .bib file for
>>all the researchers. (We are just doing too diverse things in this
>>group for that.)
>
>
> Hello,
>
> don't worry, that is not the point. What I wanted is to include all
> bibliographies cited in the work, not just the current chapter (which is
> empty if you have a separate "bibliography chapter").
>
> It has nothing to do with choosing the entries from .bib file. This
> should include cited entries only and all entries as an option (as we're
> used to).
i an look into it but then i need some files [indeed a minimal example] to test
with; i don't have bib tex files and/or files using them on my system
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2005-01-04 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-02 14:44 David Antos
2005-01-02 14:58 ` Taco Hoekwater
2005-01-02 22:01 ` David Antos
2005-01-03 11:17 ` Hans Hagen
2005-01-03 12:42 ` David Antos
2005-01-03 17:05 ` Hans Hagen
2005-01-04 10:00 ` Christopher Creutzig
2005-01-04 10:34 ` David Antos
2005-01-04 17:00 ` Hans Hagen [this message]
2005-01-04 18:21 ` Taco Hoekwater
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=41DACBA8.80202@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/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).