... OK, thanks to Marco and Wolfgang.
Best regads,
Lukas
On Thu, 07 Mar 2013 15:09:01 +0100, Marco Patzer home...@lavabit.com wrote:
On 2013–03–07 Procházka Lukáš Ing. - Pontex s. r. o. wrote:
kind request - \simplealignedbox is not known to me - could anyone
familar add some info to
How does one forces the item nubers to the right. The goal is have the units
above each other and not above the tens:
1 1
..not
9 9
10 10
Could not find it in the command refs of the contextgarden.
Hans van der Meer
On 2013–03–04 Meer, H. van der wrote:
How does one forces the item nubers to the right. The goal is have the units
above each other and not above the tens:
Here's an ugly solution using a box. Maybe there's a more clean
solution.
\setupitemgroup [itemize] [left=\simplealignedbox{1em
clean
solution.
\setupitemgroup [itemize] [left=\simplealignedbox{1em}{flushright}]
\starttext
\startitemize [n, packed, columns]
\dorecurse{32}{\startitem foo \stopitem}
\stopitemize
\stoptext
Marco
___
If your
On 2013–03–04 Meer, H. van der wrote:
A lucky guess did me look into the code. Whereas I got no results
with [align=] it turns out that [itemalign=flushright] does the
trick. Spares you the ugly solution.
That's indeed much better :)
Maybe someone more apt to do things in the contextgarden,
Hi,
I have two problems with vertical position, one in itemize and one in
math. The example below show them both.
\starttext
\startitemize[n]
\item
\startitemize[a][left={},right={)},stopper=]
\item Bla bla
$\theta = \arctan\bigl(\frac{\bar{y}^2}{\bar{x}^2}\bigr)$ % comment
this line out to see
The following does not seem to indent the second level itemization. The
first level is indented correctly by 2em, but the second level is not
indenting by 4em.
Troy Henderson
\setupindenting[no]
\setupitemgroup[itemize][1][][margin=2em]
\setupitemgroup[itemize][2][][margin=4em]
\starttext
Here
On 16-10-2012 00:45, Marcin Borkowski wrote:
It's me again!
This doesn't quite work as expected (at least by me, that is;)):
\starttext
\startitemize
\startitem
\placefigure[right,high,none]{}{\framed[width=3cm,height=2cm]{!}}
\input knuth
\stopitem
\stopitemize
\stoptext
Dnia 2012-10-16, o godz. 09:41:23
Hans Hagen pra...@wxs.nl napisał(a):
On 16-10-2012 00:45, Marcin Borkowski wrote:
It's me again!
This doesn't quite work as expected (at least by me, that is;)):
\starttext
\startitemize
\startitem
On 16-10-2012 10:05, Marcin Borkowski wrote:
Well, I meant the bullet and item text on the left and image on the
right. Is it possible?
maybe if you put \placefigure[right]{}{} before the \item
-
It's me again!
This doesn't quite work as expected (at least by me, that is;)):
\starttext
\startitemize
\startitem
\placefigure[right,high,none]{}{\framed[width=3cm,height=2cm]{!}}
\input knuth
\stopitem
\stopitemize
\stoptext
(Namely, at the beginning of the \item there is
On 15-9-2012 20:06, Aditya Mahajan wrote:
On Sat, 15 Sep 2012, Wolfgang Schuster wrote:
Am 15.09.2012 um 00:06 schrieb Aditya Mahajan adit...@umich.edu:
Thanks for the diagnosis. What will be a good way to fix this? I
think that
Am 15.09.2012 um 00:06 schrieb Aditya Mahajan adit...@umich.edu:
Thanks for the diagnosis. What will be a good way to fix this? I think that
\expanded{\setupcounter[#1][\c!start=\ifx\p_start\empty0\else\number\p_start\fi.,...]}
should work (but I haven't tested it yet).
I would do the
On Sat, 15 Sep 2012, Wolfgang Schuster wrote:
Am 15.09.2012 um 00:06 schrieb Aditya Mahajan adit...@umich.edu:
Thanks for the diagnosis. What will be a good way to fix this? I think that
\expanded{\setupcounter[#1][\c!start=\ifx\p_start\empty0\else\number\p_start\fi.,...]}
should work (but
in \setuppagenumber the value is kept
in \p_start (because there are no groups). When you start now the itemize
environment the same code is loaded and the start parameter (which hasn’t
been set yet) expands to a very stupid default value which is by another
helper function.
\def
Hi Aditya,
Yes it is a strange behaviour and it appears only when using mkiv and reversed
itemize, even with
\setuppagenumber[start=12]
instead of
\setupuserpagenumber[start=12]
Also the pagenumber remains unchanged with either of these commands, which
means that it's a bug
On Thu, 13 Sep 2012, Otared Kavian wrote:
On 13 sept. 2012, at 02:34, Aditya Mahajan adit...@umich.edu wrote:
For some reason, the numbering in itemize is affected by the value of userpage!
\setupuserpagenumber[start=12]
\starttext
\startitemize[n,reverse]
\item One
\item Two
\stopitemize
On Thu, 13 Sep 2012, Aditya Mahajan wrote:
On Thu, 13 Sep 2012, Otared Kavian wrote:
On 13 sept. 2012, at 02:34, Aditya Mahajan adit...@umich.edu wrote:
For some reason, the numbering in itemize is affected by the value of
userpage!
\setupuserpagenumber[start=12]
\starttext
\startitemize
On Thu, 13 Sep 2012, Aditya Mahajan wrote:
On Thu, 13 Sep 2012, Aditya Mahajan wrote:
On Thu, 13 Sep 2012, Otared Kavian wrote:
On 13 sept. 2012, at 02:34, Aditya Mahajan adit...@umich.edu wrote:
For some reason, the numbering in itemize is affected by the value of
userpage
is kept
in \p_start (because there are no groups). When you start now the itemize
environment the same code is loaded and the start parameter (which hasn’t
been set yet) expands to a very stupid default value which is by another
helper function.
\def\strc_counter_setup_using_parameter#1#2% name
Hi,
For some reason, the numbering in itemize is affected by the value of
userpage!
\setupuserpagenumber[start=12]
\starttext
\startitemize[n,reverse]
\item One
\item Two
\stopitemize
\stoptext
With ConTeXt 2012.09.11 20:36 I get
13. One
12. Two
Any ideas?
Aditya
What your got is already reversed, isn't it?
On Thu, Sep 13, 2012 at 8:34 AM, Aditya Mahajan adit...@umich.edu wrote:
Hi,
For some reason, the numbering in itemize is affected by the value of
userpage!
\setupuserpagenumber[start=12]
\starttext
\startitemize[n,reverse]
\item One
On Thu, Sep 13, 2012 at 8:34 AM, Aditya Mahajan adit...@umich.edu wrote:
Hi,
For some reason, the numbering in itemize is affected by the value of
userpage!
\setupuserpagenumber[start=12]
\starttext
\startitemize[n,reverse]
\item One
\item Two
\stopitemize
\stoptext
With ConTeXt
Am 03.07.2012 um 21:43 schrieb Meer, H. van der:
I do not understand the workings of the itemize.
What I want is two nested itemlists. The outer one unpacked, the inner one
packed. In the inner one the itemlist should be joinedup with the text before
it.
I do not get this working, see
Thanks. Is the [joinedup] deprecated? Or has it another use?
Hans van der Meer
On 5 jul. 2012, at 20:16, Wolfgang Schuster wrote:
You need the “paragraph” option.
\starttext
\setupitemgroup[itemize][1][4,unpacked]
\setupitemgroup[itemize][2][5,packed,paragraph
Am 05.07.2012 um 21:47 schrieb Meer, H. van der:
Thanks. Is the [joinedup] deprecated? Or has it another use?
The “joinedup” option works as intended, the problem in your example is that
the inner itemgroup acts different for the first item.
When you use ”joinedup” context ignores the
I do not understand the workings of the itemize.
What I want is two nested itemlists. The outer one unpacked, the inner one
packed. In the inner one the itemlist should be joinedup with the text before
it.
I do not get this working, see the examples. The inner list is separated from
the Intro
Dnia 2012-06-30, o godz. 07:05:36
Otared Kavian ota...@gmail.com napisał(a):
Hi,
The mechanisms of columns in itemize (which I think is the same as
startcolumns) and in simplecolumns are indeed different, as Hans
indicated once. The issue you encountered is indeed a bug as you
point out
Am 29.06.2012 um 23:30 schrieb Marcin Borkowski:
Hello,
I encountered a weird problem with
\startitemize[columns]
Namely, sometimes ConTeXt (MkIV) puts a pagebreak before the
itemization. I tried to distill the problem to a minimal example,
until now without success, but I'll post a
Hello,
I encountered a weird problem with
\startitemize[columns]
Namely, sometimes ConTeXt (MkIV) puts a pagebreak before the
itemization. I tried to distill the problem to a minimal example,
until now without success, but I'll post a ME if I'm able to reproduce
a problem in a small file.
Dnia 2012-06-29, o godz. 23:30:13
Marcin Borkowski mb...@wmi.amu.edu.pl napisał(a):
Hello,
I encountered a weird problem with
\startitemize[columns]
Namely, sometimes ConTeXt (MkIV) puts a pagebreak before the
itemization. I tried to distill the problem to a minimal example,
until
://mbork.pl
itemize-columns-test.tex___
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
Dnia 2012-06-30, o godz. 05:05:31
Otared Kavian ota...@gmail.com napisał(a):
Hi Marcin,
I tested your file and noticed the issue you are reporting. In your
case you can use \startsimplecolumns to get rid of the page break
(however there is a small problem with the distance between the text
Hi,
The mechanisms of columns in itemize (which I think is the same as
startcolumns) and in simplecolumns are indeed different, as Hans indicated once.
The issue you encountered is indeed a bug as you point out: once (a few months
ago) I had an analogous problem and Wolfgang S. suggested me
On 23-5-2012 04:54, Rogers, Michael K wrote:
I'll try again:
ConTeXt used to match the conversion style in a reference to the itemize item
with the number/character of the item. Now it doesn't convert numbers to
characters. Does this happen to anyone else? Example:
\setupitemgroup[itemize
On May 24, 2012, at 6:06 AM, Hans Hagen wrote:
On 23-5-2012 04:54, Rogers, Michael K wrote:
I'll try again:
ConTeXt used to match the conversion style in a reference to the itemize
item with the number/character of the item. Now it doesn't convert numbers
to characters. Does
I'll try again:
ConTeXt used to match the conversion style in a reference to the itemize item
with the number/character of the item. Now it doesn't convert numbers to
characters. Does this happen to anyone else? Example:
\setupitemgroup[itemize][1][n]
\setupitemgroup[itemize][2
. The level two items
are converted to letters, but references to them appear as unconverted numbers.
Is there a way to convert them?
\setupitemgroup[itemize][1][n]
\setupitemgroup[itemize][2][a]
\starttext
\startitemize %level 1
\item One
\startitemize %level 2
\item AA \item[BB] BB
\stopitemize
Hello,
I'm currently porting my work to the mkIV version of ConTeXt :
I've found this annoying regression with this simple example :
\starttext
Some previous sentence before the list
\startitemize[columns,n,nowhite]
\item one
\item two
\stopitemize
\startitemize[continue,columns,nowhite]
On 2012-04-26 Pierre-François Bonnefoi bonne...@unilim.fr wrote:
I'm currently porting my work to the mkIV version of ConTeXt :
I've found this annoying regression with this simple example :
[…]
I get some space between itemization with mkIV that I don't get
with mkII.
Confirmed with
On 2012-04-26 Pierre-François Bonnefoi bonne...@unilim.fr wrote:
I'm currently porting my work to the mkIV version of ConTeXt :
I've found this annoying regression with this simple example :
[…]
I get some space between itemization with mkIV that I don't get
with mkII.
Confirmed with
Hello all
Once again I return to this issue. Lukas confirmed me that really links
do not work. Where is error when links into items in the itemize list
are not working. Links are active but not working...
It is interesting that the chapter on the links when hovering tooltip
will appear
On 13-4-2012 09:50, Jaroslav Hajtmar wrote:
Hello all
Once again I return to this issue. Lukas confirmed me that really links
do not work. Where is error when links into items in the itemize list
are not working. Links are active but not working...
It is interesting that the chapter on the links
to this issue. Lukas confirmed me that really links
do not work. Where is error when links into items in the itemize list
are not working. Links are active but not working...
It is interesting that the chapter on the links when hovering tooltip
will appear with the page number where the link leads
\starttext/\stoptext and in your case
also the options for itemize.
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
Hello,
is there an option for \startitemize or \setupitemize or \setupitemgroup:
\startitemize
\item A
\startitemize
\item B
\stopitemize
\stopitemize
to get:
1. A
1.1 B (= nested item has its parent numbers, too)
or rather
1. A
1.1 B (= nested item has its
indented.
\starttext
\startitemize[n,repeat,intext]
\item A
\startitemize[A,broad]
\item B
\stopitemize
\stopitemize
\stoptext
BTW: A minimal example should contain \starttext/\stoptext and in your case
also the options for itemize.
Wolfgang
Hello all,
Where is error when not work links into items in the itemize list. Links
are active but not working?
Thanx
Jaroslav Hajtmar
Here is example:
\setupinteraction[state=start]
\starttext
\in{First link}[bibl:7] and \in{second link}[bibl:1]
\page
\startitemize[n]
\item [bibl:7
Hello all,
can somehow insert the chapter (section, subsection, ...) number as a
prefix of itemize list?
Thanx Jaroslav
Example show exactly what I mean:
\section{First section}
\startitemize
\item aaa
\item bbb
\item ccc
\stopitemize
\section{Second section}
\startitemize
\item ddd
Am 25.03.2012 um 10:36 schrieb Jaroslav Hajtmar:
Hello all,
can somehow insert the chapter (section, subsection, ...) number as a prefix
of itemize list?
Thanx Jaroslav
Example show exactly what I mean:
\section{First section}
\startitemize
\item aaa
\item bbb
\item ccc
:
Hello all,
can somehow insert the chapter (section, subsection, ...) number as a prefix of
itemize list?
Thanx Jaroslav
Example show exactly what I mean:
\section{First section}
\startitemize
\item aaa
\item bbb
\item ccc
\stopitemize
\section{Second section}
\startitemize
\item ddd
\item eee
Am 25.03.2012 um 11:36 schrieb Jaroslav Hajtmar:
Thanx Wolfgang.
How easy!
Can I also put subsection (subsubsection) number to the prefix too? It is
possible eventually set the depth level?
For example: \setupitemize[each][n,broad][prefix=yes, depthlevel=3]
You can change the section
Excellent. If works now fine!
Thanx very much Wolfgang..
Jaroslav
Dne 25.3.2012 12:02, Wolfgang Schuster napsal(a):
Am 25.03.2012 um 11:36 schrieb Jaroslav Hajtmar:
Thanx Wolfgang.
How easy!
Can I also put subsection (subsubsection) number to the prefix too? It is
possible eventually
Hello Wolfgang.
Once again I return to this topic. I send an example thatbehaves strangely.
It's a bad set of values, or error ConTeXt?
Thanx Jaroslav
\starttext
\setupitemize[each][width=3em,prefix=yes,prefixset=all]
\section{Section}
\subsection{Subsection}
\startitemize[n]
\item A
\item
Am 25.03.2012 um 16:05 schrieb Jaroslav Hajtmar:
Hello Wolfgang.
Once again I return to this topic. I send an example thatbehaves strangely.
It's a bad set of values, or error ConTeXt?
The output is correct because the prefix is only added in front of the normal
number.
I guess you want in
On Thu, Mar 22, 2012 at 03:01, Kip Warner wrote:
On Tue, 2012-03-20 at 18:22 -0400, Aditya Mahajan wrote:
Anything else will leave to undersirable behaviour (or segfaults :) ) As I
had said in one of my earlier emails, this is the case for ALL context
macros that take both options and
On 22-3-2012 11:38, Mojca Miklavec wrote:
- The fact that assignments and simple options have to be separated is
not a limitation of TeX, but the way how ConTeXt is programmed. Hans
uses a single command that takes all options inside brackets at once
that defines (results in) something similar
On 22-3-2012 11:38, Mojca Miklavec wrote:
- The fact that assignments and simple options have to be separated is
not a limitation of TeX, but the way how ConTeXt is programmed. Hans
uses a single command that takes all options inside brackets at once
that defines (results in) something similar
On 2012-03-22 11:38, Mojca Miklavec wrote:
On Thu, Mar 22, 2012 at 03:01, Kip Warner wrote:
On Tue, 2012-03-20 at 18:22 -0400, Aditya Mahajan wrote:
Anything else will leave to undersirable behaviour (or segfaults :) ) As I
had said in one of my earlier emails, this is the case for ALL
On 2012-03-22 12:21, Philipp Gesang wrote:
Therefore the difference to Context deserves mention at least
somewhere in
http://wiki.contextgarden.net/From_LaTeX_to_ConTeXt
which said migrators are most likely to consult first.
Fyi I just added a couple words to the article:
On Thu, Mar 22, 2012 at 3:01 AM, Kip Warner k...@thevertigo.com wrote:
What's probably happening is eventually the system runs out of memory,
the swap gets depleted as well, and as a last act of desperation, the
kernel finally denies an allocation request to luatex which is pretty
rare. The
On Thu, Mar 22, 2012 at 1:05 PM, luigi scarso luigi.sca...@gmail.com wrote:
On Thu, Mar 22, 2012 at 3:01 AM, Kip Warner k...@thevertigo.com wrote:
What's probably happening is eventually the system runs out of memory,
the swap gets depleted as well, and as a last act of desperation, the
kernel
On Thu, 2012-03-22 at 11:38 +0100, Mojca Miklavec wrote:
- Maybe it could be more explicit, but if you ever take a look at
documentation
Sorry, but which documentation should one obviously be looking at? The
half a dozen PDFs, the several versions of the wiki, the mailing list,
one of the
On Thu, 2012-03-22 at 12:21 +0100, Philipp Gesang wrote:
You’re right, it can cause confusion to people migrating from
Latex where package options, afair, allows mixed key-value/list
syntax (like e.g. Lua does as well). Random example from the
KOMA-Script manual:
On Thu, 2012-03-22 at 12:58 +0100, Philipp Gesang wrote:
Fyi I just added a couple words to the article:
http://wiki.contextgarden.net/From_LaTeX_to_ConTeXt#Optional_Arguments_and_Setups
please expand as needed!
Thank you.
--
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail
Hi all,
Is there a way to define your own itemize symbols? I would like a solid square,
as in symbol 8 (referring to Table 10.1 in the Context Manual, but solid/filled
whereas 8 is hollow.
I tried to declare my own bullet point, as in:
\def\squarebullet{\vrule height .9ex width .8ex depth
On 03/21/2012 10:19 AM, Malte Stien wrote:
Hi all,
Is there a way to define your own itemize symbols? I would like a solid square,
as in symbol 8 (referring to Table 10.1 in the Context Manual, but solid/filled
whereas 8 is hollow.
I tried to declare my own bullet point, as in:
\def
Am 21.03.2012 um 10:19 schrieb Malte Stien:
Hi all,
Is there a way to define your own itemize symbols? I would like a solid
square, as in symbol 8 (referring to Table 10.1 in the Context Manual, but
solid/filled whereas 8 is hollow.
I tried to declare my own bullet point
Am 21.03.2012 um 13:11 schrieb Wolfgang Schuster:
Am 21.03.2012 um 10:19 schrieb Malte Stien:
Hi all,
Is there a way to define your own itemize symbols? I would like a solid
square, as in symbol 8 (referring to Table 10.1 in the Context Manual, but
solid/filled whereas 8 is hollow
On Tue, 2012-03-20 at 22:41 +0100, luigi scarso wrote:
As I said earlier, I get a segmentation fault if I leave it to run, but
I always have to kill it before it takes down the entire operating
system with it (apparently this is normal). I don't get the TeX capacity
exceeded error message,
On Tue, 2012-03-20 at 18:22 -0400, Aditya Mahajan wrote:
Anything else will leave to undersirable behaviour (or segfaults :) ) As I
had said in one of my earlier emails, this is the case for ALL context
macros that take both options and assignments.
Fair enough. I got it to work now with,
Am 20.03.2012 um 06:49 schrieb Kip Warner:
On Tue, 2012-03-20 at 06:46 +0100, Wolfgang Schuster wrote:
TeX has it’s problem with certain errors, accept it.
It is not a problem with the program raising an error, it was how it
went about doing it. It should not have to take down the entire
On 20-3-2012 01:43, Kip Warner wrote:
On Mon, 2012-03-19 at 22:49 +0100, Hans Hagen wrote:
On 19-3-2012 00:29, Kip Warner wrote:
I've cc'd the luatex user mailing list since this is probably, I
suppose, a luatex issue more than a ConTeXt one.
not that probable
Actually highly probably,
On 20-3-2012 06:49, Kip Warner wrote:
On Tue, 2012-03-20 at 06:46 +0100, Wolfgang Schuster wrote:
TeX has it’s problem with certain errors, accept it.
It is not a problem with the program raising an error, it was how it
went about doing it. It should not have to take down the entire
operating
On Tue, Mar 20, 2012 at 9:17 AM, Hans Hagen pra...@wxs.nl wrote:
On 20-3-2012 06:49, Kip Warner wrote:
On Tue, 2012-03-20 at 06:46 +0100, Wolfgang Schuster wrote:
TeX has it’s problem with certain errors, accept it.
It is not a problem with the program raising an error, it was how it
went
On Mon, Mar 19, 2012 at 10:49:48PM -0700, Kip Warner wrote:
On Tue, 2012-03-20 at 06:46 +0100, Wolfgang Schuster wrote:
TeX has it’s problem with certain errors, accept it.
It is not a problem with the program raising an error, it was how it
went about doing it. It should not have to take
On Tue, Mar 20, 2012 at 08:21:35AM +0100, Patrick Gundlach wrote:
Am 20.03.2012 um 06:49 schrieb Kip Warner:
On Tue, 2012-03-20 at 06:46 +0100, Wolfgang Schuster wrote:
TeX has it’s problem with certain errors, accept it.
It is not a problem with the program raising an error, it was
On Tue, 2012-03-20 at 09:17 +0100, Hans Hagen wrote:
which is not really a crash of my operating system; there is not much
I
can do about this issue I fear.
Totally up to you. I just wanted to bring it to your attention.
--
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail
On Tue, 2012-03-20 at 16:57 +0200, Khaled Hosny wrote:
Older TeX engines had hard memory limit, so in case of such
syntactical errors the engine would consume all its allocated memory
and die (with a misleading error message), LuaTeX dynamically allocates
memory (for good reasons) so it won't
On 20-3-2012 19:59, Kip Warner wrote:
On Tue, 2012-03-20 at 16:57 +0200, Khaled Hosny wrote:
Older TeX engines had hard memory limit, so in case of such
syntactical errors the engine would consume all its allocated memory
and die (with a misleading error message), LuaTeX dynamically allocates
On Tue, 2012-03-20 at 20:26 +0100, Hans Hagen wrote:
well you can try what happens if you run stock lua:
local t = { }
while true do
t[#t+1] = just a bogus string: .. (#t+1)
end
at some point your system will run out of (virtual) memory or lua will
run out of whatever its limits
On Tue, Mar 20, 2012 at 8:59 PM, Kip Warner k...@thevertigo.com wrote:
On Tue, 2012-03-20 at 20:26 +0100, Hans Hagen wrote:
well you can try what happens if you run stock lua:
local t = { }
while true do
t[#t+1] = just a bogus string: .. (#t+1)
end
at some point your system will run
On 20-3-2012 20:59, Kip Warner wrote:
On Tue, 2012-03-20 at 20:26 +0100, Hans Hagen wrote:
well you can try what happens if you run stock lua:
local t = { }
while true do
t[#t+1] = just a bogus string: .. (#t+1)
end
at some point your system will run out of (virtual) memory or lua will
On Tue, 2012-03-20 at 21:39 +0100, luigi scarso wrote:
When TeX says
! TeX capacity exceeded, sorry [token memory size=...]
it is its graceful way to exit from an irreversible situation.
It can be caused by luatex or ConTeXt mkiv
but it's *not* a segmentation fault, as you said early:
On Tue, 2012-03-20 at 21:44 +0100, Hans Hagen wrote:
sure, but mu experience is that browsers of email clients are way more
demanding than tex when it comes to memory usage
I've never had either take down the entire operating system. There is a
different from intended memory usage and
On Tue, Mar 20, 2012 at 10:24 PM, Kip Warner k...@thevertigo.com wrote:
On Tue, 2012-03-20 at 21:39 +0100, luigi scarso wrote:
When TeX says
! TeX capacity exceeded, sorry [token memory size=...]
it is its graceful way to exit from an irreversible situation.
It can be caused by luatex or
On Tue, 2012-03-20 at 06:46 +0100, Wolfgang Schuster wrote:
You can’t have a assignment in both parameters because this would lead
to the same problem as before,
combine both settings in one argument and it works.
I must not be doing it right because the item numbers are gone now and
replaced
On Tue, 20 Mar 2012, Kip Warner wrote:
On Tue, 2012-03-20 at 06:46 +0100, Wolfgang Schuster wrote:
You can’t have a assignment in both parameters because this would lead
to the same problem as before,
combine both settings in one argument and it works.
I must not be doing it right because
Am 19.03.2012 um 00:29 schrieb Kip Warner:
On Sun, 2012-03-18 at 16:25 -0700, Kip Warner wrote:
On Sat, 2012-03-17 at 11:21 +0100, Wolfgang Schuster wrote:
Am 17.03.2012 um 10:21 schrieb luigi scarso:
On Sat, Mar 17, 2012 at 2:47 AM, Kip Warner k...@thevertigo.com wrote:
Hey list,
Is
On 19-3-2012 00:29, Kip Warner wrote:
I've cc'd the luatex user mailing list since this is probably, I
suppose, a luatex issue more than a ConTeXt one.
not that probable
One other thing that I should have made more clear, this only happens
when I insert the aforementioned line correction
On 19-3-2012 00:25, Kip Warner wrote:
The good news is that this is probably what I need. The bad news is
luatex completely blows itself to pieces, allocating memory until the
system crashes.
Packaging itemizes are on a todo list as I sometimes need it myself, but
it has a low priority
On Mon, 2012-03-19 at 22:49 +0100, Hans Hagen wrote:
On 19-3-2012 00:29, Kip Warner wrote:
I've cc'd the luatex user mailing list since this is probably, I
suppose, a luatex issue more than a ConTeXt one.
not that probable
Actually highly probably, since the seg fault is raised in
On Mon, 2012-03-19 at 22:50 +0100, Hans Hagen wrote:
Packaging itemizes are on a todo list as I sometimes need it myself, but
it has a low priority
Ok, but I thought they were already packaged with context?
--
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
On Mon, 2012-03-19 at 09:17 +0100, Wolfgang Schuster wrote:
Make a example because this works:
\starttext
%\dorecurse{2}{\input tufte\par}
\dorecurse{3}{\input tufte\par}
\startitemize[before={\startlinecorrection[blank]},after=
\stoplinecorrection]
\dorecurse{4}{\startitem \input
Am 20.03.2012 um 02:04 schrieb Kip Warner:
On Mon, 2012-03-19 at 09:17 +0100, Wolfgang Schuster wrote:
Make a example because this works:
\starttext
%\dorecurse{2}{\input tufte\par}
\dorecurse{3}{\input tufte\par}
\startitemize[before={\startlinecorrection[blank]},after=
On Tue, 2012-03-20 at 06:22 +0100, Wolfgang Schuster wrote:
The problem is the empty second argument.
\startitemize[before=\startlinecorrection,after=\stoplinecorrection][]
When you pass two arguments with \startitemize the first argument os for
keywords (e.g. packed or fit)
and second
Am 20.03.2012 um 06:31 schrieb Kip Warner:
On Tue, 2012-03-20 at 06:22 +0100, Wolfgang Schuster wrote:
The problem is the empty second argument.
\startitemize[before=\startlinecorrection,after=\stoplinecorrection][]
When you pass two arguments with \startitemize the first argument os for
On Tue, 2012-03-20 at 06:46 +0100, Wolfgang Schuster wrote:
TeX has it’s problem with certain errors, accept it.
It is not a problem with the program raising an error, it was how it
went about doing it. It should not have to take down the entire
operating system to indicate to the user that
On Sat, 2012-03-17 at 11:21 +0100, Wolfgang Schuster wrote:
Am 17.03.2012 um 10:21 schrieb luigi scarso:
On Sat, Mar 17, 2012 at 2:47 AM, Kip Warner k...@thevertigo.com wrote:
Hey list,
Is there any way to hint to ConTeXt that the contents of a \startitemize
\stopitemize pair should
On Mon, Mar 19, 2012 at 12:25 AM, Kip Warner k...@thevertigo.com wrote:
On Sat, 2012-03-17 at 11:21 +0100, Wolfgang Schuster wrote:
Am 17.03.2012 um 10:21 schrieb luigi scarso:
On Sat, Mar 17, 2012 at 2:47 AM, Kip Warner k...@thevertigo.com wrote:
Hey list,
Is there any way to hint to
301 - 400 of 852 matches
Mail list logo
