>
> > A "show output anyway" button would be great.
> > However, if LyX consistency were assured, there's no need for it (expect
> > when using ERT).
>
> ... or the LaTeX preamble (1) or an outdated TeX distribution (2) or a
> package
> combination with conflicts (3) or ... (?)
>
> Günter
>
I repe
On 2011-05-11, Diego Queiroz wrote:
> [-- Type: text/plain, Encoding: --]
>> But the only one for truly consistent behaviour. If you want to export
>> stand-alone, uncheck the master setting.
> Even if the master setting is not set in the child, LyX still display all
> macros perfectly if the
>
> But the only one for truly consistent behaviour. If you want to export
> stand-alone, uncheck the master setting.
>
Even if the master setting is not set in the child, LyX still display all
macros perfectly if the master document is open.
My complaint is this: if LyX is able to interpret thing
On 2011-05-10, Diego Queiroz wrote:
>> >>> For truly consistent behaviour, we would have to disable stand-alone
>> >>> compilation of documents setting a master (except for "included" (vs.
>> >>> "input") documents).
> This is a strong restriction.
But the only one for truly consistent behaviour
>
> >>> For truly consistent behaviour, we would have to disable stand-alone
> >>> compilation of documents setting a master (except for "included" (vs.
> >>> "input") documents).
>
This is a strong restriction.
With this, in a document with thousand of pages I will obligated to generate
all pages
On 05/10/2011 09:09 AM, Guenter Milde wrote:
> On 2011-05-10, Jürgen Spitzmüller wrote:
>> Guenter Milde wrote:
>>> For truly consistent behaviour, we would have to disable stand-alone
>>> compilation of documents setting a master (except for "included" (vs.
>>> "input") documents).
>> Why this? I
On 2011-05-10, Jürgen Spitzmüller wrote:
> Guenter Milde wrote:
>> For truly consistent behaviour, we would have to disable stand-alone
>> compilation of documents setting a master (except for "included" (vs.
>> "input") documents).
> Why this? I have many documents with a master set that get comp
Guenter Milde wrote:
> For truly consistent behaviour, we would have to disable stand-alone
> compilation of documents setting a master (except for "included" (vs.
> "input") documents).
Why this? I have many documents with a master set that get compiled stand-
alone from time to time and should _
On 2011-05-09, Diego Queiroz wrote:
>> But what if you really want to compile it as a standalone document?
>> People do this.
>> Richard
> But if it was really a standalone document, I would have to unset master
> document property, right?
...
> I am just looking for a more "user oriented be
>
> Yes I am able to do what you describe in 1.6. In your example child doc,
> you did not set the master setting, did you?
>
Indeed.
I was in a hurry and I forgot it. ;/
---
Diego Queiroz
On 05/09/2011 02:38 PM, Julien Rioux wrote:
>
> Yes I am able to do what you describe in 1.6. In your example child
> doc, you did not set the master setting, did you? But anyway, I
> corrected it and still in 2.1.0svn the compilation of the child is
> broken:
>
> Undefined control sequence \anymac
On 09/05/2011 2:23 PM, Diego Queiroz wrote:
Which workaround? You said math macros don't work within child docs, I say
they work for me. No workaround necessary.
Maybe I misunderstood you.
I was citing your workaround to include bibtex in the childs.
"I use a branch named "child only", whic
>
> Which workaround? You said math macros don't work within child docs, I say
> they work for me. No workaround necessary.
>
Maybe I misunderstood you.
I was citing your workaround to include bibtex in the childs.
>> "I use a branch named "child only", which is activated in child docs but
deacti
On 09/05/2011 1:44 PM, Diego Queiroz wrote:
So, I do not experience your problem. However document settings and stuff
that gets defined in the preamble need to be set in both master and child
docs.
--
Julien
Actually, the answer is: yes, you do experience the very same problem.
Otherwise you
On 09/05/2011 1:44 PM, Diego Queiroz wrote:
So, I do not experience your problem. However document settings and stuff
that gets defined in the preamble need to be set in both master and child
docs.
--
Julien
Actually, the answer is: yes, you do experience the very same problem.
Otherwise you
>
> So, I do not experience your problem. However document settings and stuff
> that gets defined in the preamble need to be set in both master and child
> docs.
> --
> Julien
>
Actually, the answer is: yes, you do experience the very same problem.
Otherwise you won't need to go after a workaround
On 09/05/2011 10:22 AM, Diego Queiroz wrote:
I'm not sure if this is a bug report or a feature request. Probably the
second one.
In LyX it's ok to define a Math Macro in a Master document and use it in a
child one. It's also ok to use math macros that are defined in a child and
use it in other c
>
> But what if you really want to compile it as a standalone document?
> People do this.
>
> Richard
>
But if it was really a standalone document, I would have to unset master
document property, right?
Anyway, in my case, the problem is that my child document with the macros
also define Nomencla
On 05/09/2011 11:05 AM, Diego Queiroz wrote:
>
>> If you want to compile just one chapter as part of a larger document,
>> then you need to use the \includeonly support, accessible from
>> Document>Settings.
> I was not aware of this feature. Thanks for the hint.
>
It's new in 2.0.0.
> But it is a
>
> If you ask to compile just the child, then you are asking to compile it
> as a standalone document, so it is no surprise that this does not work.
>
Exactly. :-)
> If you want to compile just one chapter as part of a larger document,
> then you need to use the \includeonly support, accessibl
On 05/09/2011 10:22 AM, Diego Queiroz wrote:
> I'm not sure if this is a bug report or a feature request. Probably the
> second one.
>
> In LyX it's ok to define a Math Macro in a Master document and use it in a
> child one. It's also ok to use math macros that are defined in a child and
> use it i
I'm not sure if this is a bug report or a feature request. Probably the
second one.
In LyX it's ok to define a Math Macro in a Master document and use it in a
child one. It's also ok to use math macros that are defined in a child and
use it in other child document.
In both cases, I am able to vie
22 matches
Mail list logo
