Julien Rioux wrote:
On 16/11/2010 8:56 AM, Jannick Asmus wrote:
\renewcommand{\lyxadded}[3]{{\cbstart\color{lyxadded}{}#3\cbend}}
\renewcommand{\lyxdeleted}[3]{{\cbstart\color{lyxdeleted}\sout{#3}\cbend}}
That's what I meant by funky code.
Ahh, I misunderstood you.
The reason I asked is
Julien Rioux wrote:
On 16/11/2010 8:56 AM, Jannick Asmus wrote:
\renewcommand{\lyxadded}[3]{{\cbstart\color{lyxadded}{}#3\cbend}}
\renewcommand{\lyxdeleted}[3]{{\cbstart\color{lyxdeleted}\sout{#3}\cbend}}
That's what I meant by funky code.
Ahh, I misunderstood you.
The reason I asked is
Julien Rioux wrote:
On 16/11/2010 8:56 AM, Jannick Asmus wrote:
\renewcommand{\lyxadded}[3]{{\cbstart\color{lyxadded}{}#3\cbend}}
\renewcommand{\lyxdeleted}[3]{{\cbstart\color{lyxdeleted}\sout{#3}\cbend}}
That's what I meant by funky code.
Ahh, I misunderstood you.
The reason I asked is
Julien Rioux wrote:
Do you have funky show changes in output code?
No, the compilation crashes so that there is no pdf output. What seems
to produce problems is something like
\subsection{\lyxadded{Jannick}{Tue Nov 16 10:41:08 2010}{My New
Subsection}}
Vincent suggested to replace the
On 16/11/2010 8:56 AM, Jannick Asmus wrote:
\renewcommand{\lyxadded}[3]{{\cbstart\color{lyxadded}{}#3\cbend}}
\renewcommand{\lyxdeleted}[3]{{\cbstart\color{lyxdeleted}\sout{#3}\cbend}}
That's what I meant by funky code. The reason I asked is that I had a
suspicion. I also have my own
Julien Rioux wrote:
Do you have funky show changes in output code?
No, the compilation crashes so that there is no pdf output. What seems
to produce problems is something like
\subsection{\lyxadded{Jannick}{Tue Nov 16 10:41:08 2010}{My New
Subsection}}
Vincent suggested to replace the
On 16/11/2010 8:56 AM, Jannick Asmus wrote:
\renewcommand{\lyxadded}[3]{{\cbstart\color{lyxadded}{}#3\cbend}}
\renewcommand{\lyxdeleted}[3]{{\cbstart\color{lyxdeleted}\sout{#3}\cbend}}
That's what I meant by funky code. The reason I asked is that I had a
suspicion. I also have my own
Julien Rioux wrote:
Do you have funky "show changes in output" code?
No, the compilation crashes so that there is no pdf output. What seems
to produce problems is something like
\subsection{\lyxadded{Jannick}{Tue Nov 16 10:41:08 2010}{My New
Subsection}}
Vincent suggested to replace the
On 16/11/2010 8:56 AM, Jannick Asmus wrote:
\renewcommand{\lyxadded}[3]{{\cbstart\color{lyxadded}{}#3\cbend}}
\renewcommand{\lyxdeleted}[3]{{\cbstart\color{lyxdeleted}\sout{#3}\cbend}}
That's what I meant by funky code. The reason I asked is that I had a
suspicion. I also have my own
Hi,
sections or subsections inserted in track mode yield an compilation
error. Prompted error is, e.g., Use of \...@part doesn't match its
definition. Interestingly, changes of headings in track mode are not
liked either.
Did anyone get aware of that? Or is that a bug?
/J.
Sections or subsections inserted in track mode yield an compilation error.
Prompted error is, e.g., Use of \...@part doesn't match its definition.
Interestingly, changes of headings in track mode are not liked either.
I don't see a problem with this.
Can you send an example file which shows
On 16/11/2010 4:19 AM, Jannick Asmus wrote:
Hi,
sections or subsections inserted in track mode yield an compilation
error. Prompted error is, e.g., Use of \...@part doesn't match its
definition. Interestingly, changes of headings in track mode are not
liked either.
Did anyone get aware of
Hi,
sections or subsections inserted in track mode yield an compilation
error. Prompted error is, e.g., Use of \...@part doesn't match its
definition. Interestingly, changes of headings in track mode are not
liked either.
Did anyone get aware of that? Or is that a bug?
/J.
Sections or subsections inserted in track mode yield an compilation error.
Prompted error is, e.g., Use of \...@part doesn't match its definition.
Interestingly, changes of headings in track mode are not liked either.
I don't see a problem with this.
Can you send an example file which shows
On 16/11/2010 4:19 AM, Jannick Asmus wrote:
Hi,
sections or subsections inserted in track mode yield an compilation
error. Prompted error is, e.g., Use of \...@part doesn't match its
definition. Interestingly, changes of headings in track mode are not
liked either.
Did anyone get aware of
Hi,
sections or subsections inserted in track mode yield an compilation
error. Prompted error is, e.g., "Use of \...@part doesn't match its
definition". Interestingly, changes of headings in track mode are not
liked either.
Did anyone get aware of that? Or is that a bug?
/J.
> Sections or subsections inserted in track mode yield an compilation error.
> Prompted error is, e.g., "Use of \...@part doesn't match its definition".
> Interestingly, changes of headings in track mode are not liked either.
I don't see a problem with this.
Can you send an example file which
On 16/11/2010 4:19 AM, Jannick Asmus wrote:
Hi,
sections or subsections inserted in track mode yield an compilation
error. Prompted error is, e.g., "Use of \...@part doesn't match its
definition". Interestingly, changes of headings in track mode are not
liked either.
Did anyone get aware of
18 matches
Mail list logo