From: Tobias Burnus <tobias.burnus@physik.fu-berlin.de>
Subject: Re: Problems with m-bibtex
Date: Thu, 7 Aug 2003 11:45:24 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0308071144150.25294-100000@g25.physik.fu-berlin.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0308061142140.10540-100000@g25.physik.fu-berlin.de>
Hi,
On Wed, 6 Aug 2003, Tobias Burnus wrote:
> I've two problems with m-bib:
> a) I want to have the cites numbered by occurrence like this [1], [2],
> etc. I managed to get 1, 2, 3 etc. in the reference list but
> in the text I get [23], [5] etc. where this number is the number of
> occurrence in the .bib file. I used:
> \setuppublications[alternative=apa]
> \setuppublications[numbering=yes,refcommand=num] %,refcommand=number]
I still have this problem.
> b) I'm using \cite[reference1, reference2] but I get only
> [23], i.e. one reference shown in the text. In the reference list they
> appear both.
This problem vanishes if I use refcommand=number instead of
refcommand=num.
Tobias
prev parent reply other threads:[~2003-08-07 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 9:46 Tobias Burnus
2003-08-07 9:45 ` Tobias Burnus [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0308071144150.25294-100000@g25.physik.fu-berlin.de \
--to=tobias.burnus@physik.fu-berlin.de \
--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).