From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: [dev-context] Re: new beta
Date: Thu, 8 Sep 2005 16:59:48 +0200 [thread overview]
Message-ID: <6faad9f0050908075953120dfc@mail.gmail.com> (raw)
In-Reply-To: <432031F2.6090503@elvenkind.com>
> \definecharacter numbersign \companionsymbol{35}
But please leave a possibility for something like
\companionsymbol[1]{35}
\companionsymbol[3]{49}
...
(Not the exact syntax, only the principle, which should not set the
limits to 256 again.)
Otherwise we're at the beginning again once the number of
"companionsymbols" exceeds 256.
Mojca
next prev parent reply other threads:[~2005-09-08 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 16:48 Hans Hagen
[not found] ` <43200FFB.3060703@elvenkind.com>
[not found] ` <43201B66.5050300@wxs.nl>
[not found] ` <432031F2.6090503@elvenkind.com>
2005-09-08 14:59 ` Mojca Miklavec [this message]
2005-09-08 15:14 ` [dev-context] " Hans Hagen
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=6faad9f0050908075953120dfc@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.com \
--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).