Re: Ugly IPA toolbars on startup
Le 12/10/12 15:39, Jürgen Spitzmüller a écrit : Jean-Marc Lasgouttes wrote: It is terribly annoying. Also, it would be nice if the toolbar palettes were second class citizens so that they do not appear in View>Toolbar. The list is becoming unmanageable. Does not look like a very difficult task (I'm too busy ATM, though). I think I complained too fast. These palettes are already in the "other toolbars" menu. So the only problem that remains is these ugly toolbars on startup. I do not understand why this happens only with these new ones. JMarc
Re: Error in build process on Windows 7, using Visual Studio 2012
> - to be able to run the executable, it should be installed along with the > necessary dlls, > *This point still remains. Either: - I have to copy the dlls manually to the bin directory, - or I have to call check_convert.exe from the directory where the dlls are. This is the same as for LyX.exe itself. I have to specify the startup directory to point at the directory where the dlls are (the GNUWIN32 dir). * Apart from this it seems to work, though the filetools test fails trivially. On windows the path is "C:/foo" instead of "/foo". * I'm wondering whether we want a new project for every test we will have. Or we need to subgroup some projects. * There is also a new 'test' project. What does it test ? What is the difference between check and test ? * What does "checkregfiles" mean ? Vincent
Re: About LyX menus & usability.
On 2012-10-17, Tommaso Cucinotta wrote: > On 17/10/12 11:26, Jürgen Spitzmüller wrote: >> Marginal notes and footnotes are conceptually different to the >> LyX notes, despite the similar name. LyX notes are rather editiorial >> tools (adressed at the author/editor; except for "greyed out maybe, >> which is a problematic case in itself). Footnotes, endnotes and >> marginal notes are part of the document proper. Since they are so >> important in scientific writing, moving them to a second level would >> be a bad sign for a mainly "scientific" writing application. Maybe we can gain clarity renaming Insert>Note>... to Insert>Comment>LyX Note >Comment >Greyed out (or drop/merge the "greyed out" with branches...). Günter
Re: $$e not set on import --> import of .Rnw (knitr) fails
Import Rnw is something I was asked long time ago but have not figured out how it works. It seems the Sweave/knitr module is called but really should not be, because these modules are only responsible for Rnw-->TeX, not for Rnw-->LyX. Or should they? Ideally LyX should be able to handle the TeX part, and for the R code chunks (<<>>= and @), they can be imported to ERT, but I do not know how to do that. Regards, Yihui -- Yihui Xie Phone: 515-294-2465 Web: http://yihui.name Department of Statistics, Iowa State University 2215 Snedecor Hall, Ames, IA On Thu, Oct 18, 2012 at 5:02 AM, Scott Kostyshak wrote: > On Thu, Oct 18, 2012 at 3:46 AM, Jean-Marc Lasgouttes > wrote: >> Le 18/10/12 01:49, Scott Kostyshak a écrit : >> Stupid question; where is importation of knitr files defined in converters? >>> >>> >>> Rnw (knitr) -> latex (plain) >>> The converter is currently: >>> Rscript --verbose --no-save --no-restore $$s/scripts/lyxknitr.R $$p$$i >>> $$p$$o $$e $$r >>> When I change this to the following, import works: >>> Rscript --verbose --no-save --no-restore $$s/scripts/lyxknitr.R $$p$$i >>> $$p$$o ISO-8859-15 $$r >> >> >> But this is a converter for export, not import. > > Ah, then I don't understand how LyX handles imports. The Customization > manual does not talk about importing. Doesn't LyX use the converters > to convert the file to LaTeX and then use tex2lyx to import the tex > file? > >> What is the difference between the Rnw files when you do this change? > > No difference. In the recipe for reproducing, steps (1) and (2) are > the same. To get it to import I only substitute for $$e before step > (3) (importing). > > Scott
Re: $$e not set on import --> import of .Rnw (knitr) fails
On Thu, Oct 18, 2012 at 9:11 AM, Jean-Marc Lasgouttes wrote: > Le 18/10/2012 14:55, Scott Kostyshak a écrit : > >>> The old way this "noweb mode" works is >>> 1/ ensure that the class name is literate-something (now it would be >>> ensure >>> that some module is loaded and the module name should be passed to >>> tex2lyx) >>> >>> 2/ when a layout starts with <<, change it to a layout with name "Scrap". >>> This could be OK because the Sweave/knitr modules declare Scrap as a >>> synonym >>> for Chunk. >>> >>> 3/ transform [[something]] to ERT. I do not know what this is good for, >>> presumably a noweb-only thing. >> >> >> OK, thanks for the explanation. > > > So my point is that we should fix 1/ and get rid of the literate-xx classes > if they are still there. Ah, now I see why importing these types of files is different -- because they depend on modules. I didn't think about that. > > >> Yes, the only thing that changes is what I have as the Converter for >> Rnw (knitr) to LaTeX (plain). Is there some other output that I can >> send? Any -dbg flag that I can set to give more information on this? > > > Try "-dbg files". The unchangedConverter.log is here (error): http://paste.debian.net/201557/ And the changedConverter.log is here (no error): http://paste.debian.net/201558/ Thanks, Scott
Re: [LyX 2.0.x] * Additional.lyx - no CT in branch.
On Thu, Oct 18, 2012 at 9:15 AM, Pavel Sanda wrote: > The branch, 2.0.x, has been updated. > > - Log - > > commit d21eac8a893945aa05c0e945794a99143a34971b > Author: Pavel Sanda > Date: Thu Oct 18 15:14:46 2012 +0200 > > * Additional.lyx - no CT in branch. Sorry, Pavel. I'll remember this for next time. Thanks, Scott
Re: $$e not set on import --> import of .Rnw (knitr) fails
The [[foo]] notation is noweb syntax for a reference to something that is defined elsewhere. By putting it in an ERT we ensure that it ends up in the noweb file unaltered. On Oct 18, 2012, at 5:18, Jean-Marc Lasgouttes wrote: > Le 18/10/2012 14:02, Scott Kostyshak a écrit : >> Ah, then I don't understand how LyX handles imports. The Customization >> manual does not talk about importing. Doesn't LyX use the converters >> to convert the file to LaTeX and then use tex2lyx to import the tex >> file? > > Normally, the importation is done by tex2lyx using the -n flag, but I > think that this support needs to be updated to the new world of module > based literate programming. > > The old way this "noweb mode" works is > 1/ ensure that the class name is literate-something (now it would be > ensure that some module is loaded and the module name should be passed > to tex2lyx) > > 2/ when a layout starts with <<, change it to a layout with name > "Scrap". This could be OK because the Sweave/knitr modules declare Scrap > as a synonym for Chunk. > > 3/ transform [[something]] to ERT. I do not know what this is good for, > presumably a noweb-only thing. >> >>> What is the difference between the Rnw files when you do this change? >> >> No difference. In the recipe for reproducing, steps (1) and (2) are >> the same. > > You mean that the Rnw files are the same in the two cases? This is weird. > > JMarc >
Re: $$e not set on import --> import of .Rnw (knitr) fails
Le 18/10/2012 14:55, Scott Kostyshak a écrit : The old way this "noweb mode" works is 1/ ensure that the class name is literate-something (now it would be ensure that some module is loaded and the module name should be passed to tex2lyx) 2/ when a layout starts with <<, change it to a layout with name "Scrap". This could be OK because the Sweave/knitr modules declare Scrap as a synonym for Chunk. 3/ transform [[something]] to ERT. I do not know what this is good for, presumably a noweb-only thing. OK, thanks for the explanation. So my point is that we should fix 1/ and get rid of the literate-xx classes if they are still there. Yes, the only thing that changes is what I have as the Converter for Rnw (knitr) to LaTeX (plain). Is there some other output that I can send? Any -dbg flag that I can set to give more information on this? Try "-dbg files". JMarc
Re: $$e not set on import --> import of .Rnw (knitr) fails
On Thu, Oct 18, 2012 at 8:18 AM, Jean-Marc Lasgouttes wrote: > Le 18/10/2012 14:02, Scott Kostyshak a écrit : > >> Ah, then I don't understand how LyX handles imports. The Customization >> manual does not talk about importing. Doesn't LyX use the converters >> to convert the file to LaTeX and then use tex2lyx to import the tex >> file? > > > Normally, the importation is done by tex2lyx using the -n flag, but I think > that this support needs to be updated to the new world of module based > literate programming. > > The old way this "noweb mode" works is > 1/ ensure that the class name is literate-something (now it would be ensure > that some module is loaded and the module name should be passed to tex2lyx) > > 2/ when a layout starts with <<, change it to a layout with name "Scrap". > This could be OK because the Sweave/knitr modules declare Scrap as a synonym > for Chunk. > > 3/ transform [[something]] to ERT. I do not know what this is good for, > presumably a noweb-only thing. OK, thanks for the explanation. >> >>> What is the difference between the Rnw files when you do this change? >> >> >> No difference. In the recipe for reproducing, steps (1) and (2) are >> the same. > > > You mean that the Rnw files are the same in the two cases? This is weird. Yes, the only thing that changes is what I have as the Converter for Rnw (knitr) to LaTeX (plain). Is there some other output that I can send? Any -dbg flag that I can set to give more information on this? Thanks, Scott
Re: About LyX menus & usability.
Tommaso Cucinotta wrote: > What about "Version Control" operations ? They probably affect the whole > document, so move them to Document ? However, it's quite common to find > that stuff under "File". No, this really belongs to file, not to the document content. > Again, inserting figures is very very common, You said it yourself ;) While we can discuss Date or Preview items, killing Graphics looks really harsh for whatever reason. Pavel
Re: $$e not set on import --> import of .Rnw (knitr) fails
Le 18/10/2012 14:02, Scott Kostyshak a écrit : Ah, then I don't understand how LyX handles imports. The Customization manual does not talk about importing. Doesn't LyX use the converters to convert the file to LaTeX and then use tex2lyx to import the tex file? Normally, the importation is done by tex2lyx using the -n flag, but I think that this support needs to be updated to the new world of module based literate programming. The old way this "noweb mode" works is 1/ ensure that the class name is literate-something (now it would be ensure that some module is loaded and the module name should be passed to tex2lyx) 2/ when a layout starts with <<, change it to a layout with name "Scrap". This could be OK because the Sweave/knitr modules declare Scrap as a synonym for Chunk. 3/ transform [[something]] to ERT. I do not know what this is good for, presumably a noweb-only thing. What is the difference between the Rnw files when you do this change? No difference. In the recipe for reproducing, steps (1) and (2) are the same. You mean that the Rnw files are the same in the two cases? This is weird. JMarc
Re: About LyX menus & usability.
Le 18/10/2012 11:34, Liviu Andronic a écrit : On Thu, Oct 18, 2012 at 7:45 AM, Jürgen Spitzmüller wrote: I wonder if the term "Annotation" for LyX Notes and comments would be better. I think less people would associate that with footnotes and marginal notes. Actually this would be a good idea. Yes, this looks like a good term. JMarc
Re: $$e not set on import --> import of .Rnw (knitr) fails
On Thu, Oct 18, 2012 at 3:46 AM, Jean-Marc Lasgouttes wrote: > Le 18/10/12 01:49, Scott Kostyshak a écrit : > >>> Stupid question; where is importation of knitr files defined in >>> converters? >> >> >> Rnw (knitr) -> latex (plain) >> The converter is currently: >> Rscript --verbose --no-save --no-restore $$s/scripts/lyxknitr.R $$p$$i >> $$p$$o $$e $$r >> When I change this to the following, import works: >> Rscript --verbose --no-save --no-restore $$s/scripts/lyxknitr.R $$p$$i >> $$p$$o ISO-8859-15 $$r > > > But this is a converter for export, not import. Ah, then I don't understand how LyX handles imports. The Customization manual does not talk about importing. Doesn't LyX use the converters to convert the file to LaTeX and then use tex2lyx to import the tex file? > What is the difference between the Rnw files when you do this change? No difference. In the recipe for reproducing, steps (1) and (2) are the same. To get it to import I only substitute for $$e before step (3) (importing). Scott
Re: About LyX menus & usability.
On Thu, Oct 18, 2012 at 7:45 AM, Jürgen Spitzmüller wrote: > I wonder if the term "Annotation" for LyX Notes and comments would be > better. I think less people would associate that with footnotes and > marginal notes. > Actually this would be a good idea. > How are these things called in Word Processors and PDF Readers in English UIs? > PDF readers use the term 'annotation' for roughly what LyX calls notes/comments. See [1] but also in Evince > Side Pane > Annotations. [1] http://www.qtrac.eu/viewpdf.html Liviu
Re: $$e not set on import --> import of .Rnw (knitr) fails
Le 18/10/12 01:49, Scott Kostyshak a écrit : Stupid question; where is importation of knitr files defined in converters? Rnw (knitr) -> latex (plain) The converter is currently: Rscript --verbose --no-save --no-restore $$s/scripts/lyxknitr.R $$p$$i $$p$$o $$e $$r When I change this to the following, import works: Rscript --verbose --no-save --no-restore $$s/scripts/lyxknitr.R $$p$$i $$p$$o ISO-8859-15 $$r But this is a converter for export, not import. What is the difference between the Rnw files when you do this change? JMarc
