nd I would like to know which lines to add to the
end of files.
context filename
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53
gt; xmp > using file
'/usr/local/texlive/2013/texmf-dist/tex/context/base/lpdf-pdx.xml'
pages > flushing realpage 1, userpage 1
structure > sectioning > chapter @ level 2 : 0.1 -> \xmlfirst
{demo::5}{/title}
)
system > invalid \starttext ... \sto
loaded yet, using 'lm mono' in box
backend > xmp > using file
'/usr/local/texlive/2013/texmf-dist/tex/context/base/lpdf-pdx.xml'
pages > flushing realpage 1, userpage 1
structure > sectioning > chapter @ level 2 : 0.1 -> \xmlfirst
{demo::5}{/title}
)
1, userpage 1
)
)
system > structure > start used structure
used structure > text: test3
system > structure > stop used structure
system > files > start used files
used file > 1: filename=cont-yes.mkiv filetype=tex
foundname=/home/sa
ng objects
3) 'properties' and 'methods' for every particular 'class'
I've roughly scanned the ConTeXt source structure and bringing the following
idea:
1) There is no 'packages' counterpart in ConTeXt, but it would be handy to
think of any logical structure
s' for every particular 'class'
I've roughly scanned the ConTeXt source structure and bringing the following
idea:
1) There is no 'packages' counterpart in ConTeXt, but it would be handy to
think of any logical structure to group commands to logical groups (even
nest
been written.
we can do this (line 308 of lpdf-wid)
if author == "" and title ~= "" then
author = title
title = filename or ""
end
but you can also add an author field to the specification as what shows
up in the pdf is partly the side eff
ocal otf = fonts.handlers.otf
local patches = otf.enhancers.patches
local register = patches.register
local report = patches.report
function patch (data,filename)
report("I am here")
report("processing data %s", table.serialize(data))
end
register("after&quo
l patches = otf.enhancers.patches
local register = patches.register
local report = patches.report
function patch (data,filename)
report("I am here")
report("processing data %s", table.serialize(data))
end
register("after",
.
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 he
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
:-)
Adi
rsion of context,
> context-beta and context-stable. Then, download 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
amp; 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-stable/tex/setptex && context filename
to compile a fi
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 thi
pdf
> > automatically. It is really very helpful!
> >
> > 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 doc
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 te
pt 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"
For more complicated documents (depending on multip
zadeRegOT.ttf
> scheherazadenormal scheherazade
> /home/marco/.fonts/scheherazade/ScheherazadeRegOT.ttf
>
> This might be related to the thread from a few days ago:
>
> http://thread.gmane.org/gmane.comp.tex.context/83871/focus=83877
>
> Marco
>
>
> PS: The font
http://thread.gmane.org/gmane.comp.tex.context/83871/focus=83877
Marco
PS: The font can be found here:
http://scripts.sil.org/cms/scripts/render_download.php?format=file&media_id=Scheherazade-2.000&fi
at actually 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
ght 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!
mail
ding from cache using hash
'lmroman12-regular'
fonts > otf loading > apply enhancement 'unpack' to file
'/usr/local/texlive/2013/texmf-dist/fonts/opentype/public/lm/lmroman12-regular.otf'
fonts > otf loading > apply enhancement &#x
> preloading latin modern fonts (second stage)
fonts > typescripts > unknown library 'loc'
{/usr/share/texmf/fonts/map/dvips/lm/lm-math.map}{/usr/share/texmf/fonts/map/dvips/lm/lm-rm.map}
fonts > 'fallback modern rm 12pt' is loaded
On Mon, 01 Jul 2013 10:54:11 +0200, Hans Hagen 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.l
= [[start "test" pdfxcview.exe /A
"nolock=yes=OpenParameters" "%filename%"]],
if you have a texmfcnf.lua file in your local tree you can ass a
directive there, otherwise you can make such a file with:
return {
type= "configuration",
content
look at some
properties, because of inconsistent naming 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 loo
\symb_place_indeed ...name \??symbol #1\endcsname
\relax \endgroup
\symb_place_retry ...name \symb_place_indeed {:#1}
\else #1\fi
\symb_place_normal_c ...lace_retry \currentsymbol
text/tex/texmf/fonts/map/dvips/lm/lm-math.map}{/home/christian/context/tex/texmf/fonts/map/dvips/lm/lm-rm.map}
fonts > 'fallback modern rm 12pt' is loaded
backend > xmp > using file
'/home/christian/context/tex/texmf-context/tex/context/base/lpdf-pdx.xml'
pages
corresponding
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
e 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
&
"%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 na
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
t;%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 PDF:
java -Xmx2
e. Is a corresponding
> 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 ar
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, 201
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
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
Tho
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 file
Am 04.05.2013 um 13:50 schrieb Alan Bowen :
> 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 process individual
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?
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 W
Am 01.05.2013 um 23:02 schrieb Wolfgang Schuster :
>
> Am 01.05.2013 um 12:16 schrieb Alan BRASLAU :
>
>> 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 us
On Wed, 1 May 2013 16:16:07 +0200
Sietse Brouwer 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
> > followe
Am 01.05.2013 um 12:16 schrieb Alan BRASLAU :
> 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 extracti
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
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 poss
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 > fi
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
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 \setup
> '5' placed
floatblocks > '6' placed
floatblocks > '7' placed
floatblocks > '8' placed
backend > xmp > using file '/home/maja/context/tex/texmf-context/tex/context/base/lpdf-pdx.xml'
pages >
/tex/context/base/lpdf-pdx.xml'
pages > flushing realpage 1, userpage 1
) )
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
/tex/texmf/fonts/map/dvips/lm/lm-rm.map}
fonts > 'fallback modern rm 12pt' is loaded
backend > xmp > using file '/home/maja/context/tex/texmf-context/tex/context/base/lpdf-pdx.xml'
pages > flushing realpage 1, userpage 1
) )
system &
tex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/otf/latinmodern-math.tma'
fonts > 'fallback modern rm 12pt' is loaded
backend > xmp > using file '/home/context/tex/texmf-context/tex/context/base/lpdf-pdx.xml'
pages > fl
ern-math.tma'
fonts > fallback modern rm 12pt is loaded
backend > xmp > using file '/home/context/tex/texmf-context/tex/context/base/lpdf-pdx.xml'
pages > flushing realpage 1, userpage 1
) )
system > files > start used files
used fil
les
backend > xmp > using file '/home/context/tex/texmf-context/tex/context/base/lpdf-pdx.xml'
pages > flushing realpage 1, userpage 1
) )
system > files > start used files
used files >1: filename=cont-yes.mkiv | filetype=tex | found
Hi All,
Am 08.03.2013 um 09:02 schrieb Marco Patzer :
> 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, blo
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 pathn
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 i
essage
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 an entry
e that ConTeXt 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]
>
>
t is indeed true that ConTeXt 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]
con
0
..\localbrokenpenalty=0
..\localleftbox=null
..\localrightbox=null
.\hbox(10.42677+4.05482)x0.0, direction TLT
.\3>modern-designsize-12pt-tt-tf-0--0 $
.\glue 6.18
.\3>modern-designsize-12pt-tt-tf-0--0 g
.etc.
backend > xmp > using file
'/Applications/ConTeXt/tex/texmf-
antly, that catches ^ and _,
>> but what about 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 outs
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 an
>
>>>>> Hi Gerben,
>>>>>
>>>>> ·
>>>>>
>>>>>> 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
>>
Am 20.01.2013 um 18:06 schrieb Gerben Wierda :
> On 20 Jan 2013, at 16:09, Philipp Gesang wrote:
>
>> ·
>>
>>> On 20 Jan 2013, at 12:57, Philipp Gesang wrote:
>>>
>>>> Hi Gerben,
>>>>
>>>> ·
>>>
On 20 Jan 2013, at 16:09, Philipp Gesang wrote:
> ·
>
>> On 20 Jan 2013, at 12:57, Philipp Gesang wrote:
>>
>>> Hi Gerben,
>>>
>>> ·
>>>
>>>> how do I get the filename (full path not needed) in the footer
>
·
> On 20 Jan 2013, at 12:57, Philipp Gesang wrote:
>
> > Hi Gerben,
> >
> > ·
> >
> >> 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
>
On 20 Jan 2013, at 12:57, Philipp Gesang wrote:
> Hi Gerben,
>
> ·
>
>> 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 2
Hi Gerben,
·
> 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
\jobnam
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
: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
>> 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 suffi
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 no
milar.
>
> next beta:
>
> \starttext
>
> \startbuffer[test]
> crap
> \stopbuffer
>
> \savebuffer[test][whatever]
>
> \savebuffer[list=test,file=something,prefix=no]
>
> \stoptext
Which file extension would this use, “tmp” as the current \
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
> &g
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 in
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
error. Nor did
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
ly 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
at 2:46 PM, Hans Hagen 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}
>
> 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 mu
ml related 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 merge
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 | 8
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
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, du
Xt appears to be including 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 mean
.692913385827 56.692913385827 ] /F
> (clip.mov) >>
> /Rect [70.867 657.6468 127.5599 714.3397]
>>>
>
> so, ConTeXt appears to be including the right annotation, but the viewer
> (acroread) is not rendering the movie.
Your example works on my Mac with Adobe Reader 10
ize > enabled
(/opt/ctxbeta/tex/texmf-context/tex/context/sample/ward.tex)
backend > xmp > using file '/opt/ctxbeta/tex/texmf-context/tex/context/base/lpdf-pdx.xml'
pages > flushing realpage 1, userpage 1
) )
system > files > start used
Am 26.11.2012 um 21:42 schrieb Erik Margraf :
> 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 beca
t;system.inputmode"] = "any",
Absolute path (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 =
loaded = { }
function languages.loadpatterns(tag)
if not loaded[tag] then
loaded[tag] = 0
local filename = kpse.find_file("lang-" .. tag .. ".lua")
if filename and filename == "" then
print("")
else
$fullname
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
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
On 30-10-2012 18:38, Pontus Lurcock wrote:
On Tue 30 Oct 2012, Bill Meahan wrote:
On 10/30/2012 01:20 PM, Hans Hagen wrote:
filename 2>&1
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 &>
On 30-10-2012 18:38, Pontus Lurcock wrote:
On Tue 30 Oct 2012, Bill Meahan wrote:
On 10/30/2012 01:20 PM, Hans Hagen wrote:
filename 2>&1
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 &>
On 30-10-2012 18:38, Pontus Lurcock wrote:
On Tue 30 Oct 2012, Bill Meahan wrote:
On 10/30/2012 01:20 PM, Hans Hagen wrote:
filename 2>&1
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 &>
On 30-10-2012 18:26, Bill Meahan wrote:
On 10/30/2012 01:20 PM, Hans Hagen wrote:
>filename 2>&1
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"
On Tue 30 Oct 2012, Bill Meahan wrote:
> On 10/30/2012 01:20 PM, Hans Hagen wrote:
> > >filename 2>&1
>
> 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 &>
On 10/30/2012 01:20 PM, Hans Hagen wrote:
>filename 2>&1
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 conte
601 - 700 of 1663 matches
Mail list logo
