Hi all,
after a lot of confusion I discovered that first-setup.sh is not Andy-proof. If
there is a broken internet connection, the update lua process works and pushes
the rsync error message very quickly out of the terminal. I propose to change
the rsync line to
rsync -rlptv
On Fri, Jun 8, 2012 at 6:40 PM, Andy Thomas wrote:
Hi all,
after a lot of confusion I discovered that first-setup.sh is not Andy-proof.
If there is a broken internet connection, the update lua process works and
pushes the rsync error message very quickly out of the terminal. I propose to
On Fri, Jun 8, 2012 at 6:47 PM, Mojca Miklavec wrote:
On Fri, Jun 8, 2012 at 6:40 PM, Andy Thomas wrote:
Hi all,
after a lot of confusion I discovered that first-setup.sh is not Andy-proof.
If there is a broken internet connection, the update lua process works and
pushes the rsync error
On Fri, 8 Jun 2012, Mojca Miklavec wrote:
Also keep in mind that users need to update the original script
(currently still called first-setup.sh) manually.
FWIW, I updated the PKGBUILD for arch linux:
https://aur.archlinux.org/packages.php?ID=30398
Aditya
On 8-6-2012 18:54, Mojca Miklavec wrote:
On Fri, Jun 8, 2012 at 6:47 PM, Mojca Miklavec wrote:
On Fri, Jun 8, 2012 at 6:40 PM, Andy Thomas wrote:
Hi all,
after a lot of confusion I discovered that first-setup.sh is not Andy-proof. If
there is a broken internet connection, the update lua
hi there,
here is a simple patch for first-setup.sh
in a nutshell:
- removed the first check for ruby. the same check is performed
at the end of the install process again, and IMHO it is a much
better place to show some reminders to the user after many
screenfuls of rsync flew by.
- a
Hello,
which of the following command options are (still) valid?
--modules=all
--extras=all
--goodies=all
--third=all
Which files (or in which directories) are affected by these options?
Is the asterisks '*' valid instead of 'all', i.e. e.g. --modules=* instead
--modules=all?
Is there a
2011/9/28 Procházka Lukáš Ing. - Pontex s. r. o. l...@pontex.cz:
Hello,
which of the following command options are (still) valid?
--modules=all
--extras=all
--goodies=all
--third=all
Which files (or in which directories) are affected by these options?
Is the asterisks '*' valid instead
On Wed, 28 Sep 2011 13:16:19 +0200, luigi scarso luigi.sca...@gmail.com wrote:
2011/9/28 Procházka Lukáš Ing. - Pontex s. r. o. l...@pontex.cz:
Hello,
which of the following command options are (still) valid?
--modules=all
--extras=all
--goodies=all
--third=all
Which files (or in which
2011/9/28 Procházka Lukáš l...@pontex.cz:
So thus my generalized question - what are other
secret/undocumented/unfindable options, like --goodies=
They aren't all that undocumented. For my system, this lua script is
used, and there's a pretty nice help listing right at the top of the
code:
Thomas,
On Tue, Jun 1, 2010 at 13:20, Mojca Miklavec wrote:
On Tue, Jun 1, 2010 at 12:49, Thomas A. Schmitz wrote:
Hi all, esp. Mojca,
I don't know if anything changed recently, but first-setup.sh doesn't fetch
the latest beta for me anymore, even when I feed it the --context=beta
switch.
Mojca Miklavec wrote:
As long as the server reports
wget http://www.pragma-ade.com/context/beta/cont-tmf.zip
HTTP request sent, awaiting response... 403 Forbidden
Looks like Hans' new NAS also considers working with context a
security risk. :)
On Jun 2, 2010, at 3:43 PM, Mojca Miklavec wrote:
You may try again with --context=experimental as a temporary solution.
Mojca,
I just tried this (sorry, came home only now), and now I get a version of
2010.06.02 which isn't even announced on the pragma site... So let's hope that
Hans talks
On 2-6-2010 11:35, Thomas A. Schmitz wrote:
On Jun 2, 2010, at 3:43 PM, Mojca Miklavec wrote:
You may try again with --context=experimental as a temporary solution.
Mojca,
I just tried this (sorry, came home only now), and now I get a version of
2010.06.02 which isn't even announced on
On Wed, Jun 2, 2010 at 11:45 PM, Hans Hagen pra...@wxs.nl wrote:
On 2-6-2010 11:35, Thomas A. Schmitz wrote:
On Jun 2, 2010, at 3:43 PM, Mojca Miklavec wrote:
You may try again with --context=experimental as a temporary solution.
Mojca,
I just tried this (sorry, came home only now), and
Hi all, esp. Mojca,
I don't know if anything changed recently, but first-setup.sh doesn't
fetch the latest beta for me anymore, even when I feed it the --
context=beta switch. At first, I thought it was a glitch, but I have
now tried on 3 different computers, and after running
On Tue, Jun 1, 2010 at 12:49 PM, Thomas A. Schmitz
thomas.schm...@uni-bonn.de wrote:
Hi all, esp. Mojca,
I don't know if anything changed recently, but first-setup.sh doesn't fetch
the latest beta for me anymore, even when I feed it the --context=beta
switch. At first, I thought it was a
On Tue, Jun 1, 2010 at 12:49, Thomas A. Schmitz wrote:
Hi all, esp. Mojca,
I don't know if anything changed recently, but first-setup.sh doesn't fetch
the latest beta for me anymore, even when I feed it the --context=beta
switch. At first, I thought it was a glitch, but I have now tried on 3
Please, could you check mtx-update.lua.
This should be fixed now. Hans, thanks a lot.
Mojca
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
Hi.
Please, could you check mtx-update.lua, line 376. I'm found it
suspicious that the line
command = string.format(%s -tgo --chmod=a+x
%s/texmf-context/scripts/context/lua/%s.lua %s/texmf-%s/bin/%s, bin,
texroot, script, texroot, platform, script)
don't contain contextgarden
On Fri, May 21, 2010 at 16:28, Vladimir Lomov lomov...@gmail.com wrote:
Hi.
Please, could you check mtx-update.lua, line 376. I'm found it
suspicious that the line
command = string.format(%s -tgo --chmod=a+x
%s/texmf-context/scripts/context/lua/%s.lua %s/texmf-%s/bin/%s,
On Tue, Nov 24, 2009 at 15:24, Bernhard Rosensteiner wrote:
Hello all,
after my new OSX installation i did first-setup.sh as always but now i get:
This is LuaTeX, Version beta-0.40.6-2009100310 (TeX Live 2009) (INITEX)
\write18 enabled.
Hello all,
after my new OSX installation i did first-setup.sh as always but now i get:
This is LuaTeX, Version beta-0.40.6-2009100310 (TeX Live 2009) (INITEX)
\write18 enabled.
(/Applications/ConTeXt/tex/texmf-context/tex/context/base/cont-en.tex
! I can't find file `context.tex'.
l.16 \input
Bernhard Rosensteiner wrote:
Hello all,
after my new OSX installation i did first-setup.sh as always but now i get:
This is LuaTeX, Version beta-0.40.6-2009100310 (TeX Live 2009) (INITEX)
\write18 enabled.
(/Applications/ConTeXt/tex/texmf-context/tex/context/base/cont-en.tex
! I can't find
Hello,
thanks for your advice. I solved the problem 5 minutes ago: i used the context
file version in texmf-osx-64\bin and suddenly some mysterious command line
magic happened (only the first time i did context...) and LuaTeX 0.45 worked.
best regards
Bernhard
Am 24.11.2009 um 16:21 schrieb
On Tue, Nov 24, 2009 at 15:24, Bernhard Rosensteiner wrote:
Hello all,
after my new OSX installation i did first-setup.sh as always but now i get:
This is LuaTeX, Version beta-0.40.6-2009100310 (TeX Live 2009) (INITEX)
\write18 enabled.
On Tue, Nov 24, 2009 at 16:21, Hans Hagen wrote:
Bernhard Rosensteiner wrote:
Hello all,
after my new OSX installation i did first-setup.sh as always but now i
get:
This is LuaTeX, Version beta-0.40.6-2009100310 (TeX Live 2009) (INITEX)
\write18 enabled.
27 matches
Mail list logo
