Re: [NTG-context] I can't change startitemize[n]-- startitemize[1]
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 interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] I can't change startitemize[n]-- startitemize[1]
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 more empty lines in your source)
\defineregister[symbol][symbols]
\starttext
\startitemize[1] \item test \stopitemize
\stoptext
as you redefine \symbol to be a register entry resolving \symbol[1]
inside the itemize does not work any more as expected
so, when defining commands
- avoid built incommands
- for instance by using longer names
- or names that are unlikely to show up in the core
- or Symbol or MySymbol or so
furthermore, a few tips:
\setupbodyfont [cmr,11pt] % cmr, 11pt
% no need for cmr
\setuphead[chapter][style={\tfd\bf}]
% \bfd is a bit faster (no need for {} unless embedded [])
\usemodule[bib]
\usemodule[bibltx]
\setupbibtex[database=memoria,sort=author]
% avoid this in examples as we don't have your data
\usemodule[newmat]
% most math is in the core so that module is kind of obsolete
\usemodule[math-ams]
% not needed, as it is preloaded or loaded automatically
\hyphenation{do-cu-ment}
\hyphenation{pro-ble-ma}
\hyphenation{es-crip-tu-ra}
\hyphenation{ge-ne-ra-lit-za-ció}
\hyphenation{cor-res-po-nents}
\hyphenation{pa-rells}
\hyphenation{ge-ne-rat}
% collect these exceptions and send then to mojca or arthur
\usemodule[tikz]
\usemodule[pgfmath]
\usetikzlibrary[mindmap,arrows,calc,decorations.pathmorphing,decorations.markings]
% it seems that something is loaded twice (or at least dimension
registers are redefined)
\setupunderbar[alternative=b] % Fix underline style
% you can use the textbackgrounds for this (see anch-bar)
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
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] I can't change startitemize[n]-- startitemize[1]
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
the error (tip: use a bit more empty lines in your source)
\defineregister[symbol][symbols]
\starttext
\startitemize[1] \item test \stopitemize
\stoptext
Thank you VERY much Hans. I'm charmed. Thanks. I was crazy finding the
error. I was convinced that it was a silly thing.
as you redefine \symbol to be a register entry resolving \symbol[1]
inside the itemize does not work any more as expected
so, when defining commands
- avoid built incommands
- for instance by using longer names
- or names that are unlikely to show up in the core
- or Symbol or MySymbol or so
Really, I did not know that. It's a messy thing that we could not define
what we like ;-)
furthermore, a few tips:
\setupbodyfont [cmr,11pt] % cmr, 11pt
% no need for cmr
Yes I know.
\setuphead[chapter][style={\tfd\bf}]
% \bfd is a bit faster (no need for {} unless embedded [])
OKay.
\usemodule[bib]
\usemodule[bibltx]
\setupbibtex[database=memoria,sort=author]
% avoid this in examples as we don't have your data
Okay. Sorry.
\usemodule[newmat]
% most math is in the core so that module is kind of obsolete
\usemodule[math-ams]
% not needed, as it is preloaded or loaded automatically
Mmmm... interesting. I remember that I put because I just want to put
one symbol. I don't remember why I have that
\hyphenation{do-cu-ment}
\hyphenation{pro-ble-ma}
\hyphenation{es-crip-tu-ra}
\hyphenation{ge-ne-ra-lit-za-ció}
\hyphenation{cor-res-po-nents}
\hyphenation{pa-rells}
\hyphenation{ge-ne-rat}
% collect these exceptions and send then to mojca or arthur
Okay. It's a pleasure to give to you.
How can I see what is, if there is, the lists of hyphenated words?
\usemodule[tikz]
\usemodule[pgfmath]
\usetikzlibrary[mindmap,arrows,calc,decorations.pathmorphing,decorations.markings]
% it seems that something is loaded twice (or at least dimension
registers are redefined)
\setupunderbar[alternative=b] % Fix underline style
% you can use the textbackgrounds for this (see anch-bar)
Thanks for this pointing
Regards,
Xan.
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] I can't change startitemize[n]-- startitemize[1]
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 wolfgang) wants to overload something built in by something better % collect these exceptions and send then to mojca or arthur Okay. It's a pleasure to give to you. How can I see what is, if there is, the lists of hyphenated words? best ask mojca or arthur who to contact as they are in charge of pattern management for all tex distributions 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 - ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] I can't change startitemize[n]-- startitemize[1]
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 that someone who knows th einternals (like wolfgang or wolfgang or wolfgang) wants to overload something built in by something better why not discipline ? I mean something like 0) context macro are ok 1) \usemodule[foo] are ok (no collision with macros in 0) 2) define your macros inside \startPrivate[namespace] ... \stopPrivate 3) explicit redefinition of macros in 0,1 by 3) should be no collision between 0,1,2 -- luigi ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] I can't change startitemize[n]-- startitemize[1]
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 interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] I can't change startitemize[n]-- startitemize[1]
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 ? -- luigi ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] I can't change startitemize[n]-- startitemize[1]
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 in mkiv but even then it might just be that someone who knows th einternals (like wolfgang or wolfgang or wolfgang) wants to overload something built in by something better why not discipline ? I mean something like 0) context macro are ok 1) \usemodule[foo] are ok (no collision with macros in 0) 2) define your macros inside \startPrivate[namespace] ... \stopPrivate 3) explicit redefinition of macros in 0,1 by 3) should be no collision between 0,1,2 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. And maybe have some hook to disable the warning/error for those who know what they are doing. Aditya ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] I can't change startitemize[n]-- startitemize[1]
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 macros in your document? by namespace ? can you give a example! Wolfgang ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] I can't change startitemize[n]-- startitemize[1]
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 ;-) 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 wolfgang) wants to overload something built in by something better why not discipline ? I mean something like 0) context macro are ok 1) \usemodule[foo] are ok (no collision with macros in 0) 2) define your macros inside \startPrivate[namespace] ... \stopPrivate 3) explicit redefinition of macros in 0,1 by 3) should be no collision between 0,1,2 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. And maybe have some hook to disable the warning/error for those who know what they are doing. yes, it's equivalent -- luigi ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] I can't change startitemize[n]-- startitemize[1]
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 your macros inside \startPrivate[namespace] ... \stopPrivate And how do you want to access the macros in your document? by namespace ? can you give a example! hmm, where do you see the problem ? -- luigi ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] I can't change startitemize[n]-- startitemize[1]
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 \define and \redefine. And maybe have some hook to disable the warning/error for those who know what they are doing. In this case you can use \def, \edef ... Wolfgang ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] I can't change startitemize[n]-- startitemize[1]
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 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 ? can you give a example! hmm, where do you see the problem ? I mean, we already have \setvalue -- luigi ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] I can't change startitemize[n]-- startitemize[1]
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][...] ... \stopprivate and use them with 'fooindex', 'foofootnote' ... in their documents? In this case it would be better to write to write commands like \MyNote Wolfgang ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] I can't change startitemize[n]-- startitemize[1]
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 (like wolfgang or wolfgang or wolfgang) wants to overload something built in by something better In my modest opinion it could help: a warning that says you overload something predefined. And really I think it helps it the error message is more explicit. A normal user like me turn crazy trying to find the error But well, you are the boss ;-) % collect these exceptions and send then to mojca or arthur Okay. It's a pleasure to give to you. How can I see what is, if there is, the lists of hyphenated words? best ask mojca or arthur who to contact as they are in charge of pattern management for all tex distributions Okay, In private or public mail? Xan. ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] I can't change startitemize[n]-- startitemize[1]
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 to us make an easy convention. should they write \startprivate[foo] \definenote[footnote][...] \defineregister[index][...] ... \stopprivate and use them with 'fooindex', 'foofootnote' ... in their documents? true, but what about \startprivate[texns:Logo='www.logosrl.it/context'] \definenote[Footnote][...] \defineregister[Index][...] ... \stopprivate \LogoFootnote \LogoIndex Not so horrible; one can easily see in the source own private macros. In this case it would be better to write to write commands like \MyNote Yes, it's a discipline problem. -- luigi ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___
Re: [NTG-context] I can't change startitemize[n]-- startitemize[1]
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, issue a warning
or an error.
There is \define and \redefine.
I know. What I am asking is that the core macros like \definedescription,
\defineitemgroups, \definehead, which have the general form
\def\defineSOMETHING%
{\dodoubleargument\dodefineSOMETHING}
\def\dodefineSOMETHING[#1][#2]%
{\setvalue{#1}{\dododefineSOMETHING[#2]}
should do some check before the \setvalue. Maybe a universal solution will
be to change \setvalue so that it uses \define (or a check like define)
internally.
And maybe have some hook to disable the warning/error for those who know
what they are doing.
In this case you can use \def, \edef ...
I meant with commands like \defineSOMETHING above. For example, I once did
\definecolor[page][s=0.9] instead of what I normally do:
\definecolor[pagecolor][s=0.9]. Took a while to figure out what was going
wrong. Some of Xan's error were due to similar things,
\defineSOMETHING[note], \defineSOMETHING[symbol], etc. If all these
commands issued a warning that you are redefining existing macro,
debugging will be much easier. And if you know what you are doing, we
could have
\redefinecolor[page][s=0.9]
that does not issue a warning. Or the easier to implemnet:
\setupcolors[check=error|warn|ignore]
for all \setupSOMETHING commands where the equivalent \defineSOMETHING
defines a control sequence.
Aditya
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] I can't change startitemize[n]-- startitemize[1]
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 \definecommands should check if
the macro is previously defined or not. If it is defined, issue a warning or
an error.
There is \define and \redefine.
I know. What I am asking is that the core macros like \definedescription,
\defineitemgroups, \definehead, which have the general form
\def\defineSOMETHING%
{\dodoubleargument\dodefineSOMETHING}
\def\dodefineSOMETHING[#1][#2]%
{\setvalue{#1}{\dododefineSOMETHING[#2]}
should do some check before the \setvalue. Maybe a universal solution will
be to change \setvalue so that it uses \define (or a check like define)
internally.
Or maybe
\Usersetvalue
I think to an user-space
and a kernel-space
--
luigi
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
Re: [NTG-context] I can't change startitemize[n]-- startitemize[1]
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 mentioned) is more or less to use UpperCase names for
your own commands and UPPERCASE for logo's and abbreviations (but these
can have an optional namespace)
kind of tricky are colors and fonts as they have no namespace so i often
end up with ThisColor or ThatFont
I meant with commands like \defineSOMETHING above. For example, I once
did \definecolor[page][s=0.9] instead of what I normally do:
\definecolor[pagecolor][s=0.9]. Took a while to figure out what was
going wrong. Some of Xan's error were due to similar things,
\defineSOMETHING[note], \defineSOMETHING[symbol], etc. If all these
commands issued a warning that you are redefining existing macro,
debugging will be much easier. And if you know what you are doing, we
could have
\redefinecolor[page][s=0.9]
that does not issue a warning. Or the easier to implemnet:
\setupcolors[check=error|warn|ignore]
maybe later, as it clutters the code; maybe after the mkii-mkiv cleanup
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
-
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___
