Re: Sweave errors: more explicit?

2010-05-09 Thread M . Speiser
You might try starting LyX from a console/x-terminal-emulator. Under Unix/X11, you can see error messages in ~/.xsession-errors (for programs not started from an x-term... When I launch LyX from a terminal (mac os x), all LaTeX and R traces are visible within that same terminal! Thanks

Re: Sweave errors: more explicit?

2010-05-09 Thread [Ricardo Rodriguez] eBioTIC.
Hi! M. Speiser wrote: You might try starting LyX from a console/x-terminal-emulator. Under Unix/X11, you can see error messages in ~/.xsession-errors (for programs not started from an x-term... When I launch LyX from a terminal (mac os x), all LaTeX and R traces are visible within that

Re: Sweave errors: more explicit?

2010-05-09 Thread M . Speiser
You might try starting LyX from a console/x-terminal-emulator. Under Unix/X11, you can see error messages in ~/.xsession-errors (for programs not started from an x-term... When I launch LyX from a terminal (mac os x), all LaTeX and R traces are visible within that same terminal! Thanks

Re: Sweave errors: more explicit?

2010-05-09 Thread [Ricardo Rodriguez] eBioTIC.
Hi! M. Speiser wrote: You might try starting LyX from a console/x-terminal-emulator. Under Unix/X11, you can see error messages in ~/.xsession-errors (for programs not started from an x-term... When I launch LyX from a terminal (mac os x), all LaTeX and R traces are visible within that

Re: Sweave errors: more explicit?

2010-05-09 Thread M . Speiser
> > You might try starting LyX from a console/x-terminal-emulator. > > Under Unix/X11, you can see error messages in ~/.xsession-errors (for > programs not started from an x-term... When I launch LyX from a terminal (mac os x), all LaTeX and R traces are visible within that same terminal!

Re: Sweave errors: more explicit?

2010-05-09 Thread [Ricardo Rodriguez] eBioTIC.
Hi! M. Speiser wrote: You might try starting LyX from a console/x-terminal-emulator. Under Unix/X11, you can see error messages in ~/.xsession-errors (for programs not started from an x-term... When I launch LyX from a terminal (mac os x), all LaTeX and R traces are visible within that

Sweave errors: more explicit?

2010-04-19 Thread M . Speiser
Hi, I am currently using LyX+Sweave a whole lot, huge fan of the concept! One of the few weaknesses of this solution though is that the error message (when there is something wrong with the R code) isn't much help: An error occurred whilst running R CMD Sweave 'myfile.Rnw' Is there a trick to

Re: Sweave errors: more explicit?

2010-04-19 Thread Guenter Milde
On 2010-04-19, M Speiser wrote: Hi, I am currently using LyX+Sweave a whole lot, huge fan of the concept! One of the few weaknesses of this solution though is that the error message (when there is something wrong with the R code) isn't much help: An error occurred whilst running R CMD

Sweave errors: more explicit?

2010-04-19 Thread M . Speiser
Hi, I am currently using LyX+Sweave a whole lot, huge fan of the concept! One of the few weaknesses of this solution though is that the error message (when there is something wrong with the R code) isn't much help: An error occurred whilst running R CMD Sweave 'myfile.Rnw' Is there a trick to

Re: Sweave errors: more explicit?

2010-04-19 Thread Guenter Milde
On 2010-04-19, M Speiser wrote: Hi, I am currently using LyX+Sweave a whole lot, huge fan of the concept! One of the few weaknesses of this solution though is that the error message (when there is something wrong with the R code) isn't much help: An error occurred whilst running R CMD

Sweave errors: more explicit?

2010-04-19 Thread M . Speiser
Hi, I am currently using LyX+Sweave a whole lot, huge fan of the concept! One of the few weaknesses of this solution though is that the error message (when there is something wrong with the R code) isn't much help: "An error occurred whilst running R CMD Sweave 'myfile.Rnw'" Is there a trick to

Re: Sweave errors: more explicit?

2010-04-19 Thread Guenter Milde
On 2010-04-19, M Speiser wrote: > Hi, > I am currently using LyX+Sweave a whole lot, huge fan of the concept! > One of the few weaknesses of this solution though is that the error > message (when there is something wrong with the R code) isn't much > help: > "An error occurred whilst running R