Re: branch warnings
Lars Gullik Bjønnes wrote: Is branch the only place where you do --without-included-boost? I don't specify that explicitly. I compile trunk --with-version-suffix=-svn --enable-maintainer-mode and branch with --enable-build-type=rel whatever these switches do in details. Jürgen -- Lgb
Re: branch warnings
Jürgen Spitzmüller sp...@lyx.org writes: | Lars Gullik Bjønnes wrote: Is branch the only place where you do --without-included-boost? | I don't specify that explicitly. | I compile trunk | --with-version-suffix=-svn --enable-maintainer-mode | and branch with | --enable-build-type=rel | whatever these switches do in details. The reason why I asked, that I have seen these warnings too, but only when I am or have been fiddling with --without-included-boost etc. first. -- Lgb
Categorization of letter classes
Branch: master Jürgen, the classes 'letter (g-brief...)' are not categorized. But could they not belong to category Letters? (Document-Settings...-Document Class-Letters) Kornel signature.asc Description: This is a digitally signed message part.
Re: LyX functions for bibliography managers
Hi, I created a patch implementing the bibtex-insert function, please see http://www.lyx.org/trac/ticket/8368 This is an attempt to enhance the workflow with external bibliography managers, by providing a new LFUN command bibtex-insert that takes one argument, a BibTeX fragment (i.e. one or more entries), and 1) Update the first LyX managed bibliography file (for the moment, it checks if the string lyxmanagedequals true, i.e. if @string{lyxmanaged = true} is in the BibTeX file) that occurs in a bibtex inset after the cursor position. For the moment, nothing is done if no LyX managed file exists (the function exits with an error). 2) Insert citations to all the bibtex entries given as an argument (or update if before/after a citation inset) The patch basically refactored the code that was used to parse a BibTeX file (in InsetBibtex.cpp), so it can be used to parse the managed file without updating any buffer cache, in order to update the BibTeX file. I also changed the information stored for each bibtex file in order to store the last update timestamp as well as the managed flag. I plan to enhance the patch in order to answer to suggestions and remarks, especially regarding improving what happens if no LyX managed bibliography exists (also, maybe it would be better to have a header to mark a file as LyX managed like % LyX managed file as the first line of the file, rather than a BibTeX string?). Benjamin On Jun 15, 2012, at 09:20 , Benjamin Piwowarski benjamin.piwowar...@lip6.fr wrote: On Jun 14, 2012, at 16:10 , Richard Heck wrote: On 06/13/2012 07:54 AM, Rainer M Krug wrote: While we are at that subject what is missing in the citation management, I would like to see two things: 1) the possibility to create a local .bib file (in the directory of the .lyx file) which contains only the references used. This would make co-operation between authors much easier. If this file could be embedded in the .lyx file, this would be brilliant, although this is not necessary, as other external files also exist. I'm not sure exactly how you want this to work, but it can easily enough be done with aux2bib. The downside to this method, to my mind, is that it's one-off: Once you've created this custom bib file, you've lost the ability to cite anything from your other bib file. So I tend to do this only at the end, or near it. Here is more precisely the plan. First, we need a function that gets the active BibTeX insets - i.e. the bibliography insets that would be used by a citation at this point of the file. This should deal with sectioned bibliographies, but in order to work with those, would need to use a LyX inset to separate bibliographies. Once we have a list of BibTex insets, we can check for LyX managed BibTeX files (using a special header in the .bib file - managed bibs in the following) that LyX has the right to modify. When we need to update a LyX managed BibTeX file, the process would go a bit further, by - if needed - (1) Proposing to create a BibTeX inset at the end of the file and (2) creating a managed bib in one of the insets (The first? Ask the user?) Only one function is really needed for basic functionality, that is a function that add/update one BibTeX entry bibtex-entries-put entry It would either identify a managed file where the entry exists and update it (by re-writing only the entry), or add it to one of the managed bib. In order to update a BibTeX file, LyX can mostly rely on the BibTeX parsing code already present and copy the file up to the entry, replace the entry by the one given, and then copy the rest of the file. This does seem to be difficult to achieve. If you agree on this, I will start (I would like to target 2.1) to work on it and post a patch on the list when ready. Benjamin
Re: LyX functions for bibliography managers
On 10/10/2012 09:41 AM, Benjamin Piwowarski wrote: Hi, I created a patch implementing the bibtex-insert function, please see http://www.lyx.org/trac/ticket/8368 [snip] The patch basically refactored the code that was used to parse a BibTeX file (in InsetBibtex.cpp), so it can be used to parse the managed file without updating any buffer cache, in order to update the BibTeX file. I also changed the information stored for each bibtex file in order to store the last update timestamp as well as the managed flag. I'd suggest dividing the patch into pieces. The first one might simply refactor the code a bit, then the next one (or two, or however many) add additional pieces, one coherent unit at a time. This makes reading the patches easier, and also allows any introduced bugs to be localized. Richard
Re: Re: Categorization of letter classes
Am Mittwoch, 10. Oktober 2012 um 14:56:01, schrieb Jürgen Spitzmüller sp...@lyx.org 2012/10/10 Kornel Benko: Jürgen, the classes 'letter (g-brief...)' are not categorized. But could they not belong to category Letters? They are categorized here (I habe categorized all layouts in the repo). Do you have copies of these layout in your ~./lyx/layouts directory? That's it! Jürgen Kornel signature.asc Description: This is a digitally signed message part.
Re: Categorization of letter classes
Le 10/10/12 16:47, Kornel Benko a écrit : They are categorized here (I habe categorized all layouts in the repo). Do you have copies of these layout in your ~./lyx/layouts directory? That's it! Would it be possible to autocategorize layouts in layout2layout, i.e. catch the name letter(Foo), set category to Letter and description to Foo? If we do that only for the categories we know (artcile, letter, ...) this should not be too error-prone. I think that many people have modified layout files in their personnal directory (and perhaps do not remember about it). JMarc
Re: Categorization of letter classes
2012/10/10 Jean-Marc Lasgouttes lasgout...@lyx.org: Would it be possible to autocategorize layouts in layout2layout, i.e. catch the name letter(Foo), set category to Letter and description to Foo? If we do that only for the categories we know (artcile, letter, ...) this should not be too error-prone. I think that many people have modified layout files in their personnal directory (and perhaps do not remember about it). Good idea. This would still only be a first step, since the change also involves (or should involve) a revision of the description. But better than nothing. Any volunteers? Jürgen JMarc
Re: Categorization of letter classes
Le 10/10/12 17:12, Jürgen Spitzmüller a écrit : Good idea. This would still only be a first step, since the change also involves (or should involve) a revision of the description. But better than nothing. Did you do more than keep what is inside parenthesis? Any volunteers? Good question :) JMarc
Re: Categorization of letter classes
2012/10/10 Jean-Marc Lasgouttes lasgout...@lyx.org: I see. That is indeed difficult to automate. Well, we could write a Siri plugin ;-) Jürgen
Re: Categorization of letter classes
On 10/10/2012 11:15 AM, Jean-Marc Lasgouttes wrote: Le 10/10/12 17:12, Jürgen Spitzmüller a écrit : Good idea. This would still only be a first step, since the change also involves (or should involve) a revision of the description. But better than nothing. Did you do more than keep what is inside parenthesis? Any volunteers? Good question :) I'll be happy to take care of this. Richard
Re: Categorization of letter classes
On 10/10/2012 01:15 PM, Richard Heck wrote: On 10/10/2012 11:15 AM, Jean-Marc Lasgouttes wrote: Le 10/10/12 17:12, Jürgen Spitzmüller a écrit : Good idea. This would still only be a first step, since the change also involves (or should involve) a revision of the description. But better than nothing. Did you do more than keep what is inside parenthesis? Any volunteers? Good question :) I'll be happy to take care of this. I bumped the format number, which seemed like a good idea, and wrote some lyx2lyx to deal with this, but it doesn't really work. I mean, I can use it manually to convert my own layouts, which seems like a good idea, but the category info is written at conversion time, by chkconfig.ltx, not at run time, so it doesn't do anything about categories from within LyX. So a user would need to run layout2layout.py manually, then reconfigure. Richard
Re: About LyX menus usability.
On 02/10/12 02:57, Pavel Sanda wrote: The problem is that there are usually many diverging opinions. so it seems. It might be better to make more brief Insert than dissolve Document into Edit/Insert. ok, for what it matters, a few less disruptive proposals: -) aggregate insertion of references to something into an Edit sub-menu ? (Insert-Reference-, then Citation..., Cross-Reference..., Label..., anything else ?) -) move Marginal note (and Footnote ?) to Insert-Note sub-menu That might mitigate the issue of the Insert menu size. -) if Document- has to contain operations affecting the whole document, then rendering with LaTeX, dvipdf, or viewing as HTML in a browser, etc..., seem all operations that deserve to be moved there. On the other hand, all the other entries in the View menu seem related to activating/deactivating certain GUI features of LyX. Furthermore, that would give more sense to have the View LaTeX Log menu entry in Document-..., wouldn't it ? Bye, T.
Ugly IPA toolbars on startup
When I start LyX, I get all the IPA toolbars superimposed on the top left of my toolbar area. This is quite annoying and I solved it by deselecting the toolbars one by one. How come I am the only one to complain about it? JMarc
Re: Categorization of letter classes
Le 10/10/12 19:58, Richard Heck a écrit : I bumped the format number, which seemed like a good idea, and wrote some lyx2lyx to deal with this, but it doesn't really work. I mean, I can use it manually to convert my own layouts, which seems like a good idea, but the category info is written at conversion time, by chkconfig.ltx, not at run time, so it doesn't do anything about categories from within LyX. So a user would need to run layout2layout.py manually, then reconfigure. The (long-term) plan could be like: 1/ change the layout format to be like the module format (this is needed anyway) 2/ use python to parse those layout files and eventually get rid of the latex-based detection (modules already do that anyway) 3/ change layout2layout to be more like a python package (it will please José anyway) 4/ convert layout files with layout2layout before parsing them in configure.py (otherwise it will break one day anyway) JMarc PS: it would be nice too to have a function the updates all user data in place, so that the foo2foo scripts do not have to be run every time (causing long startups).
Re: Ugly IPA toolbars on startup
On Wed, Oct 10, 2012 at 5:52 PM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: When I start LyX, I get all the IPA toolbars superimposed on the top left of my toolbar area. This is quite annoying and I solved it by deselecting the toolbars one by one. I've had this problem also. Thanks for the solution. How come I am the only one to complain about it? I was going to but I've already hit my quota of complaints for the month :) Scott
Re: Ugly IPA toolbars on startup
Le 11/10/12 00:16, Scott Kostyshak a écrit : On Wed, Oct 10, 2012 at 5:52 PM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: When I start LyX, I get all the IPA toolbars superimposed on the top left of my toolbar area. This is quite annoying and I solved it by deselecting the toolbars one by one. I've had this problem also. Thanks for the solution. What is very weird is that these things are supposed to be iconpalettes, and I see them as separate toolbars... JMarc
Re: Ugly IPA toolbars on startup
On 10/10/2012 06:26 PM, Jean-Marc Lasgouttes wrote: Le 11/10/12 00:16, Scott Kostyshak a écrit : On Wed, Oct 10, 2012 at 5:52 PM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: When I start LyX, I get all the IPA toolbars superimposed on the top left of my toolbar area. This is quite annoying and I solved it by deselecting the toolbars one by one. I've had this problem also. Thanks for the solution. What is very weird is that these things are supposed to be iconpalettes, and I see them as separate toolbars... I was wondering what that was. I've got them all superimposed over File and Edit. rh
Re: Noweb/Literate programming Copier problem
Kayvan Sylvan wrote: So I fixed the documentation (patch attached) and I now have a perfectly working solution for using LyX and noweb for literate programming. Please apply my patch and we can just close ticket 5444. Note that the Customization.lyx file had Change Tracking enabled, so I left it on. Someone will have to accept the changes after applying this patch. It is now in. BTW we still do not have a word about knitr in Additional manual. Yihui, what about add few paragraphs there? Pavel
Re: Noweb/Literate programming Copier problem
I'm pretty busy at the moment. I'm wondering if Scott can do it. Regards, Yihui -- Yihui Xie xieyi...@gmail.com Phone: 515-294-2465 Web: http://yihui.name Department of Statistics, Iowa State University 2215 Snedecor Hall, Ames, IA On Wed, Oct 10, 2012 at 6:41 PM, Pavel Sanda sa...@lyx.org wrote: Kayvan Sylvan wrote: So I fixed the documentation (patch attached) and I now have a perfectly working solution for using LyX and noweb for literate programming. Please apply my patch and we can just close ticket 5444. Note that the Customization.lyx file had Change Tracking enabled, so I left it on. Someone will have to accept the changes after applying this patch. It is now in. BTW we still do not have a word about knitr in Additional manual. Yihui, what about add few paragraphs there? Pavel
Re: Ugly IPA toolbars on startup
2012/10/11 Richard Heck rgh...@lyx.org: I was wondering what that was. I've got them all superimposed over File and Edit. I think it's a session problem. I have this always whenever a new toolbar is added. Jürgen rh
Re: branch warnings
Lars Gullik Bjønnes wrote: > Is branch the only place where you do --without-included-boost? I don't specify that explicitly. I compile trunk --with-version-suffix=-svn --enable-maintainer-mode and branch with --enable-build-type=rel whatever these switches do in details. Jürgen > -- > Lgb >
Re: branch warnings
Jürgen Spitzmüllerwrites: | Lars Gullik Bjønnes wrote: >> Is branch the only place where you do --without-included-boost? > | I don't specify that explicitly. > | I compile trunk | --with-version-suffix=-svn --enable-maintainer-mode > | and branch with | --enable-build-type=rel > | whatever these switches do in details. The reason why I asked, that I have seen these warnings too, but only when I am or have been fiddling with --without-included-boost etc. first. -- Lgb
Categorization of letter classes
Branch: master Jürgen, the classes 'letter (g-brief...)' are not categorized. But could they not belong to category "Letters"? (Document->Settings...->Document Class->Letters) Kornel signature.asc Description: This is a digitally signed message part.
Re: LyX functions for bibliography managers
Hi, I created a patch implementing the "bibtex-insert" function, please see http://www.lyx.org/trac/ticket/8368 This is an attempt to enhance the workflow with external bibliography managers, by providing a new LFUN command "bibtex-insert" that takes one argument, a BibTeX fragment (i.e. one or more entries), and 1) Update the first LyX managed bibliography file (for the moment, it checks if the string lyxmanagedequals true, i.e. if @string{lyxmanaged = "true"} is in the BibTeX file) that occurs in a bibtex inset after the cursor position. For the moment, nothing is done if no LyX managed file exists (the function exits with an error). 2) Insert citations to all the bibtex entries given as an argument (or update if before/after a citation inset) The patch basically refactored the code that was used to parse a BibTeX file (in InsetBibtex.cpp), so it can be used to parse the managed file without updating any buffer cache, in order to update the BibTeX file. I also changed the information stored for each bibtex file in order to store the last update timestamp as well as the "managed" flag. I plan to enhance the patch in order to answer to suggestions and remarks, especially regarding improving what happens if no LyX managed bibliography exists (also, maybe it would be better to have a header to mark a file as "LyX managed" like % LyX managed file as the first line of the file, rather than a BibTeX string?). Benjamin On Jun 15, 2012, at 09:20 , Benjamin Piwowarskiwrote: > > On Jun 14, 2012, at 16:10 , Richard Heck wrote: > >> On 06/13/2012 07:54 AM, Rainer M Krug wrote: >>> While we are at that subject what is missing in the citation management, I >>> would like to see two things: >>> 1) the possibility to create a local .bib file (in the directory of the >>> .lyx file) which contains only the references used. This would make >>> co-operation between authors much easier. If this file could be embedded in >>> the .lyx file, this would be brilliant, although this is not necessary, as >>> other external files also exist. >>> >> I'm not sure exactly how you want this to work, but it can easily enough be >> done with aux2bib. The downside to this method, to my mind, is that it's >> one-off: Once you've created this custom bib file, you've lost the ability >> to cite anything from your other bib file. So I tend to do this only at the >> end, or near it. > > Here is more precisely the plan. > > First, we need a function that gets the active BibTeX insets - i.e. the > bibliography insets that would be used by a citation at this point of the > file. This should deal with sectioned bibliographies, but in order to work > with those, would need to use a LyX inset to separate bibliographies. Once we > have a list of BibTex insets, we can check for LyX managed BibTeX files > (using a special header in the .bib file - managed bibs in the following) > that LyX has the right to modify. > > When we need to update a LyX managed BibTeX file, the process would go a bit > further, by - if needed - (1) Proposing to create a BibTeX inset at the end > of the file and (2) creating a managed bib in one of the insets (The first? > Ask the user?) > > Only one function is really needed for basic functionality, that is a > function that add/update one BibTeX entry > > bibtex-entries-put > > It would either identify a managed file where the entry exists and update it > (by re-writing only the entry), or add it to one of the managed bib. In order > to update a BibTeX file, LyX can mostly rely on the BibTeX parsing code > already present and copy the file up to the entry, replace the entry by the > one given, and then copy the rest of the file. This does seem to be difficult > to achieve. > > If you agree on this, I will start (I would like to target 2.1) to work on it > and post a patch on the list when ready. > > Benjamin >
Re: LyX functions for bibliography managers
On 10/10/2012 09:41 AM, Benjamin Piwowarski wrote: Hi, I created a patch implementing the "bibtex-insert" function, please see http://www.lyx.org/trac/ticket/8368 [snip] The patch basically refactored the code that was used to parse a BibTeX file (in InsetBibtex.cpp), so it can be used to parse the managed file without updating any buffer cache, in order to update the BibTeX file. I also changed the information stored for each bibtex file in order to store the last update timestamp as well as the "managed" flag. I'd suggest dividing the patch into pieces. The first one might simply refactor the code a bit, then the next one (or two, or however many) add additional pieces, one coherent unit at a time. This makes reading the patches easier, and also allows any introduced bugs to be localized. Richard
Re: Re: Categorization of letter classes
Am Mittwoch, 10. Oktober 2012 um 14:56:01, schrieb Jürgen Spitzmüller> 2012/10/10 Kornel Benko: > > Jürgen, the classes 'letter (g-brief...)' are not categorized. But could > > they not belong > > > > to category "Letters"? > > They are categorized here (I habe categorized all layouts in the > repo). Do you have copies of these layout in your ~./lyx/layouts > directory? That's it! > Jürgen Kornel signature.asc Description: This is a digitally signed message part.
Re: Categorization of letter classes
Le 10/10/12 16:47, Kornel Benko a écrit : > They are categorized here (I habe categorized all layouts in the > repo). Do you have copies of these layout in your ~./lyx/layouts > directory? That's it! Would it be possible to autocategorize layouts in layout2layout, i.e. catch the name "letter(Foo)", set category to Letter and description to Foo? If we do that only for the categories we know (artcile, letter, ...) this should not be too error-prone. I think that many people have modified layout files in their personnal directory (and perhaps do not remember about it). JMarc
Re: Categorization of letter classes
2012/10/10 Jean-Marc Lasgouttes: > Would it be possible to autocategorize layouts in layout2layout, i.e. catch > the name "letter(Foo)", set category to Letter and description to Foo? > > If we do that only for the categories we know (artcile, letter, ...) this > should not be too error-prone. > > I think that many people have modified layout files in their personnal > directory (and perhaps do not remember about it). Good idea. This would still only be a first step, since the change also involves (or should involve) a revision of the description. But better than nothing. Any volunteers? Jürgen > JMarc >
Re: Categorization of letter classes
Le 10/10/12 17:12, Jürgen Spitzmüller a écrit : Good idea. This would still only be a first step, since the change also involves (or should involve) a revision of the description. But better than nothing. Did you do more than keep what is inside parenthesis? Any volunteers? Good question :) JMarc
Re: Categorization of letter classes
2012/10/10 Jean-Marc Lasgouttes: > I see. That is indeed difficult to automate. Well, we could write a Siri plugin ;-) Jürgen
Re: Categorization of letter classes
On 10/10/2012 11:15 AM, Jean-Marc Lasgouttes wrote: Le 10/10/12 17:12, Jürgen Spitzmüller a écrit : Good idea. This would still only be a first step, since the change also involves (or should involve) a revision of the description. But better than nothing. Did you do more than keep what is inside parenthesis? Any volunteers? Good question :) I'll be happy to take care of this. Richard
Re: Categorization of letter classes
On 10/10/2012 01:15 PM, Richard Heck wrote: On 10/10/2012 11:15 AM, Jean-Marc Lasgouttes wrote: Le 10/10/12 17:12, Jürgen Spitzmüller a écrit : Good idea. This would still only be a first step, since the change also involves (or should involve) a revision of the description. But better than nothing. Did you do more than keep what is inside parenthesis? Any volunteers? Good question :) I'll be happy to take care of this. I bumped the format number, which seemed like a good idea, and wrote some lyx2lyx to deal with this, but it doesn't really work. I mean, I can use it manually to convert my own layouts, which seems like a good idea, but the category info is written at conversion time, by chkconfig.ltx, not at run time, so it doesn't do anything about categories from within LyX. So a user would need to run layout2layout.py manually, then reconfigure. Richard
Re: About LyX menus & usability.
On 02/10/12 02:57, Pavel Sanda wrote: The problem is that there are usually many diverging opinions. so it seems. It might be better to make more brief Insert than dissolve Document into Edit/Insert. ok, for what it matters, a few less disruptive proposals: -) aggregate insertion of references to something into an Edit sub-menu ? (Insert->Reference->, then Citation..., Cross-Reference..., Label..., anything else ?) -) move Marginal note (and Footnote ?) to Insert->Note sub-menu That might mitigate the issue of the Insert menu size. -) if Document-> has to contain operations affecting the whole document, then rendering with LaTeX, dvipdf, or viewing as HTML in a browser, etc..., seem all operations that deserve to be moved there. On the other hand, all the other entries in the View menu seem related to activating/deactivating certain GUI features of LyX. Furthermore, that would give more sense to have the "View LaTeX Log" menu entry in Document->..., wouldn't it ? Bye, T.
Ugly IPA toolbars on startup
When I start LyX, I get all the IPA toolbars superimposed on the top left of my toolbar area. This is quite annoying and I "solved" it by deselecting the toolbars one by one. How come I am the only one to complain about it? JMarc
Re: Categorization of letter classes
Le 10/10/12 19:58, Richard Heck a écrit : I bumped the format number, which seemed like a good idea, and wrote some lyx2lyx to deal with this, but it doesn't really work. I mean, I can use it manually to convert my own layouts, which seems like a good idea, but the category info is written at conversion time, by chkconfig.ltx, not at run time, so it doesn't do anything about categories from within LyX. So a user would need to run layout2layout.py manually, then reconfigure. The (long-term) plan could be like: 1/ change the layout format to be like the module format (this is needed anyway) 2/ use python to parse those layout files and eventually get rid of the latex-based detection (modules already do that anyway) 3/ change layout2layout to be more like a python package (it will please José anyway) 4/ convert layout files with layout2layout before parsing them in configure.py (otherwise it will break one day anyway) JMarc PS: it would be nice too to have a function the updates all user data in place, so that the foo2foo scripts do not have to be run every time (causing long startups).
Re: Ugly IPA toolbars on startup
On Wed, Oct 10, 2012 at 5:52 PM, Jean-Marc Lasgoutteswrote: > When I start LyX, I get all the IPA toolbars superimposed on the top left of > my toolbar area. This is quite annoying and I "solved" it by deselecting the > toolbars one by one. I've had this problem also. Thanks for the solution. > How come I am the only one to complain about it? I was going to but I've already hit my quota of complaints for the month :) Scott
Re: Ugly IPA toolbars on startup
Le 11/10/12 00:16, Scott Kostyshak a écrit : On Wed, Oct 10, 2012 at 5:52 PM, Jean-Marc Lasgoutteswrote: When I start LyX, I get all the IPA toolbars superimposed on the top left of my toolbar area. This is quite annoying and I "solved" it by deselecting the toolbars one by one. I've had this problem also. Thanks for the solution. What is very weird is that these things are supposed to be iconpalettes, and I see them as separate toolbars... JMarc
Re: Ugly IPA toolbars on startup
On 10/10/2012 06:26 PM, Jean-Marc Lasgouttes wrote: Le 11/10/12 00:16, Scott Kostyshak a écrit : On Wed, Oct 10, 2012 at 5:52 PM, Jean-Marc Lasgoutteswrote: When I start LyX, I get all the IPA toolbars superimposed on the top left of my toolbar area. This is quite annoying and I "solved" it by deselecting the toolbars one by one. I've had this problem also. Thanks for the solution. What is very weird is that these things are supposed to be iconpalettes, and I see them as separate toolbars... I was wondering what that was. I've got them all superimposed over "File" and "Edit". rh
Re: Noweb/Literate programming Copier problem
Kayvan Sylvan wrote: > So I fixed the documentation (patch attached) and I now have a perfectly > working solution for using LyX and noweb for literate programming. > > Please apply my patch and we can just close ticket 5444. > > Note that the Customization.lyx file had Change Tracking enabled, so I left > it on. Someone will have to accept the changes after applying this patch. It is now in. BTW we still do not have a word about knitr in Additional manual. Yihui, what about add few paragraphs there? Pavel
Re: Noweb/Literate programming Copier problem
I'm pretty busy at the moment. I'm wondering if Scott can do it. Regards, Yihui -- Yihui XiePhone: 515-294-2465 Web: http://yihui.name Department of Statistics, Iowa State University 2215 Snedecor Hall, Ames, IA On Wed, Oct 10, 2012 at 6:41 PM, Pavel Sanda wrote: > Kayvan Sylvan wrote: >> So I fixed the documentation (patch attached) and I now have a perfectly >> working solution for using LyX and noweb for literate programming. >> >> Please apply my patch and we can just close ticket 5444. >> >> Note that the Customization.lyx file had Change Tracking enabled, so I left >> it on. Someone will have to accept the changes after applying this patch. > > It is now in. > BTW we still do not have a word about knitr in Additional manual. > Yihui, what about add few paragraphs there? > > Pavel
Re: Ugly IPA toolbars on startup
2012/10/11 Richard Heck: > I was wondering what that was. I've got them all superimposed over "File" > and "Edit". I think it's a "session" problem. I have this always whenever a new toolbar is added. Jürgen > rh >