Re: Big document

Paul Johnson wrote: [...] There are no show-stopping problems for me, but a few little problems. Even though each chapter setup indicates that it has a master document, and I *thought* Lyx would get a pre-amble from that master document, it appears to have no effect when I look at chapters. I

Re: Big document

Paul Johnson wrote: [...] There are no show-stopping problems for me, but a few little problems. Even though each chapter setup indicates that it has a master document, and I *thought* Lyx would get a pre-amble from that master document, it appears to have no effect when I look at chapters. I

Re: Big document

Paul Johnson wrote: [...] There are no show-stopping problems for me, but a few little problems. Even though each chapter setup indicates that it has a master document, and I *thought* Lyx would get a pre-amble from that master document, it appears to have no effect when I look at chapters. I

Re: Big document

On 2009-02-02, Paul Johnson wrote: I have converted from a big document to a single small master document that includes the separate chapters. ... Here are some problems I've run into. 2. It is much nicer to work on the separate chapters in separate files. They are smaller, more manageable

Re: Big document

On 2009-02-02, Paul Johnson wrote: I have converted from a big document to a single small master document that includes the separate chapters. ... Here are some problems I've run into. 2. It is much nicer to work on the separate chapters in separate files. They are smaller, more manageable

Re: Big document

On 2009-02-02, Paul Johnson wrote: > I have converted from a big document to a single small master document > that includes the separate chapters. ... > Here are some problems I've run into. > 2. It is much nicer to work on the separate chapters in separate > files. They ar

Re: Big document

