On 10/1/12 12:15 AM, Yihui Xie wrote:
> If you are using the German translation of the GUI, you can set the
> interface language option to be Default in the preferences. Otherwise
> you have to wait for LyX 2.0.5 for the bug fix.
>
My interpretation was wrong then. I thought the workaround was
Aliabbas Petiwala wrote:
Thanks Jurgen, it solved the problem by installing charter font which was
not installed, but after importing coling2012.tex as shown below, i am
getting errors(i have commented line :%\usepackage[utf8]{inputenc}):
! Package inputenc Error: Keyboard character used
Thanks Jurgen after following your steps, now another error crops up:
LaTeX Font Info: Font shape `MDA/mdbch/m/n' will be
(Font) scaled to size 4.80003pt on input line 84.
LaTeX Font Info: Font shape `MDB/mdbch/m/n' will be
(Font) scaled to size 4.80003pt on input line 84.
! Package inputenc
Aliabbas Petiwala wrote:
Thanks Jurgen after following your steps, now another error crops up:
LaTeX Font Info: Font shape `MDA/mdbch/m/n' will be
(Font) scaled to size 4.80003pt on input line 84.
LaTeX Font Info: Font shape `MDB/mdbch/m/n' will be
(Font) scaled to size 4.80003pt
I am getting the error in using the coling 2012 sty files at
http://coling2012-iitb.org/doc/coling-latex.zip copying in the relevant
miktex folder)
On Mon, Oct 1, 2012 at 2:21 PM, Jürgen Spitzmüller sp...@lyx.org wrote:
Aliabbas Petiwala wrote:
Thanks Jurgen after following your steps, now
Aliabbas Petiwala wrote:
I am getting the error in using the coling 2012 sty files at
http://coling2012-iitb.org/doc/coling-latex.zip copying in the relevant
miktex folder)
If you do not provide a minimal example file, I cannot help you further. (The
coling2000.sty file itself looks innocent
what i did is just import the coling tex file from that zip folder in lyx
and i am getting those errors.Ya all the problems are in the tex file
On Mon, Oct 1, 2012 at 5:16 PM, Jürgen Spitzmüller sp...@lyx.org wrote:
Aliabbas Petiwala wrote:
I am getting the error in using the coling 2012 sty
Aliabbas Petiwala wrote:
what i did is just import the coling tex file from that zip folder in lyx
and i am getting those errors.Ya all the problems are in the tex file
Then post this LyX file please, and also all the sty and TeX files. I'm
willing to help, but I do not want to first download
the error.
HTH
Jürgen
on the inputenc call in order to
determine the encoding of the latex file. If this line is missing, tex2lyx
assumes the encoding is latin1. This happens in your case. The file,
however,
is encoded in utf8, and thus some glyphs are imported wrongly, which
triggers
the error.
HTH
Jürgen
Aliabbas Petiwala wrote:
wont it be possible to change the converter to not assume things and detect
the encoding from the doc itself?
I'm not very familiar with the tex2lyx internals, but I fear it's not easy to
do that (this has already been considered).
Jürgen
On 10/1/12 12:15 AM, Yihui Xie wrote:
Wonderful. That is the root of the problem. The locale should not be C.
This bug has been biting us: http://www.lyx.org/trac/ticket/7741
If you are using the German translation of the GUI, you can set the
interface language option to be Default in the
Le 01/10/12 21:37, Michael Bach a écrit :
On 10/1/12 12:15 AM, Yihui Xie wrote:
I am using an American locale and GUI, so interface language default
does not work.
What do you mean exactly? Is it just that the US GUI is not convenient
to you? You do not need the German UI to input German
That is something confused me as well. Here is a screenshot of what I
was talking about: http://i.imgur.com/vkLhP.png It only sets the
language of the GUI and will not affect the document itself.
Regards,
Yihui
--
Yihui Xie xieyi...@gmail.com
Phone: 515-294-2465 Web: http://yihui.name
Department
Aliabbas Petiwala wrote:
Thanks Jurgen, it solved the problem by installing charter font which was
not installed, but after importing coling2012.tex as shown below, i am
getting errors(i have commented line :%\usepackage[utf8]{inputenc}):
! Package inputenc Error: Keyboard character used
Thanks Jurgen after following your steps, now another error crops up:
LaTeX Font Info: Font shape `MDA/mdbch/m/n' will be
(Font) scaled to size 4.80003pt on input line 84.
LaTeX Font Info: Font shape `MDB/mdbch/m/n' will be
(Font) scaled to size 4.80003pt on input line 84.
! Package inputenc
Aliabbas Petiwala wrote:
Thanks Jurgen after following your steps, now another error crops up:
LaTeX Font Info: Font shape `MDA/mdbch/m/n' will be
(Font) scaled to size 4.80003pt on input line 84.
LaTeX Font Info: Font shape `MDB/mdbch/m/n' will be
(Font) scaled to size 4.80003pt
I am getting the error in using the coling 2012 sty files at
http://coling2012-iitb.org/doc/coling-latex.zip copying in the relevant
miktex folder)
On Mon, Oct 1, 2012 at 2:21 PM, Jürgen Spitzmüller sp...@lyx.org wrote:
Aliabbas Petiwala wrote:
Thanks Jurgen after following your steps, now
Aliabbas Petiwala wrote:
I am getting the error in using the coling 2012 sty files at
http://coling2012-iitb.org/doc/coling-latex.zip copying in the relevant
miktex folder)
If you do not provide a minimal example file, I cannot help you further. (The
coling2000.sty file itself looks innocent
what i did is just import the coling tex file from that zip folder in lyx
and i am getting those errors.Ya all the problems are in the tex file
On Mon, Oct 1, 2012 at 5:16 PM, Jürgen Spitzmüller sp...@lyx.org wrote:
Aliabbas Petiwala wrote:
I am getting the error in using the coling 2012 sty
Aliabbas Petiwala wrote:
what i did is just import the coling tex file from that zip folder in lyx
and i am getting those errors.Ya all the problems are in the tex file
Then post this LyX file please, and also all the sty and TeX files. I'm
willing to help, but I do not want to first download
the error.
HTH
Jürgen
on the inputenc call in order to
determine the encoding of the latex file. If this line is missing, tex2lyx
assumes the encoding is latin1. This happens in your case. The file,
however,
is encoded in utf8, and thus some glyphs are imported wrongly, which
triggers
the error.
HTH
Jürgen
Aliabbas Petiwala wrote:
wont it be possible to change the converter to not assume things and detect
the encoding from the doc itself?
I'm not very familiar with the tex2lyx internals, but I fear it's not easy to
do that (this has already been considered).
Jürgen
On 10/1/12 12:15 AM, Yihui Xie wrote:
Wonderful. That is the root of the problem. The locale should not be C.
This bug has been biting us: http://www.lyx.org/trac/ticket/7741
If you are using the German translation of the GUI, you can set the
interface language option to be Default in the
Le 01/10/12 21:37, Michael Bach a écrit :
On 10/1/12 12:15 AM, Yihui Xie wrote:
I am using an American locale and GUI, so interface language default
does not work.
What do you mean exactly? Is it just that the US GUI is not convenient
to you? You do not need the German UI to input German
That is something confused me as well. Here is a screenshot of what I
was talking about: http://i.imgur.com/vkLhP.png It only sets the
language of the GUI and will not affect the document itself.
Regards,
Yihui
--
Yihui Xie xieyi...@gmail.com
Phone: 515-294-2465 Web: http://yihui.name
Department
Aliabbas Petiwala wrote:
> Thanks Jurgen, it solved the problem by installing charter font which was
> not installed, but after importing coling2012.tex as shown below, i am
> getting errors(i have commented line :%\usepackage[utf8]{inputenc}):
> ! Package inputenc Error: Keyboard ch
Thanks Jurgen after following your steps, now another error crops up:
LaTeX Font Info: Font shape `MDA/mdbch/m/n' will be
(Font) scaled to size 4.80003pt on input line 84.
LaTeX Font Info: Font shape `MDB/mdbch/m/n' will be
(Font) scaled to size 4.80003pt on input line 84.
! Package inputenc
Aliabbas Petiwala wrote:
> Thanks Jurgen after following your steps, now another error crops up:
>
> LaTeX Font Info: Font shape `MDA/mdbch/m/n' will be
>
> (Font) scaled to size 4.80003pt on input line 84.
>
> LaTeX Font Info: Font shape `MDB/mdbch/m/n' will be
>
I am getting the error in using the coling 2012 sty files at
http://coling2012-iitb.org/doc/coling-latex.zip copying in the relevant
miktex folder)
On Mon, Oct 1, 2012 at 2:21 PM, Jürgen Spitzmüller <sp...@lyx.org> wrote:
> Aliabbas Petiwala wrote:
> > Thanks Jurgen after follo
Aliabbas Petiwala wrote:
> I am getting the error in using the coling 2012 sty files at
> http://coling2012-iitb.org/doc/coling-latex.zip copying in the relevant
> miktex folder)
If you do not provide a minimal example file, I cannot help you further. (The
coling2000.sty file its
what i did is just import the coling tex file from that zip folder in lyx
and i am getting those errors.Ya all the problems are in the tex file
On Mon, Oct 1, 2012 at 5:16 PM, Jürgen Spitzmüller <sp...@lyx.org> wrote:
> Aliabbas Petiwala wrote:
> > I am getting the error in using
Aliabbas Petiwala wrote:
> what i did is just import the coling tex file from that zip folder in lyx
> and i am getting those errors.Ya all the problems are in the tex file
Then post this LyX file please, and also all the sty and TeX files. I'm
willing to help, but I do not want to first
ers
the error.
HTH
Jürgen
blem.
>
> Explanation:
>
> tex2lyx, LyX's tex converter, relies on the inputenc call in order to
> determine the encoding of the latex file. If this line is missing, tex2lyx
> assumes the encoding is latin1. This happens in your case. The file,
> however,
> is encoded in utf8, an
Aliabbas Petiwala wrote:
> wont it be possible to change the converter to not assume things and detect
> the encoding from the doc itself?
I'm not very familiar with the tex2lyx internals, but I fear it's not easy to
do that (this has already been considered).
Jürgen
On 10/1/12 12:15 AM, Yihui Xie wrote:
Wonderful. That is the root of the problem. The locale should not be C.
This bug has been biting us: http://www.lyx.org/trac/ticket/7741
If you are using the German translation of the GUI, you can set the
interface language option to be Default in the
Le 01/10/12 21:37, Michael Bach a écrit :
On 10/1/12 12:15 AM, Yihui Xie wrote:
I am using an American locale and GUI, so interface language default
does not work.
What do you mean exactly? Is it just that the US GUI is not convenient
to you? You do not need the German UI to input German
That is something confused me as well. Here is a screenshot of what I
was talking about: http://i.imgur.com/vkLhP.png It only sets the
language of the GUI and will not affect the document itself.
Regards,
Yihui
--
Yihui Xie
Phone: 515-294-2465 Web: http://yihui.name
Aliabbas Petiwala wrote:
I am getting the following error in using the coling 2012 sty files
http://coling2012-iitb.org/doc/coling-latex.zip(copying in the relevant
miktex folder)
pdfTeX error: pdflatex (file bchr8a.pfb): cannot open Type 1 font file for
rea
You need to activate the map
.
Sorry about the confusion! The error occurs only on Mac OS X 10.8.2
Mountain Lion. The problem I think is related to the fact that I work on
the same code base from both Windows 7 and Mac OS X using a git
repository. To handle end-of-line characters differently, there is an
option in git
I found the error source, but have no clue for a fix yet. The resulting
.tex document after a LyX-caused knit() is cut off exactly at the first
occurrence of a German diacritic o, i.e. the character ö. This is also
in line with the fact that the knitr-minimal example runs fine since
State University
2215 Snedecor Hall, Ames, IA
On Sun, Sep 30, 2012 at 2:11 PM, Michael Bach pha...@gmail.com wrote:
I found the error source, but have no clue for a fix yet. The resulting .tex
document after a LyX-caused knit() is cut off exactly at the first
occurrence of a German diacritic o
On 9/30/12 10:51 PM, Yihui Xie wrote:
You can make a copy of that document, delete everything in it, and
only put a code chunk
=
sessionInfo()
@
there and compile it. Then show us the results from sessionInfo().
Good idea, it is as I suspected:
sessionInfo()
## R version 2.15.1
Wonderful. That is the root of the problem. The locale should not be C.
This bug has been biting us: http://www.lyx.org/trac/ticket/7741
If you are using the German translation of the GUI, you can set the
interface language option to be Default in the preferences. Otherwise
you have to wait for
THE SAME error:
!pdfTeX error: pdflatex (file bchr8a.pfb): cannot open Type 1 font file for
rea
i really cant figure out what to do and how to install this bchr8a?
Thanks
On Sun, Sep 30, 2012 at 2:34 PM, Jürgen Spitzmüller sp...@lyx.org wrote:
Aliabbas Petiwala wrote:
I am getting
Aliabbas Petiwala wrote:
BUT I GET THE SAME error:
!pdfTeX error: pdflatex (file bchr8a.pfb): cannot open Type 1 font file for
rea
i really cant figure out what to do and how to install this bchr8a?
Maybe the fonts themselves are not installed properly. Try to deinstall and
reinstall
Aliabbas Petiwala wrote:
I am getting the following error in using the coling 2012 sty files
http://coling2012-iitb.org/doc/coling-latex.zip(copying in the relevant
miktex folder)
pdfTeX error: pdflatex (file bchr8a.pfb): cannot open Type 1 font file for
rea
You need to activate the map
.
Sorry about the confusion! The error occurs only on Mac OS X 10.8.2
Mountain Lion. The problem I think is related to the fact that I work on
the same code base from both Windows 7 and Mac OS X using a git
repository. To handle end-of-line characters differently, there is an
option in git
I found the error source, but have no clue for a fix yet. The resulting
.tex document after a LyX-caused knit() is cut off exactly at the first
occurrence of a German diacritic o, i.e. the character ö. This is also
in line with the fact that the knitr-minimal example runs fine since
State University
2215 Snedecor Hall, Ames, IA
On Sun, Sep 30, 2012 at 2:11 PM, Michael Bach pha...@gmail.com wrote:
I found the error source, but have no clue for a fix yet. The resulting .tex
document after a LyX-caused knit() is cut off exactly at the first
occurrence of a German diacritic o
On 9/30/12 10:51 PM, Yihui Xie wrote:
You can make a copy of that document, delete everything in it, and
only put a code chunk
=
sessionInfo()
@
there and compile it. Then show us the results from sessionInfo().
Good idea, it is as I suspected:
sessionInfo()
## R version 2.15.1
Wonderful. That is the root of the problem. The locale should not be C.
This bug has been biting us: http://www.lyx.org/trac/ticket/7741
If you are using the German translation of the GUI, you can set the
interface language option to be Default in the preferences. Otherwise
you have to wait for
THE SAME error:
!pdfTeX error: pdflatex (file bchr8a.pfb): cannot open Type 1 font file for
rea
i really cant figure out what to do and how to install this bchr8a?
Thanks
On Sun, Sep 30, 2012 at 2:34 PM, Jürgen Spitzmüller sp...@lyx.org wrote:
Aliabbas Petiwala wrote:
I am getting
Aliabbas Petiwala wrote:
BUT I GET THE SAME error:
!pdfTeX error: pdflatex (file bchr8a.pfb): cannot open Type 1 font file for
rea
i really cant figure out what to do and how to install this bchr8a?
Maybe the fonts themselves are not installed properly. Try to deinstall and
reinstall
Aliabbas Petiwala wrote:
> I am getting the following error in using the coling 2012 sty files
> http://coling2012-iitb.org/doc/coling-latex.zip(copying in the relevant
> miktex folder)
>
> pdfTeX error: pdflatex (file bchr8a.pfb): cannot open Type 1 font file for
> rea
Yo
nts/..."
I think that is Mac OS, although in the first email it was Windows 7.
Sorry about the confusion! The error occurs only on Mac OS X 10.8.2
Mountain Lion. The problem I think is related to the fact that I work on
the same code base from both Windows 7 and Mac OS X
I found the error source, but have no clue for a fix yet. The resulting
.tex document after a LyX-caused knit() is cut off exactly at the first
occurrence of a German diacritic o, i.e. the character ö. This is also
in line with the fact that the knitr-minimal example runs fine since
ment of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA
On Sun, Sep 30, 2012 at 2:11 PM, Michael Bach <pha...@gmail.com> wrote:
> I found the error source, but have no clue for a fix yet. The resulting .tex
> document after a LyX-caused knit() is cut off exactly at the
On 9/30/12 10:51 PM, Yihui Xie wrote:
You can make a copy of that document, delete everything in it, and
only put a code chunk
<<>>=
sessionInfo()
@
there and compile it. Then show us the results from sessionInfo().
Good idea, it is as I suspected:
sessionInfo()
## R version 2.15.1
Wonderful. That is the root of the problem. The locale should not be C.
This bug has been biting us: http://www.lyx.org/trac/ticket/7741
If you are using the German translation of the GUI, you can set the
interface language option to be Default in the preferences. Otherwise
you have to wait for
THE SAME error:
!pdfTeX error: pdflatex (file bchr8a.pfb): cannot open Type 1 font file for
rea
i really cant figure out what to do and how to install this bchr8a?
Thanks
On Sun, Sep 30, 2012 at 2:34 PM, Jürgen Spitzmüller <sp...@lyx.org> wrote:
> Aliabbas Petiwala wrote:
> &g
Aliabbas Petiwala wrote:
> BUT I GET THE SAME error:
>
> !pdfTeX error: pdflatex (file bchr8a.pfb): cannot open Type 1 font file for
> rea
>
>
> i really cant figure out what to do and how to install this bchr8a?
Maybe the fonts themselves are not installed prope
produces a skryptum.tex
file that can be tex'ed correctly and contains the \Sepr{} parts. Also,
the .Rnw file is complete, i.e. not cut off like the .tex file.
So I guess the Rscript call messes things up? I tried the hint by Scott
on setting an error hook, but to no avail. How to debug further
Just a quick follow-up.
I gather from the log that R reads the file as UTF-8. I checked my System
$ locale
and the R
Sys.getlocale()
Both are correctly set up as en_US.UTF-8. Just to rule that one out(?)...
Does the knitr example file work? I forget how to get to example files on MacOS.
Mabye Yihui will have an idea of what's going on, but in the meantime
if you want to try something, you can try with the newest version of
LyX's knitr module that Yihui sent in a couple of days ago. To do
this, you
I think this indicated the problem in your log:
12:13:14.670: Warning in readLines(input, warn = FALSE) :
12:13:14.673: invalid input found on input connection 'skryptum.Rnw'
But without a reproducible example, I'm afraid I cannot do anything,
especially I do not have Mac OS to test with.
On Sat, Sep 29, 2012 at 5:34 PM, Yihui Xie x...@yihui.name wrote:
I think this indicated the problem in your log:
12:13:14.670: Warning in readLines(input, warn = FALSE) :
12:13:14.673: invalid input found on input connection 'skryptum.Rnw'
But without a reproducible example, I'm afraid I
He sent me the message log without cc'ing the list, and I saw
12:13:14.353: Rscript --verbose --no-save --no-restore
/Applications/LyX.app/Contents/Resources/scripts/lyxknitr.R
/var/folders/yx/tvnzczfx7c31c68jrddvlqgrgn/T/lyx_tmpdir.xJL523/lyx_tmpbuf3/skryptum.Rnw
On Sat, Sep 29, 2012 at 5:43 PM, Yihui Xie x...@yihui.name wrote:
He sent me the message log without cc'ing the list, and I saw
12:13:14.353: Rscript --verbose --no-save --no-restore
/Applications/LyX.app/Contents/Resources/scripts/lyxknitr.R
produces a skryptum.tex
file that can be tex'ed correctly and contains the \Sepr{} parts. Also,
the .Rnw file is complete, i.e. not cut off like the .tex file.
So I guess the Rscript call messes things up? I tried the hint by Scott
on setting an error hook, but to no avail. How to debug further
Just a quick follow-up.
I gather from the log that R reads the file as UTF-8. I checked my System
$ locale
and the R
Sys.getlocale()
Both are correctly set up as en_US.UTF-8. Just to rule that one out(?)...
Does the knitr example file work? I forget how to get to example files on MacOS.
Mabye Yihui will have an idea of what's going on, but in the meantime
if you want to try something, you can try with the newest version of
LyX's knitr module that Yihui sent in a couple of days ago. To do
this, you
I think this indicated the problem in your log:
12:13:14.670: Warning in readLines(input, warn = FALSE) :
12:13:14.673: invalid input found on input connection 'skryptum.Rnw'
But without a reproducible example, I'm afraid I cannot do anything,
especially I do not have Mac OS to test with.
On Sat, Sep 29, 2012 at 5:34 PM, Yihui Xie x...@yihui.name wrote:
I think this indicated the problem in your log:
12:13:14.670: Warning in readLines(input, warn = FALSE) :
12:13:14.673: invalid input found on input connection 'skryptum.Rnw'
But without a reproducible example, I'm afraid I
He sent me the message log without cc'ing the list, and I saw
12:13:14.353: Rscript --verbose --no-save --no-restore
/Applications/LyX.app/Contents/Resources/scripts/lyxknitr.R
/var/folders/yx/tvnzczfx7c31c68jrddvlqgrgn/T/lyx_tmpdir.xJL523/lyx_tmpbuf3/skryptum.Rnw
On Sat, Sep 29, 2012 at 5:43 PM, Yihui Xie x...@yihui.name wrote:
He sent me the message log without cc'ing the list, and I saw
12:13:14.353: Rscript --verbose --no-save --no-restore
/Applications/LyX.app/Contents/Resources/scripts/lyxknitr.R
") which produces a skryptum.tex
file that can be tex'ed correctly and contains the \Sepr{} parts. Also,
the .Rnw file is complete, i.e. not cut off like the .tex file.
So I guess the Rscript call messes things up? I tried the hint by Scott
on setting an error hook, but to no avail. How to
Just a quick follow-up.
I gather from the log that R reads the file as UTF-8. I checked my System
$ locale
and the R
> Sys.getlocale()
Both are correctly set up as en_US.UTF-8. Just to rule that one out(?)...
Does the knitr example file work? I forget how to get to example files on MacOS.
Mabye Yihui will have an idea of what's going on, but in the meantime
if you want to try something, you can try with the newest version of
LyX's knitr module that Yihui sent in a couple of days ago. To do
this, you
I think this indicated the problem in your log:
12:13:14.670: Warning in readLines(input, warn = FALSE) :
12:13:14.673: invalid input found on input connection 'skryptum.Rnw'
But without a reproducible example, I'm afraid I cannot do anything,
especially I do not have Mac OS to test with.
On Sat, Sep 29, 2012 at 5:34 PM, Yihui Xie wrote:
> I think this indicated the problem in your log:
>
> 12:13:14.670: Warning in readLines(input, warn = FALSE) :
> 12:13:14.673: invalid input found on input connection 'skryptum.Rnw'
>
> But without a reproducible example, I'm
He sent me the message log without cc'ing the list, and I saw
12:13:14.353: Rscript --verbose --no-save --no-restore
"/Applications/LyX.app/Contents/Resources/scripts/lyxknitr.R"
"/var/folders/yx/tvnzczfx7c31c68jrddvlqgrgn/T/lyx_tmpdir.xJL523/lyx_tmpbuf3/""skryptum.Rnw"
On Sat, Sep 29, 2012 at 5:43 PM, Yihui Xie wrote:
> He sent me the message log without cc'ing the list, and I saw
>
> 12:13:14.353: Rscript --verbose --no-save --no-restore
> "/Applications/LyX.app/Contents/Resources/scripts/lyxknitr.R"
>
Dear LyX Developers and Users,
I am using LyX 2.0.4 on Windows 7 with the knitr (Rnw) module. I successfully
compiled the knitr-minimal.lyx example file and moved on to the
knitr-manual.lyx. I then get an error message that Rscript failed.
Can someone give me a hint on how to get a debug log
On Wed, Sep 26, 2012 at 5:54 AM, Michael Bach pha...@gmail.com wrote:
Dear LyX Developers and Users,
I am using LyX 2.0.4 on Windows 7 with the knitr (Rnw) module. I successfully
compiled the knitr-minimal.lyx example file and moved on to the
knitr-manual.lyx. I then get an error message
Hi Scott,
Thanks for responses.
Look in the terminal output. It might give you the error.
I cannot find a terminal output view in LyX - checked all toolbars and View
menu.
You could alternatively do File Export R/S code and then run/debug
the resulting file in R.
I tried
of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA
On Wed, Sep 26, 2012 at 10:16 AM, Michael Bach pha...@gmail.com wrote:
Hi Scott,
Thanks for responses.
Look in the terminal output. It might give you the error.
I cannot find a terminal output view in LyX - checked all
be interested in setting an error hook (a command that
is run when an error occurs). Otherwise if your document exports fine
you might not realize that there could be an error (knitr will print
the error message to your latex document but it will appear to compile
just fine). For example,
knit_hooks$set
Dear LyX Developers and Users,
I am using LyX 2.0.4 on Windows 7 with the knitr (Rnw) module. I successfully
compiled the knitr-minimal.lyx example file and moved on to the
knitr-manual.lyx. I then get an error message that Rscript failed.
Can someone give me a hint on how to get a debug log
On Wed, Sep 26, 2012 at 5:54 AM, Michael Bach pha...@gmail.com wrote:
Dear LyX Developers and Users,
I am using LyX 2.0.4 on Windows 7 with the knitr (Rnw) module. I successfully
compiled the knitr-minimal.lyx example file and moved on to the
knitr-manual.lyx. I then get an error message
Hi Scott,
Thanks for responses.
Look in the terminal output. It might give you the error.
I cannot find a terminal output view in LyX - checked all toolbars and View
menu.
You could alternatively do File Export R/S code and then run/debug
the resulting file in R.
I tried
of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA
On Wed, Sep 26, 2012 at 10:16 AM, Michael Bach pha...@gmail.com wrote:
Hi Scott,
Thanks for responses.
Look in the terminal output. It might give you the error.
I cannot find a terminal output view in LyX - checked all
be interested in setting an error hook (a command that
is run when an error occurs). Otherwise if your document exports fine
you might not realize that there could be an error (knitr will print
the error message to your latex document but it will appear to compile
just fine). For example,
knit_hooks$set
Dear LyX Developers and Users,
I am using LyX 2.0.4 on Windows 7 with the knitr (Rnw) module. I successfully
compiled the knitr-minimal.lyx example file and moved on to the
knitr-manual.lyx. I then get an error message that Rscript failed.
Can someone give me a hint on how to get a debug log
On Wed, Sep 26, 2012 at 5:54 AM, Michael Bach <pha...@gmail.com> wrote:
> Dear LyX Developers and Users,
>
> I am using LyX 2.0.4 on Windows 7 with the knitr (Rnw) module. I successfully
> compiled the knitr-minimal.lyx example file and moved on to the
> knitr-manual.lyx
Hi Scott,
Thanks for responses.
> Look in the terminal output. It might give you the error.
>
I cannot find a terminal output view in LyX - checked all toolbars and View
menu.
> You could alternatively do File > Export > R/S code and then run/debug
> the resulting file
ihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA
On Wed, Sep 26, 2012 at 10:16 AM, Michael Bach <pha...@gmail.com> wrote:
> Hi Scott,
>
> Thanks for responses.
>
>> Look in the terminal output. It might give you the error.
>>
>
>
l,
You might also be interested in setting an error hook (a command that
is run when an error occurs). Otherwise if your document exports fine
you might not realize that there could be an error (knitr will print
the error message to your latex document but it will appear to compile
just
1401 - 1500 of 7214 matches
Mail list logo