\startitemize
\item First
\item Second
\stopitemize
\stopparagraph
\stopsection
\stoptext
~~~
Running `context test.tex` generates a `test.export` file that looks as
follows:
~~~ {test.export}
?xml version='1.0' encoding='UTF-8' standalone='yes' ?
!-- input filename
this
might be interesting.
1. Use the filename of a font. With the “file:” prefix you can the
tell the module
to look for a file with the given name, when the file isn’t found the
font from
the tf-alternative is used. The file-method is also used when you omit
the prefix.
\setupfontfamily [serif
examples where I change the font for
italic.
1. Use the filename of a font. With the “file:” prefix you can the tell the
module
to look for a file with the given name, when the file isn’t found the font from
the tf-alternative is used. The file-method is also used when you omit the
prefix
.
Underfull \hbox (badness 2401) in paragraph at lines 464--464
... lots more output ...
system | total runtime: 1.962
How do you prevent ConTeXt from writing anything whatsoever to the
console?
context --batchmode filename /dev/null
:-)
\dontcomplain also helps
at lines 464--464
... lots more output ...
system | total runtime: 1.962
How do you prevent ConTeXt from writing anything whatsoever to the console?
context --batchmode filename /dev/null
:-)
Aditya
--context=current
Now, you can run
source path-to-context-beta/tex/setuptex context filename
to compile a file using context beta and
source path-to-context-stable/tex/setptex context filename
to compile a file using context stable.
Aditya
and copy first-setup.sh in
both directories, and run:
cd context-beta first-setup
cd context-stable first-setup --context=current
Now, you can run
source path-to-context-beta/tex/**setuptex context filename
to compile a file using context beta and
source path-to-context
!
Because it is open-source: It is possible to addapt this tool for
context, too? Maybe one of the programmers have time for this ... :)
I use the perl program `atchange`[1] for continous preview. For
simple documents, you can just run
atchange filename.tex context --batch filename
On Wed, 28 Aug 2013, H. Özoguz wrote:
I use the perl program `atchange`[1] for continous preview. For simple
documents, you can just run
atchange filename.tex context --batch filename
Thanks Aditja. Because I have no experience with Pearl: What to do with this
text-file of your link
I use the perl program `atchange`[1] for continous preview. For simple
documents, you can just run
atchange filename.tex context --batch filename
Thanks Aditja. Because I have no experience with Pearl: What to do with
this text-file of your link? Should I just copy it as text-file
of the programmers have time for this ... :)
I use the perl program `atchange`[1] for continous preview. For simple
documents, you can just run
atchange filename.tex context --batch filename
For more complicated documents (depending on multiple files and figures),
you can create a automate
might get some sipped up if you enable write18.
How can I run the old slides through mkiv?
context filename
Aditya
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist
depends on the number of metapost runs needed to create all the
random frames. You might get some sipped up if you enable write18.
How can I run the old slides through mkiv?
context filename
Aditya
___
If your
' to file
'/usr/local/texlive/2013/texmf-dist/fonts/opentype/public/lm/lmroman12-regular.otf'
fontsdefining defining tfm, name 'lmroman12-regular', fullname
'LMRoman12-Regular', filename
'/usr/local/texlive/2013/texmf-dist/fonts/opentype/public/lm/lmroman12-regular.otf',
hscale 786.432
the content to the given width.
You can get the same effect with the \scale command, another way is to
change the font size for the verbatim block with
\typefile[bodyfont=small]{filename}
or \typefile[bodyfont=8pt]{filename}.
Wolfgang
'fallback modern rm 12pt' is loaded
) ) )
system files start used files
used files 1: filename=cont-yes.mkiv filetype=tex
foundname=/usr/share/texmf/tex/context/base/cont-yes.mkiv usedmethod=otherwise
used files 2: filename=cont-new.mkiv filetype=tex
foundname=/usr
On Mon, 01 Jul 2013 10:54:11 +0200, Hans Hagen pra...@wxs.nl wrote:
you can add this to l-pdfview.lua (opencalls windows section):
['pdfxcview'] = [[start test pdfxcview.exe /A
nolock=yes=OpenParameters %filename%]],
if you have a texmfcnf.lua file in your local tree you can add
and tagging as mentioned,
following some logic, all kind of antykwa fonts suddenly could end op in
a pool of optical sizes but they are in fact all different in specific
properties. The same is true for more fonts. So what should one look at?
The filename: no universal system behind it. The font
/local/texlive/2012/texmf-dist/tex/context/base/lpdf-pdx.xml'
pagesflushing realpage 1, userpage 1
)/usr/local/texlive/2012/texmf-dist/fonts/truetype/public/ipaex/ipaexm.ttf
system files start used files
used files 1: filename=bullet-problem.tex |
foundname=bullet
/context/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf
system files start used files
used files 1: filename=cont-yes.mkiv filetype=tex
foundname=/home/christian/context/tex/texmf-context/tex/context/base/cont-yes.mkiv
usedmethod=database
used files 2: filename=cont
m_k_i_v_filename.svg.pdf file generated?
It might be informative to try running the Inkscape conversion
manually. This is the command line ConTeXT uses:
inkscape %oldname% --export-dpi=600 -A %newname%
(The quotation marks are literal: they are there in case the filename
has spaces, e.g
: they are there in case the filename
has spaces, e.g.)
If processing in Inkscape fails, you can try another tool:
http://xmlgraphics.apache.org/batik/tools/rasterizer.html
It can (despite its name) transcode SVG to vector PDF:
java -Xmx2G -jar batik-rasterizer.jar -m application/pdf image.svg
In that case you
%oldname% --export-dpi=600 -A %newname%
(The quotation marks are literal: they are there in case the filename
has spaces, e.g.)
If processing in Inkscape fails, you can try another tool:
http://xmlgraphics.apache.org/batik/tools/rasterizer.html
It can (despite its name) transcode SVG to vector
m_k_i_v_filename.svg.pdf file generated?
It might be informative to try running the Inkscape conversion
manually. This is the command line ConTeXT uses:
inkscape %oldname% --export-dpi=600 -A %newname%
(The quotation marks are literal: they are there in case the filename
has spaces, e.g.)
Good
m_k_i_v_filename.svg.pdf file generated?
It might be informative to try running the Inkscape conversion
manually. This is the command line ConTeXT uses:
inkscape %oldname% --export-dpi=600 -A %newname%
(The quotation marks are literal: they are there in case the filename
has spaces, e.g
own report.
Perhaps is can be understood what I want from my minimal example.
Thanx
Jaroslav Hajtmar
Minimal example:
\let\filename\null
\let\firstname\null
\let\surname\null
\let\city\null
\let\street\null
\let\postcode\null
\def\dosomething#1{#1\par}
\def\loadlistdatatomacros#1,#2,#3,#4,#5
On 5/1/2013 11:31 AM, Romain Diss wrote:
Hi,
I just noticed a small bug in the log of a context job. It has no incidence
but maybe this can cause a side effect somewhere.
When a file contain several dot in its name, context remove the last part in
the result filename in the log:
$ context
Thanks, Thomas. This is good to have for many purposes. But, for the task
of generating PDFs of components that are part of a larger product, the
problem of cross-references is but one of several issues—especially if one
wants ConTeXt to do most (if not all) of the work.
Alan
On Sun, May 5,
Wolfgang: OK—but a clarification. Yes, that will give me the individual
component files, but not with the page numbers etc that they would have
when they are compiled as part of the product. What I am interested in is
the extraction of component files during the compilation of a larger
product
On 05/05/2013 02:27 PM, Alan Bowen wrote:
Wolfgang: OK—but a clarification. Yes, that will give me the individual
component files, but not with the page numbers etc that they would have
when they are compiled as part of the product.
http://pragma-ade.com/general/magazines/mag-1103.pdf
HTH
Wolfgang—
Can this be extended so as to allow the extraction of the individual
component files (as PDFs with their component names) when processing a
product file?
Alan
On Thu, May 2, 2013 at 2:44 AM, Wolfgang Schuster
schuster.wolfg...@gmail.com wrote:
Am 01.05.2013 um 23:02 schrieb
Am 04.05.2013 um 13:50 schrieb Alan Bowen bowenala...@gmail.com:
Wolfgang—
Can this be extended so as to allow the extraction of the individual
component files (as PDFs with their component names) when processing a
product file?
There is no need for such a feature because you can
Am 01.05.2013 um 23:02 schrieb Wolfgang Schuster schuster.wolfg...@gmail.com:
Am 01.05.2013 um 12:16 schrieb Alan BRASLAU alan.bras...@cea.fr:
Hello,
In the production of (scientific) articles for journal submissions,
one is often expected to supply the figures as separate files.
Hi,
I just noticed a small bug in the log of a context job. It has no incidence
but maybe this can cause a side effect somewhere.
When a file contain several dot in its name, context remove the last part in
the result filename in the log:
$ context test.foo.bar
...
system files
Hello,
In the production of (scientific) articles for journal submissions,
one is often expected to supply the figures as separate files.
One workflow can be through the use of \startTEXpage\stopTEXpage
followed by an external extraction of single pdf pages to separate
files.
However, is it
Alan wrote:
In the production of (scientific) articles for
journal submissions, one is often expected to
supply the figures as separate files.
One workflow can be through the use of \startTEXpage\stopTEXpage
followed by an external extraction of single pdf pages to separate
files.
It might
Am 01.05.2013 um 12:16 schrieb Alan BRASLAU alan.bras...@cea.fr:
Hello,
In the production of (scientific) articles for journal submissions,
one is often expected to supply the figures as separate files.
One workflow can be through the use of \startTEXpage\stopTEXpage
followed by an
On Wed, 1 May 2013 16:16:07 +0200
Sietse Brouwer sbbrou...@gmail.com wrote:
Alan wrote:
In the production of (scientific) articles for
journal submissions, one is often expected to
supply the figures as separate files.
One workflow can be through the use of \startTEXpage\stopTEXpage
I'm sorry. I was pointing TEXMFLOCAL to the wrong (older) version of
fonts without OT in the filename.
However, the Type1 fonts still don't work.
Mojca
On Fri, Apr 19, 2013 at 1:31 PM, Mojca Miklavec wrote:
Hi,
in TL 2013 neither \setupbodyfont[lucida] nor \setupbodyfont[lucidanova]
works
On 4/19/2013 2:04 PM, Mojca Miklavec wrote:
I'm sorry. I was pointing TEXMFLOCAL to the wrong (older) version of
fonts without OT in the filename.
However, the Type1 fonts still don't work.
Did we change something with the type 1? In mkiv ... we probably never
finished the mappings ... waste
/opentype/public/lm-math/latinmodern-math.otf/home/maja/context/tex/texmf/fonts/opentype/public/lm-math/latinmodern-math.otf/home/maja/context/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf
system files start used files
used files 1: filename=cont-yes.mkiv filetype=tex
/context/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf
system files start used files
used files 1: filename=cont-yes.mkiv filetype=tex foundname=/home/maja/context/tex/texmf-context/tex/context/base/cont-yes.mkiv usedmethod=database
used files 2: filename=cont
-regular.otf
system files start used files
used files 1: filename=cont-yes.mkiv filetype=tex foundname=/home/maja/context/tex/texmf-context/tex/context/base/cont-yes.mkiv usedmethod=database
used files 2: filename=cont-new.mkiv filetype=tex foundname=/home/maja/context/tex/texmf
/tex/texmf-context/tex/context/base/lpdf-pdx.xml'
pagesflushing realpage 1, userpage 1
) )/home/context/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf
system files start used files
used files 1: filename=cont-yes.mkiv filetype=tex foundname=/home/context
/context/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf
system files start used files
used files 1: filename=cont-yes.mkiv filetype=tex foundname=/home/context/tex/texmf-context/tex/context/base/cont-yes.mkiv usedmethod=database
used files 2: filename=cont
flushing realpage 1, userpage 1
) )/home/context/tex/texmf/fonts/opentype/public/lm-math/latinmodern-math.otf/home/context/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf
system files start used files
used files 1: filename=cont-yes.mkiv | filetype=tex
as a simple filename
without any filename extensions or pathnames.
Avoid hard coded path names in your files, it makes them less
portable. ConTeXt adds the file name extension automatically,
there's usually no need to specify it manually.
IMHO, I would disagree. That is, using hardcoded full paths
On 2013–03–08 hwit...@gmail.com wrote:
I am just learning ConTeXt, so please bare with me. In all of the
documentation that I've read so far, it shows the names of
imported photographs, graphs, blocks, etc as a simple filename
without any filename extensions or pathnames.
Avoid hard coded
I am just learning ConTeXt, so please bare with me. In all of the
documentation that I've read so far, it shows the names of imported
photographs, graphs, blocks, etc as a simple filename without any filename
extensions or pathnames.
Having a bunch of photographs anc charts files
produces a error message
and asks
for a valid filename while \environment mentions an not existent file but
doesn’t interrupt
the compile process.
Wolfgang
___
If your question is of interest to others as well, please add
uses MkII for
XeTeX and that MkII it is frozen, but nothing prevents you from using
XeTeX with ConTeXt. Any of the following commands should work:
texexec --xtx filename[.tex]
texexec --xetex filename[.tex]
context --xetex filename[.tex]
Mojca
, but nothing prevents you from using
XeTeX with ConTeXt. Any of the following commands should work:
texexec --xtx filename[.tex]
texexec --xetex filename[.tex]
context --xetex filename[.tex]
Mojca
/tex/texmf/fonts/opentype/public/lm/lmroman8-regular.otf/Applications/ConTeXt/tex/texmf/fonts/opentype/public/lm/lmmono12-regular.otf/Applications/ConTeXt/tex/texmf/fonts/opentype/public/lm/lmroman12-regular.otf
system files start used files
used files 1: filename=cont-yes.mkiv
whitespace etc. Isn;t there a true verbatim that I can use on
a macro like \currentcomponent? Something along the lines of
\verbatimexpand{\currentcomponent}?
Untested: \filename{\currentcomponent}
Works. When outside a component (e.g. index) it defaults to the string 'text'.
Thanks,
G
Simple question, guys (and gals),
how do I get the filename (full path not needed) in the footer of my document?
I want it there while writing the book and remove it in the final stages. I am
using MKII (TeXLive 2011 still)
texexec --pdf --mode=editor --once ../products/prd_book.tex
TeXExec
Hi Gerben,
···date: 2013-01-20, Sunday···from: Gerben Wierda···
how do I get the filename (full path not needed) in the footer
of my document? I want it there while writing the book and remove
it in the final stages. I am using MKII (TeXLive 2011 still)
if the name of the main file suffices
On 20 Jan 2013, at 12:57, Philipp Gesang wrote:
Hi Gerben,
···date: 2013-01-20, Sunday···from: Gerben Wierda···
how do I get the filename (full path not needed) in the footer
of my document? I want it there while writing the book and remove
it in the final stages. I am using MKII
···date: 2013-01-20, Sunday···from: Gerben Wierda···
On 20 Jan 2013, at 12:57, Philipp Gesang wrote:
Hi Gerben,
···date: 2013-01-20, Sunday···from: Gerben Wierda···
how do I get the filename (full path not needed) in the footer
of my document? I want it there while writing
On 20 Jan 2013, at 16:09, Philipp Gesang wrote:
···date: 2013-01-20, Sunday···from: Gerben Wierda···
On 20 Jan 2013, at 12:57, Philipp Gesang wrote:
Hi Gerben,
···date: 2013-01-20, Sunday···from: Gerben Wierda···
how do I get the filename (full path not needed) in the footer
of my
···
how do I get the filename (full path not needed) in the footer
of my document? I want it there while writing the book and remove
it in the final stages. I am using MKII (TeXLive 2011 still)
if the name of the main file suffices, then the TeX command
\jobname is what you are looking
,
···date: 2013-01-20, Sunday···from: Gerben Wierda···
how do I get the filename (full path not needed) in the footer
of my document? I want it there while writing the book and remove
it in the final stages. I am using MKII (TeXLive 2011 still)
if the name of the main file suffices
on a macro like \currentcomponent? Something along the lines of
\verbatimexpand{\currentcomponent}?
Untested: \filename{\currentcomponent}
Aditya
___
If your question is of interest to others as well, please add
:08.292726460 +0100
@@ -335,8 +335,8 @@
local lucname, luaname, chunk
local basename = file.removesuffix(filename)
if basename == filename then
-luaname = fiule.addsuffix(basename,luasuffixes.lua)
-lucname = fiule.addsuffix(basename,luasuffixes.luc)
+luaname
Am 31.12.2012 um 19:02 schrieb Hans Hagen pra...@wxs.nl:
On 12/29/2012 6:29 PM, Wolfgang Schuster wrote:
Hi Hans,
can you add a \savebuffer variant which works like the first version of the
command where
\savebuffer[buffername][filename]
saved the buffer as filename
On 1/2/2013 9:15 AM, Wolfgang Schuster wrote:
Which file extension would this use, “tmp” as the current \savebuffer command
or a requested with is applied with the filename (e.g. “file=myfile.tex”) or a
extension key (e.g. “extension=tex”).
with prefix=no it uses the given filename (so
Which file extension would this use, “tmp” as the current \savebuffer
command or a requested with is applied with the filename (e.g.
“file=myfile.tex”) or a extension key (e.g. “extension=tex”).
with prefix=no it uses the given filename (so no suffix if not given)
`prefix=no` doesn't really
On 12/29/2012 6:29 PM, Wolfgang Schuster wrote:
Hi Hans,
can you add a \savebuffer variant which works like the first version of the
command where
\savebuffer[buffername][filename]
saved the buffer as filename and not as \jobname-filename.tmp like it
currently does.
Instead of a new
On Sun, Dec 23, 2012 at 02:50:06PM +0100, Hans Hagen wrote:
On 12/23/2012 7:29 AM, Khaled Hosny wrote:
Hi all,
Some people have been complaining that it is not possible to use XeTeX
with filenames containing parenthesis because XeTeX treats it as
filename quote char and this it gets
Hi Hans,
can you add a \savebuffer variant which works like the first version of the
command where
\savebuffer[buffername][filename]
saved the buffer as filename and not as \jobname-filename.tmp like it
currently does.
Instead of a new command a key-val-version of \savebuffer would do
On 12/23/2012 7:29 AM, Khaled Hosny wrote:
Hi all,
Some people have been complaining that it is not possible to use XeTeX
with filenames containing parenthesis because XeTeX treats it as
filename quote char and this it gets stripped. Anyway, after some
searching it turned out this was added
Hi all,
Some people have been complaining that it is not possible to use XeTeX
with filenames containing parenthesis because XeTeX treats it as
filename quote char and this it gets stripped. Anyway, after some
searching it turned out this was added in 2004 for ConTeXt to workaround
some MetaPost
moving all the images that are in the document from multiple directories
into one directory.
There has been some cleanup of filename constructors but nor that
drastic. Maybe some are (temporary) More sensitive so nil arguments but
that is then an indication of some issue earlier in the chain
. There is actually an \xmlinclude command
\xmlinclude{main}{include}{filename|href|name}
this will include from elements with tags 'include' and one of the attributes
mentioned. Do this as one of the first steps as it merges xml trees.
Hans
Hi Hans,
thanks for your suggestion. Yes, I mean combining
projects here. There is actually an \xmlinclude command
\xmlinclude{main}{include}{filename|href|name}
this will include from elements with tags 'include' and one of the
attributes mentioned. Do this as one of the first steps as it merges xml
trees.
Hans
{main}{include}{filename|href|name}
this will include from elements with tags 'include' and one of the attributes
mentioned. Do this as one of the first steps as it merges xml trees.
Hans
Hi Hans,
thanks for your suggestion. Yes, I mean combining multiple files into one
document. Sorry
...@wxs.nl wrote:
Using xml sounds ok to me (esp as you know how to do it) ... with xinclude
you mean combining multiple files into one? It's what we do in all xml
related projects here. There is actually an \xmlinclude command
\xmlinclude{main}{include}{filename|href|name
been rewritten. This error indicates a
problem elsewhere (i can intercept the nil btw) like an empty filename
or so.
Hans
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH
the math font is not set, due to a filename error. Apply
the change below, and math will compile again.
% type-imp-latinmodern.mkiv
\starttypescript [\s!math] [modern,latin-modern]
\loadfontgoodies[lm]
-\definefontsynonym [LMMathRoman-Regular]
[\v!file:lmodernmath-regular.otf
, but the viewer
(acroread) is not rendering the movie.
Your example works on my Mac with Adobe Reader 10.1.4, with one of my own .mov
files substituted. The pdf code is the same, except with a different filename.
This e-mail message (including any attachments
the right annotation, but the viewer
(acroread) is not rendering the movie.
Your example works on my Mac with Adobe Reader 10.1.4, with one of my own .mov
files substituted. The pdf code is the same, except with a different filename.
Thanks for checking. This means that it is a viewer issue
Hi Kip,
I had the same problem. This is the advice I got (in an unrelated
off-list e-mail):
Sietse wrote:
! Math error: parameter \Umathquad\displaystyle is not set.
Aditya wrote:
That usually means that the math font is not set.
And indeed the math font is not set, due to a filename error
, userpage 1
) )/usr/share/fonts/ousia-fonts/FreeSerif.ttf
system files start used files
used files 1: filename=cont-yes.mkiv | filetype=tex | foundname=/opt/ctxbeta/tex/texmf-context/tex/context/base/cont-yes.mkiv | usedmethod=database
used files 2: filename=cont-new.mkiv
Am 26.11.2012 um 21:42 schrieb Erik Margraf erik.marg...@gmail.com:
Dear List,
is there a Context function/macro which enables me to set
a box with verbatim file input. I.e. something
similar to :
\setbox\scratchbox\hbox{\verbatimfileinput{FileName}}
You have to use a \vbox because
(parent dir): works
Absolute path (non-parent dir): works
Absolute path (filename has no extension): fails
== Hans ==
Version: ??? on Linux
Absolute path (parent dir): works
Absolute path (non-parent dir): /??
== Sietse ==
Version: 2012.11.08 on Linux
[system.outputmode]= restricted
only the annotation module you have to install it with
first-setup --modules=t-annotation (note the t-prefix), you can also install
all available modules with first-setup --modules=all.
2. The module is MkIV only, to use MkIV process your document with “context
filename”.
Wolfgang
of defining something, what I
have to change to compile with the last context version?
You process your document with MkIV (texexec filename or context --pdftex
filename) but your document requires MkIV (context filename) because you
use the command \definehightlight which is only available with MkIV
Am 18.11.2012 14:45, schrieb ntg-context-requ...@ntg.nl:
You process your document with MkIV (texexec filename or context --pdftex
filename) but your document requires MkIV (context filename) because you use the
command \definehightlight which is only available with MkIV.
Wolfgang
Thanks
(Sorry, wrong email title)
Am 18.11.2012 14:45, schrieb ntg-context-requ...@ntg.nl:
You process your document with MkIV (texexec filename or context
--pdftex filename) but your document requires MkIV (context
filename) because you use the command \definehightlight which is
only available
file is
not created anymore and this lead to a missing section number (for the
first section only). How can I remedy to that ? Any idea ?
Use “context --arrange filename”.
Thank you, it seems trivial but it works well.
Do the use of \setuparranging should always be accompanied by context --
arrange
). How can I remedy to that ? Any idea ?
Use “context --arrange filename”.
Thank you, it seems trivial but it works well.
Do the use of \setuparranging should always be accompanied by context --
arrange filename or are there specific cases?
--
Romain Diss
romain.d...@yahoo.fr
to a missing section number (for the
first section only). How can I remedy to that ? Any idea ?
Use “context --arrange filename”.
Thank you, it seems trivial but it works well.
Do the use of \setuparranging should always be accompanied by context --
arrange filename or are there specific cases?
I
)
if not loaded[tag] then
loaded[tag] = 0
local filename = kpse.find_file(lang- .. tag .. .lua)
if filename and filename == then
print(unknown language file for: .. tag .. )
else
local whatever = loadfile(filename)
if type(whatever
example :
%%
\setuppapersize[A5][A4,landscape]
\setuparranging[2SIDE]
\starttext
\dorecurse{10}{
\section{Knuth}
\input knuth}
\stoptext
%%
If one comment the \setuparranging[2SIDE] line, everything is ok.
Use “context --arrange filename”.
Wolfgang
That is default. I deleted the .synctex.gz files manually, but it did
not help. What could be the problem?
if you get a synctex.gz file then the problem is with texworks
The are no changes in the way context produces the filename paths?
Synctex is a bit fragile when it comes to filenames within
(MkII, MkIV and MkVI) and MetaPost files use
context --ctx=s-mod filename
and for Lua files (currently broken but should be fixed in one of the next
betas) use
context --ctx=x-dx filename
Wolfgang
___
If your
the filename field at the very
beginning. As I cannot change the filename anymore, I ask a
modules-db admin to change it from -0.9.zip to
t-crossref-0.9.zip - thanks! :-S
http://wiki.contextgarden.net/Cross_Referencing
@Sieste and Wolfgang
I removed move my wrong
the filename field at the very
beginning. As I cannot change the filename anymore, I ask a
modules-db admin to change it from -0.9.zip to
t-crossref-0.9.zip - thanks! :-S
http://wiki.contextgarden.net/Cross_Referencing
@Sieste and Wolfgang
I removed move my wrong
waiting. So, it looks like we need to
use filename 21 instead of filename.
I checked the scripts in the context tree and so far found no occurences
but first-setup.sh has two 's in it that might need fixing.
Hans
On 10/30/2012 01:20 PM, Hans Hagen wrote:
filename 21
This has been the correct Bourne shell (POSIX) syntax for many years. I
think it goes all the way back to Bell Labs V7 IIRC
instead of filename.
is a bash-ism
I checked the scripts in the context tree and so far found
On Tue 30 Oct 2012, Bill Meahan wrote:
On 10/30/2012 01:20 PM, Hans Hagen wrote:
filename 21
This has been the correct Bourne shell (POSIX) syntax for many
years. I think it goes all the way back to Bell Labs V7 IIRC
instead of filename.
is a bash-ism
FWIW, Debian and Ubuntu have
601 - 700 of 1623 matches
Mail list logo
