From: Mark Smith <mark@bbprojects.net>
Subject: Re: some bib module questions
Date: Sat, 12 Mar 2005 20:09:41 +0100 [thread overview]
Message-ID: <r02010500-1038-4A2925CB932A11D9BFF8001124759EE4@[10.0.1.4]> (raw)
In-Reply-To: <423309BA.6010706@elvenkind.com>
Taco Hoekwater wrote:
>You need 'num' in both, or 'number' in both.
...as simple as that ?
Great.
I can only suggest that I was drawn to:
refcommand=number
&
setupcite[num]
because specifically these are suggested (albeit not as a combination) in the readme. In the interests of finding out whether I'm odd. Was anybody else led astray by this ?
>compression
[...]
>is turned on by default.
Fine.
>Greetings, Taco.
>
>PS. Sorry for delayed reply, I was at euroTeX past week.
No need to apologize.
thanks,
mark.
next prev parent reply other threads:[~2005-03-12 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 21:55 Fei He
2005-01-22 8:21 ` Taco Hoekwater
2005-01-25 19:37 ` Fei He
2005-01-26 7:34 ` Taco Hoekwater
2005-02-02 4:05 ` Fei He
2005-02-02 13:48 ` Taco Hoekwater
2005-03-07 18:38 ` Mark Smith
2005-03-12 15:24 ` Taco Hoekwater
2005-03-12 19:09 ` Mark Smith [this message]
2005-03-13 10:52 ` 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='r02010500-1038-4A2925CB932A11D9BFF8001124759EE4@[10.0.1.4]' \
--to=mark@bbprojects.net \
--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).