expect to wait not more than 40 seconds once the work is about to the end (which is annoying but won't kill): am I wrong? Some opinion/suggestion/experience? I have converted from a big document to a single small master document that includes the separate chapters. Here is the result, so far

Re: Big document

Paul Johnson pauljoh...@... writes: When there are things to go wrong, it seems like I can usually find them. Hope that helps. Thanks Paul, it has been very interesting. But you pointed out exactly my fears (not the most terrible anyway) so I think I'll try to keep the whole document,

Re: Big document

Piero Faustini wrote: And remember that you can always split the document if you feel that one big document is not suitable anymore. ...and is the reverse operation always possible? Yes, you can always merge two documents back to one: 1. Open one of the document. 2. Place the cursor

Re: Big document

expect to wait not more than 40 seconds once the work is about to the end (which is annoying but won't kill): am I wrong? Some opinion/suggestion/experience? I have converted from a big document to a single small master document that includes the separate chapters. Here is the result, so far

Re: Big document

Paul Johnson pauljoh...@... writes: When there are things to go wrong, it seems like I can usually find them. Hope that helps. Thanks Paul, it has been very interesting. But you pointed out exactly my fears (not the most terrible anyway) so I think I'll try to keep the whole document,

Re: Big document

Piero Faustini wrote: And remember that you can always split the document if you feel that one big document is not suitable anymore. ...and is the reverse operation always possible? Yes, you can always merge two documents back to one: 1. Open one of the document. 2. Place the cursor

Re: Big document

h and made small edits) - if the > proportion is the same, I expect to wait not more than 40 seconds once the > work > is about to the end (which is annoying but won't kill): am I wrong? > Some opinion/suggestion/experience? > > > > I have converted from a big document to a si

Re: Big document

Paul Johnson writes: > When there are things to go wrong, it seems like I can usually find > them. Hope that helps. > Thanks Paul, it has been very interesting. But you pointed out exactly my fears (not the most terrible anyway) so I think I'll try to keep the whole

Re: Big document

Piero Faustini wrote: > And remember that you can always split the document if you feel that one > big document is not suitable anymore. > ...and is the reverse operation always possible? Yes, you can always merge two documents back to one: 1. Open one of the document.

Big document

Hello fellow LyX users, I have to take a decision: wether to split my doctoral thesis in different files or not. Some people told me a thesis is HUGE and I should split the file into chapters or parts, but I'm afraid that something goes wrong at any time during the writing. It will be around

Re: Big document

My PhD is 190-ish pages in English, with tables, algorithms, figures, and a nice juicy bibliography. I have it divided into 8 included child documents (basically one per chapter), some of which are broken up logically into a few input child documents. DVI generation takes around 50 seconds, but

Re: Big document

Cameron Stone wrote: One more tip: create subdirectories for your embedded figures. I didn't and I wish I had (but I'm not spending the time to re-organise now that it's finished) In case you don't know .lyx file is plain text; so you can find and replace the graphics links quite easily

Re: Big document

(in respect to bibliography, etc). Splitting also makes version control a little easier, too. Works fine for me on the big document, too. One more tip: create subdirectories for your embedded figures. I didn't and I wish I had (but I'm not spending the time to re-organise now that it's finished

Re: Big document

two cases, I'd suggest to stay with one big document because it's simpler to manage. Just remember to backup often or better, use a source control system (git is great for local purpose). Abdel.

Re: Big document

Abdelrazak Younes you...@lyx.org writes: If you are not in one of those two cases, I'd suggest to stay with one big document because it's simpler to manage. Just remember to backup often or better, use a source control system (git is great for local purpose). And remember that you can always

Re: Big document

And remember that you can always split the document if you feel that one big document is not suitable anymore. ...and is the reverse operation always possible? Anyway, thanks to all, your opinions are very useful for me!

Re: Big document

Piero Faustini pierofaust...@hotmail.com writes: And remember that you can always split the document if you feel that one big document is not suitable anymore. ...and is the reverse operation always possible? As far as I know, yes. JMarc

Re: Big document

On Wednesday 28 January 2009 06:29:48 am Piero Faustini wrote: Hello fellow LyX users, I have to take a decision: wether to split my doctoral thesis in different files or not. Some people told me a thesis is HUGE and I should split the file into chapters or parts, but I'm afraid that something

Big document

Hello fellow LyX users, I have to take a decision: wether to split my doctoral thesis in different files or not. Some people told me a thesis is HUGE and I should split the file into chapters or parts, but I'm afraid that something goes wrong at any time during the writing. It will be around

Re: Big document

My PhD is 190-ish pages in English, with tables, algorithms, figures, and a nice juicy bibliography. I have it divided into 8 included child documents (basically one per chapter), some of which are broken up logically into a few input child documents. DVI generation takes around 50 seconds, but

Re: Big document

Cameron Stone wrote: One more tip: create subdirectories for your embedded figures. I didn't and I wish I had (but I'm not spending the time to re-organise now that it's finished) In case you don't know .lyx file is plain text; so you can find and replace the graphics links quite easily

Re: Big document

(in respect to bibliography, etc). Splitting also makes version control a little easier, too. Works fine for me on the big document, too. One more tip: create subdirectories for your embedded figures. I didn't and I wish I had (but I'm not spending the time to re-organise now that it's finished

Re: Big document

two cases, I'd suggest to stay with one big document because it's simpler to manage. Just remember to backup often or better, use a source control system (git is great for local purpose). Abdel.

Re: Big document

Abdelrazak Younes you...@lyx.org writes: If you are not in one of those two cases, I'd suggest to stay with one big document because it's simpler to manage. Just remember to backup often or better, use a source control system (git is great for local purpose). And remember that you can always

Re: Big document

And remember that you can always split the document if you feel that one big document is not suitable anymore. ...and is the reverse operation always possible? Anyway, thanks to all, your opinions are very useful for me!

Re: Big document

Piero Faustini pierofaust...@hotmail.com writes: And remember that you can always split the document if you feel that one big document is not suitable anymore. ...and is the reverse operation always possible? As far as I know, yes. JMarc

Re: Big document

On Wednesday 28 January 2009 06:29:48 am Piero Faustini wrote: Hello fellow LyX users, I have to take a decision: wether to split my doctoral thesis in different files or not. Some people told me a thesis is HUGE and I should split the file into chapters or parts, but I'm afraid that something

Big document

Hello fellow LyX users, I have to take a decision: wether to split my doctoral thesis in different files or not. Some people told me a thesis is HUGE and I should split the file into chapters or parts, but I'm afraid that something goes wrong at any time during the writing. It will be around

Re: Big document

My PhD is 190-ish pages in English, with tables, algorithms, figures, and a nice juicy bibliography. I have it divided into 8 included child documents (basically one per chapter), some of which are broken up logically into a few input child documents. DVI generation takes around 50 seconds, but

Re: Big document

Cameron Stone wrote: One more tip: create subdirectories for your embedded figures. I didn't and I wish I had (but I'm not spending the time to re-organise now that it's finished) In case you don't know .lyx file is plain text; so you can find and replace the graphics links quite easily

Re: Big document

(in respect to bibliography, etc). Splitting also makes version control a little easier, too. Works fine for me on the big document, too. One more tip: create subdirectories for your embedded figures. I didn't and I wish I had (but I'm not spending the time to re-organise now that it's finished

Re: Big document

two cases, I'd suggest to stay with one big document because it's simpler to manage. Just remember to backup often or better, use a source control system (git is great for local purpose). Abdel.

Re: Big document

Abdelrazak Younes <you...@lyx.org> writes: > If you are not in one of those two cases, I'd suggest to stay with one > big document because it's simpler to manage. Just remember to backup > often or better, use a source control system (git is great for local > purpose). And rem

Re: Big document

> And remember that you can always split the document if you feel that one > big document is not suitable anymore. > ...and is the reverse operation always possible? Anyway, thanks to all, your opinions are very useful for me!

Re: Big document

Piero Faustini <pierofaust...@hotmail.com> writes: >> And remember that you can always split the document if you feel that one >> big document is not suitable anymore. > > ...and is the reverse operation always possible? As far as I know, yes. JMarc

Re: Big document

On Wednesday 28 January 2009 06:29:48 am Piero Faustini wrote: > Hello fellow LyX users, > I have to take a decision: wether to split my doctoral thesis in different > files or not. Some people told me a thesis is HUGE and I should split the > file into chapters or parts, but I'm afraid that

Re: Navigating in a big document

Elver == Elver Loho [EMAIL PROTECTED] writes: Elver Unfortunately the Navigation system does not recognise Elver screenplay structure. Says that there is no table of contents. Elver (And generating a table of contents doesn't work either.) Elver There are no sections and chapters in this

Re: Navigating in a big document

On 9/11/06, Jean-Marc Lasgouttes [EMAIL PROTECTED] wrote: Elver == Elver Loho [EMAIL PROTECTED] writes: Elver Unfortunately the Navigation system does not recognise Elver screenplay structure. Says that there is no table of contents. Elver (And generating a table of contents doesn't work

Re: Navigating in a big document

Matej Cepl wrote: Elver Loho wrote: There are no sections and chapters in this document. Just the title page and scenes. I would say, that it is a bug in the LaTeX document structure then -- just a wild idea, cannot you contact developer of the LaTeX class to fix it? As far as I

Re: Navigating in a big document

Helge == Helge Hafting [EMAIL PROTECTED] writes: Helge As far as I know, the navigate menu is implemented in lyx, Helge not latex. It works by recognising document structure, i.e. Helge sections and such. Helge I don't know about hollywood class documents, but if they have Helge no sectioning

Re: Navigating in a big document

On 9/11/06, Jean-Marc Lasgouttes [EMAIL PROTECTED] wrote: Helge == Helge Hafting [EMAIL PROTECTED] writes: Helge As far as I know, the navigate menu is implemented in lyx, Helge not latex. It works by recognising document structure, i.e. Helge sections and such. Helge I don't know about

Re: Navigating in a big document

Elver == Elver Loho [EMAIL PROTECTED] writes: Elver Unfortunately the Navigation system does not recognise Elver screenplay structure. Says that there is no table of contents. Elver (And generating a table of contents doesn't work either.) Elver There are no sections and chapters in this

Re: Navigating in a big document

On 9/11/06, Jean-Marc Lasgouttes [EMAIL PROTECTED] wrote: Elver == Elver Loho [EMAIL PROTECTED] writes: Elver Unfortunately the Navigation system does not recognise Elver screenplay structure. Says that there is no table of contents. Elver (And generating a table of contents doesn't work

Re: Navigating in a big document

Matej Cepl wrote: Elver Loho wrote: There are no sections and chapters in this document. Just the title page and scenes. I would say, that it is a bug in the LaTeX document structure then -- just a wild idea, cannot you contact developer of the LaTeX class to fix it? As far as I

Re: Navigating in a big document

Helge == Helge Hafting [EMAIL PROTECTED] writes: Helge As far as I know, the navigate menu is implemented in lyx, Helge not latex. It works by recognising document structure, i.e. Helge sections and such. Helge I don't know about hollywood class documents, but if they have Helge no sectioning

Re: Navigating in a big document

On 9/11/06, Jean-Marc Lasgouttes [EMAIL PROTECTED] wrote: Helge == Helge Hafting [EMAIL PROTECTED] writes: Helge As far as I know, the navigate menu is implemented in lyx, Helge not latex. It works by recognising document structure, i.e. Helge sections and such. Helge I don't know about

Re: Navigating in a big document

> "Elver" == Elver Loho <[EMAIL PROTECTED]> writes: Elver> Unfortunately the Navigation system does not recognise Elver> screenplay structure. Says that there is no table of contents. Elver> (And generating a table of contents doesn't work either.) Elver> There are no sections and chapters

Re: Navigating in a big document

On 9/11/06, Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote: > "Elver" == Elver Loho <[EMAIL PROTECTED]> writes: Elver> Unfortunately the Navigation system does not recognise Elver> screenplay structure. Says that there is no table of contents. Elver> (And generating a table of contents

Re: Navigating in a big document

Matej Cepl wrote: Elver Loho wrote: There are no sections and chapters in this document. Just the title page and scenes. I would say, that it is a bug in the LaTeX document structure then -- just a wild idea, cannot you contact developer of the LaTeX class to fix it? As far as I

Re: Navigating in a big document

> "Helge" == Helge Hafting <[EMAIL PROTECTED]> writes: Helge> As far as I know, the "navigate" menu is implemented in lyx, Helge> not latex. It works by recognising document structure, i.e. Helge> sections and such. Helge> I don't know about hollywood class documents, but if they have Helge>

Re: Navigating in a big document

On 9/11/06, Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote: > "Helge" == Helge Hafting <[EMAIL PROTECTED]> writes: Helge> As far as I know, the "navigate" menu is implemented in lyx, Helge> not latex. It works by recognising document structure, i.e. Helge> sections and such. Helge> I don't

Re: Navigating in a big document

On 9/9/06, Matej Cepl [EMAIL PROTECTED] wrote: Elver Loho wrote: I was wondering... How do you guys navigate around in large files? I am not sure about screenplays and their structure, but about conveniently named menu Navigate? Does it work? Unfortunately the Navigation system does not

Re: Navigating in a big document

Elver Loho wrote: I was wondering... How do you guys navigate around in large files? I avoid large files ... because I avoid doing the amount of work needed to generate one. :-) I've got a 40-some page screenplay and working with it is a bit of a pain. It would be great if I could collapse

Re: Navigating in a big document

Elver Loho wrote: There are no sections and chapters in this document. Just the title page and scenes. I would say, that it is a bug in the LaTeX document structure then -- just a wild idea, cannot you contact developer of the LaTeX class to fix it? Matěj -- http://matej.ceplovi.cz/blog/ GPG

Re: Navigating in a big document

On 9/9/06, Matej Cepl [EMAIL PROTECTED] wrote: Elver Loho wrote: I was wondering... How do you guys navigate around in large files? I am not sure about screenplays and their structure, but about conveniently named menu Navigate? Does it work? Unfortunately the Navigation system does not

Re: Navigating in a big document

Elver Loho wrote: I was wondering... How do you guys navigate around in large files? I avoid large files ... because I avoid doing the amount of work needed to generate one. :-) I've got a 40-some page screenplay and working with it is a bit of a pain. It would be great if I could collapse

Re: Navigating in a big document

Elver Loho wrote: There are no sections and chapters in this document. Just the title page and scenes. I would say, that it is a bug in the LaTeX document structure then -- just a wild idea, cannot you contact developer of the LaTeX class to fix it? Matěj -- http://matej.ceplovi.cz/blog/ GPG

Re: Navigating in a big document

On 9/9/06, Matej Cepl <[EMAIL PROTECTED]> wrote: Elver Loho wrote: > I was wondering... How do you guys navigate around in large files? I am not sure about screenplays and their structure, but about conveniently named menu Navigate? Does it work? Unfortunately the Navigation system does not

Re: Navigating in a big document

Elver Loho wrote: I was wondering... How do you guys navigate around in large files? I avoid large files ... because I avoid doing the amount of work needed to generate one. :-) I've got a 40-some page screenplay and working with it is a bit of a pain. It would be great if I could collapse

Re: Navigating in a big document

Elver Loho wrote: > There are no sections and chapters in this document. Just the title > page and scenes. I would say, that it is a bug in the LaTeX document structure then -- just a wild idea, cannot you contact developer of the LaTeX class to fix it? Matěj -- http://matej.ceplovi.cz/blog/

Navigating in a big document

I was wondering... How do you guys navigate around in large files? I've got a 40-some page screenplay and working with it is a bit of a pain. It would be great if I could collapse scenes into just the scene header (int/ext) when not working directly with them. Sort of like most code editors

Re: Navigating in a big document

Elver Loho wrote: I was wondering... How do you guys navigate around in large files? I am not sure about screenplays and their structure, but about conveniently named menu Navigate? Does it work? Matěj -- http://matej.ceplovi.cz/blog/ GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964

Navigating in a big document

I was wondering... How do you guys navigate around in large files? I've got a 40-some page screenplay and working with it is a bit of a pain. It would be great if I could collapse scenes into just the scene header (int/ext) when not working directly with them. Sort of like most code editors

Re: Navigating in a big document

Elver Loho wrote: I was wondering... How do you guys navigate around in large files? I am not sure about screenplays and their structure, but about conveniently named menu Navigate? Does it work? Matěj -- http://matej.ceplovi.cz/blog/ GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964

Navigating in a big document

I was wondering... How do you guys navigate around in large files? I've got a 40-some page screenplay and working with it is a bit of a pain. It would be great if I could collapse scenes into just the scene header (int/ext) when not working directly with them. Sort of like most code editors

Re: Navigating in a big document

Elver Loho wrote: > I was wondering... How do you guys navigate around in large files? I am not sure about screenplays and their structure, but about conveniently named menu Navigate? Does it work? Matěj -- http://matej.ceplovi.cz/blog/ GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25