Hi Hans,
First of all, thank you very much for helping in the above problem.
Can you solve this now ? ;-)
When I change startitemize[n] to startitemize[1] in line 394 I get this
error:
! Argument of \dodoregister has an extra }.
inserted text
\par
to be read again
Hi Xan,
Have you ever considered to create a minimum example, your example is
far away from
this and you would do not only other people a favor with this but you
too.
Wolfgang
___
If your question is of
Wolfgang Schuster wrote:
Hi Xan,
Have you ever considered to create a minimum example, your example is
far away from
this and you would do not only other people a favor with this but you too.
indeed as it takes me 10 minutes of selective deletion to zoom in on the
error (tip: use a bit
En/na Hans Hagen ha escrit:
Wolfgang Schuster wrote:
Hi Xan,
Have you ever considered to create a minimum example, your example is
far away from
this and you would do not only other people a favor with this but you
too.
indeed as it takes me 10 minutes of selective deletion to zoom in on
Xan wrote:
Really, I did not know that. It's a messy thing that we could not define
what we like ;-)
it's the nature of a tex macro package; ok, i can add some strict
testing for in in mkiv but even then it might just be that someone who
knows th einternals (like wolfgang or wolfgang or
On Thu, Jul 23, 2009 at 4:37 PM, Hans Hagen pra...@wxs.nl wrote:
Xan wrote:
Really, I did not know that. It's a messy thing that we could not define
what we like ;-)
it's the nature of a tex macro package; ok, i can add some strict testing
for in in mkiv but even then it might just be
Am 23.07.2009 um 16:48 schrieb luigi scarso:
2) define your macros inside
\startPrivate[namespace]
...
\stopPrivate
And how do you want to access the macros in your document?
Wolfgang
___
If your question is of
On Thu, Jul 23, 2009 at 4:58 PM, Wolfgang Schuster
schuster.wolfg...@googlemail.com wrote:
Am 23.07.2009 um 16:48 schrieb luigi scarso:
2) define your macros inside
\startPrivate[namespace]
...
\stopPrivate
And how do you want to access the macros in your document?
by namespace ?
On Thu, 23 Jul 2009, luigi scarso wrote:
On Thu, Jul 23, 2009 at 4:37 PM, Hans Hagen pra...@wxs.nl wrote:
Xan wrote:
Really, I did not know that. It's a messy thing that we could not define
what we like ;-)
it's the nature of a tex macro package; ok, i can add some strict testing
for in
Am 23.07.2009 um 17:05 schrieb luigi scarso:
On Thu, Jul 23, 2009 at 4:58 PM, Wolfgang Schuster
schuster.wolfg...@googlemail.com wrote:
Am 23.07.2009 um 16:48 schrieb luigi scarso:
2) define your macros inside
\startPrivate[namespace]
...
\stopPrivate
And how do you want to access the
On Thu, Jul 23, 2009 at 5:05 PM, Aditya Mahajan adit...@umich.edu wrote:
On Thu, 23 Jul 2009, luigi scarso wrote:
On Thu, Jul 23, 2009 at 4:37 PM, Hans Hagen pra...@wxs.nl wrote:
Xan wrote:
Really, I did not know that. It's a messy thing that we could not define
what we like ;-)
On Thu, Jul 23, 2009 at 5:10 PM, Wolfgang Schuster
schuster.wolfg...@googlemail.com wrote:
Am 23.07.2009 um 17:05 schrieb luigi scarso:
On Thu, Jul 23, 2009 at 4:58 PM, Wolfgang Schuster
schuster.wolfg...@googlemail.com wrote:
Am 23.07.2009 um 16:48 schrieb luigi scarso:
2) define
Am 23.07.2009 um 17:05 schrieb Aditya Mahajan:
I think an easier thing to do will be to follow latex's style of
\newcommand and \renewcommand. That is, all \definecommands should
check if the macro is previously defined or not. If it is defined,
issue a warning or an error.
There is
On Thu, Jul 23, 2009 at 5:16 PM, luigi scarso luigi.sca...@gmail.comwrote:
On Thu, Jul 23, 2009 at 5:10 PM, Wolfgang Schuster
schuster.wolfg...@googlemail.com wrote:
Am 23.07.2009 um 17:05 schrieb luigi scarso:
On Thu, Jul 23, 2009 at 4:58 PM, Wolfgang Schuster
Am 23.07.2009 um 17:16 schrieb luigi scarso:
hmm, where do you see the problem ?
As programmer it's no problem to use a namespace for macros but how
do you convince users to use them, should they write
\startprivate[foo]
\definenote[footnote][...]
\defineregister[index][...]
En/na Hans Hagen ha escrit:
Xan wrote:
Really, I did not know that. It's a messy thing that we could not
define what we like ;-)
it's the nature of a tex macro package; ok, i can add some strict
testing for in in mkiv but even then it might just be that someone who
knows th einternals
On Thu, Jul 23, 2009 at 5:33 PM, Wolfgang Schuster
schuster.wolfg...@googlemail.com wrote:
Am 23.07.2009 um 17:16 schrieb luigi scarso:
hmm, where do you see the problem ?
As programmer it's no problem to use a namespace for macros but how
do you convince users to use them,
it's up
On Thu, 23 Jul 2009, Wolfgang Schuster wrote:
Am 23.07.2009 um 17:05 schrieb Aditya Mahajan:
I think an easier thing to do will be to follow latex's style of
\newcommand and \renewcommand. That is, all \definecommands should check if
the macro is previously defined or not. If it is defined,
On Thu, Jul 23, 2009 at 5:52 PM, Aditya Mahajan adit...@umich.edu wrote:
On Thu, 23 Jul 2009, Wolfgang Schuster wrote:
Am 23.07.2009 um 17:05 schrieb Aditya Mahajan:
I think an easier thing to do will be to follow latex's style of
\newcommand and \renewcommand. That is, all
Aditya Mahajan wrote:
\def\defineSOMETHING%
{\dodoubleargument\dodefineSOMETHING}
\def\dodefineSOMETHING[#1][#2]%
{\setvalue{#1}{\dododefineSOMETHING[#2]}
some do, but sometimes redefinition is quite legal; it happens that
'note' and 'symbol' are pretty core
the convention (as
20 matches
Mail list logo
