nico wrote:
On Tue, 09 May 2006 23:38:47 +0200, Hans Hagen [EMAIL PROTECTED] wrote:
nico wrote:
Hello,
Is it possible to display a list of the numbered formulas (done with
\placeformula)? I tried \placelist[formula] without success.
you want to see the formulas too?
Johannes Graumann wrote:
Trouble with tex/context/base/cont-err.tex:
system : cont-err loaded
(/home/balin/texmf/tex/context/base/cont-err.tex
Runaway argument?
on Otten}] %C %C This module is part of the \CONTEXT\ macro||package \ETC.
! Paragraph ended before was complete.
to
Johannes Graumann wrote:
Trouble with tex/context/base/cont-err.tex:
system : cont-err loaded
(/home/balin/texmf/tex/context/base/cont-err.tex
Runaway argument?
on Otten}] %C %C This module is part of the \CONTEXT\ macro||package \ETC.
! Paragraph ended before was complete.
to
nico wrote:
On Tue, 09 May 2006 23:38:47 +0200, Hans Hagen [EMAIL PROTECTED] wrote:
nico wrote:
Hello,
Is it possible to display a list of the numbered formulas (done with
\placeformula)? I tried \placelist[formula] without success.
you want to see the formulas too?
Sanjoy Mahajan wrote:
Using components (e.g. book chapters), with each component in its own
directory, say I have
\startproduct onebook
\project manybooks
\component 1/chap
\component 2/chap
\stopproduct
with this 1/chap.tex:
\startcomponent 1/chap
\product onebook
\project manybooks
Hi all,
(I have solved the punctuation-related problem)
I have tried to make a minimal example but failed in reproducing the
problem... Seems to be a problem in my complex environment. Did one of
yours have already faced this kind of strange problems with accentuated
characters within
Is the idea to use \currentcomponentpath in the directory={...}? I put
indeed
I've just tried the version below, but abc-1.eps cannot be found (I
also tried \noexpand\currentcomponentpath):
% file: chap/1/c_ch1.tex
\startcomponent c_ch1
\product onebook
\project project_books
Sanjoy Mahajan wrote:
Is the idea to use \currentcomponentpath in the directory={...}? I put
indeed
I've just tried the version below, but abc-1.eps cannot be found (I
also tried \noexpand\currentcomponentpath):
% file: chap/1/c_ch1.tex
\startcomponent c_ch1
\product
Hans,
do I need to re-report that format generation with texmfstart
newtexexec --make is still broken on OS X (I'll check on my linux box
later)? I still get these monstrous paths like
TeXExec | tex engine path: .:/Users/tas/texmf/web2c//:!!/usr/local/
so how is this component, when run on itself, supposed to locate itself,
Not sure I completely understand your question. But if I run one
component, I change to its directory first:
cd chap/1 texexec c_ch1.tex
Or is the canonical method:
texexec chap/1/c_ch1.tex
?
I've been in the
Hans and Sanjoy,
I am doing something similar, so I am following this discussion closely.
On my machine, the main directory is ~/Documents/IntAlgText/trunk.
The main directory contains my environment files and book.tex (the
project).
Then I have these directories.
On 9 May 2006, Hans Hagen wrote:
Na Li wrote:
Is there a way of defining an itemize style without having to specify
the same set of options to \startitemize every time? Something like:
\defineitemize[myitemize][s,packed][width=5em,stopper=:,style=bold]
\defineitemgroup
That does
On Tue, 9 May 2006, Hans Hagen wrote:
There is a fundamental difference between
bla \framed{bla} bla
and
\framed{bla} bla bla
that is not understandable.
this is the case for many more things and a tex speciality which takes
while to get
Hans,
This ruby stuff has me confused to no end.
I'm compiling this document (which compiled just fine with the last
release - no changes since) with the following command:
ruby ~/texmf/scripts/context/ruby/texexec.rb PhD-Thesis.tex
For trying to figure out the version I do:
ruby
Sorry but I have just see the = instead of 1 in emacs !!! (Dunno how it
was happened)
I have finally checked the coding system of all of my file...
That's ok now...
Take care of your coding system... ;)
Cheers,
Renaud
___
ntg-context mailing list
Johannes Graumann wrote:
Hans,
This ruby stuff has me confused to no end.
I'm compiling this document (which compiled just fine with the last
release - no changes since) with the following command:
ruby ~/texmf/scripts/context/ruby/texexec.rb PhD-Thesis.tex
For trying to figure out the
Thomas A. Schmitz wrote:
Hans,
do I need to re-report that format generation with texmfstart
newtexexec --make is still broken on OS X (I'll check on my linux box
later)? I still get these monstrous paths like
TeXExec | tex engine path: .:/Users/tas/texmf/web2c//:!!/usr/local/
Thomas A. Schmitz wrote:
Hans,
do I need to re-report that format generation with texmfstart
newtexexec --make is still broken on OS X (I'll check on my linux box
later)? I still get these monstrous paths like
TeXExec | tex engine path: .:/Users/tas/texmf/web2c//:!!/usr/local/
� wrote:
On Tue, 9 May 2006, Hans Hagen wrote:
There is a fundamental difference between
bla \framed{bla} bla
and
\framed{bla} bla bla
that is not understandable.
this is the case for many more things and a tex speciality which
Hello,
I should have written this a long time ago when Hans improved drastically
this feature. For those who may be interested in:
http://wiki.contextgarden.net/Verbatim_text#Line_numbering
Regards,
BG
___
ntg-context mailing list
ntg-context@ntg.nl
Yes, that's strange. I just checked, and everything is golden on a linux
system (gentoo, but I gues the same is true for other linux distros). So
I really don't see why OS X should behave differently. Is there any
debugging info that I could provide? How 'bout the other OS X users (I
seem to
Thomas A. Schmitz wrote:
Yes, that's strange. I just checked, and everything is golden on a linux
system (gentoo, but I gues the same is true for other linux distros). So
I really don't see why OS X should behave differently. Is there any
debugging info that I could provide? How 'bout the
Hans,
I linked texmfstart.rb to texmfstart in my local bin directory (which is in
the path) and issued 'chmod -R +x ~/texmf/scripts'. If I call 'ruby
~/texmf/scripts/context/ruby/texexec.rb --check' now, I get this error free
(but not informative) output:
TeXExec | current distribution: web2c
On Thu, 11 May 2006 00:11:47 +0200, Thomas A. Schmitz
[EMAIL PROTECTED] wrote:
Yes, that's strange. I just checked, and everything is golden on a linux
system (gentoo, but I gues the same is true for other linux distros). So
I really don't see why OS X should behave differently. Is there any
Taco Hoekwater wrote:
This is the very top of cont-err.tex, the 'module header'.
If that does not look broken,
then probably the file that
loads it does so while some really strange catcode settings
are in effect. The most likely cause is that you have an
invalid zip file or an error has
On Tue, 9 May 2006, Taco Hoekwater wrote:
Aditya Mahajan wrote:
Thanks. For my present project I need short month names, and the
deadline is tomorrow. So, I will stick to the manual solution at the
moment.
There should be no need for manual fixes, just do this:
\unprotect
And the beginning lines in section1.tex look like this:
\startcomponent section1
\project book
\product chapter0/chapter0
Does it matter what you put after the \startcomponent? I'm always
trying to figure out whether to use the full relative path or just the
last piece of it.
Would
On May 10, 2006, at 19:13, Hans Hagen wrote:
Thomas A. Schmitz wrote:
Hans,
do I need to re-report that format generation with texmfstart
newtexexec --make is still broken on OS X (I'll check on my linux box
later)? I still get these monstrous paths like
TeXExec | tex engine path:
On Thu, 11 May 2006, Sanjoy Mahajan wrote:
I haven't tried to compile book.tex (too big), so I don't know if
that works.
It might work, though I remember reading on the list sometime that one
isn't supposed to compile the project file -- only the components or
the products.
I had
29 matches
Mail list logo