Richard Heck wrote:
> Alternatively, we can fix the comments package. I did so with paper (and to
> some extent took over maintaining it).
if you know how, then this would be the solution.
pavel
On 07/13/2009 10:29 AM, Pavel Sanda wrote:
Jean-Marc Lasgouttes wrote:
Ouch, So we rely on a broken package?
frankly i have no idea whats going on there. if \...@savsf=1 is problem
then i wont commit it.
I don't know. But it really looks like a bad hack.
+1
Jean-Marc Lasgouttes wrote:
Ouch, So we rely on a broken package?
>>>
>>> frankly i have no idea whats going on there. if \...@savsf=1 is problem
>>> then i wont commit it.
>>
>> I don't know. But it really looks like a bad hack.
>
> +1
ok, i withdraw
pavel
Le 13 juil. 09 à 16:15, Jürgen Spitzmüller a écrit :
Am Montag 13 Juli 2009 16:14:31 schrieb Pavel Sanda:
Ouch, So we rely on a broken package?
frankly i have no idea whats going on there. if \...@savsf=1 is problem
then i wont commit it.
I don't know. But it really looks like a bad hack.
Am Montag 13 Juli 2009 16:14:31 schrieb Pavel Sanda:
> > Ouch, So we rely on a broken package?
>
> frankly i have no idea whats going on there. if \...@savsf=1 is problem
> then i wont commit it.
I don't know. But it really looks like a bad hack.
Jürgen
Jürgen Spitzmüller wrote:
> > otherwise i get latex error:
> > "
> > Bad space factor (0).
> > \end{comment}
> >I allow only values in the range 1..32767 here.
> > "
> >
> > i dont know why it happens but i found this solution googling through
> > forums.
>
> Ouch, So we rely on a broken pack
Am Montag 13 Juli 2009 16:10:04 schrieb Pavel Sanda:
> otherwise i get latex error:
> "
> Bad space factor (0).
> \end{comment}
>I allow only values in the range 1..32767 here.
> "
>
> i dont know why it happens but i found this solution googling through
> forums.
Ouch, So we rely on a broken
Jürgen Spitzmüller wrote:
> Makes sense, except for:
>
> > > +AddToPreamble
> > > + \usepackage{comment}
>
> I would rather load the package with
will try
>
> Requirescomment
>
> > > + \...@savsf=1
>
> Why is this needed?
otherwise i get latex error:
"
Bad space factor (0).
\en
Richard Heck wrote:
> Pavel, note that where "comment" appears in that array will determine when
> \usepackage{comments} is output. I don't know if it matters where it goes.
up to know it worked with the documents i tried.
pavel
On 07/13/2009 10:00 AM, Jürgen Spitzmüller wrote:
Pavel Sanda wrote:
ping
Makes sense, except for:
+AddToPreamble
+ \usepackage{comment}
I would rather load the package with
Requirescomment
Yes, that can be done now that we have it in LaTeXFeatures.
Pa
Pavel Sanda wrote:
> ping
Makes sense, except for:
> > +AddToPreamble
> > + \usepackage{comment}
I would rather load the package with
Requirescomment
> > + \...@savsf=1
Why is this needed?
Jürgen
Pavel Sanda wrote:
> Richard Heck wrote:
> > Pavel Sanda wrote:
> >> i see. as there was no feedback i suppose this module will stay locally on
> >> my box, so no additional tweaks needed...
> >>
> >>
> > Actually, I meant to be endorsing it.
>
> is this correct?
ping
> pavel
> commit c5d65f
Richard Heck wrote:
> Pavel Sanda wrote:
>> i see. as there was no feedback i suppose this module will stay locally on
>> my box, so no additional tweaks needed...
>>
>>
> Actually, I meant to be endorsing it.
is this correct?
pavel
commit c5d65f6eb648e7c109530a18128ddc718503facf
Author: Pavel
Pavel Sanda wrote:
i see. as there was no feedback i suppose this module will stay locally on
my box, so no additional tweaks needed...
Actually, I meant to be endorsing it.
rh
pavel
Richard Heck wrote:
>> OK then it is for configure.py, not for lyx.exe. Still, maybe this ought
>> to be parsed by lyx.exe too so why putting that into comments? Richard?
>>
> I'm confused about what you two are discussing.
i understand your confusion - there are more "comments" discussed :)
we w
Abdelrazak Younes wrote:
Pavel Sanda wrote:
Abdelrazak Younes wrote:
The layout format is a LyX internal format, I don't understand why
LyX should parse the comments.
i'm just copying other modules/layouts. if i understand it correctly
the comment is not for lyx binary but for configur
Pavel Sanda wrote:
Abdelrazak Younes wrote:
The layout format is a LyX internal format, I don't understand why LyX
should parse the comments.
i'm just copying other modules/layouts. if i understand it correctly
the comment is not for lyx binary but for configure.py to work.
OK the
Abdelrazak Younes wrote:
> The layout format is a LyX internal format, I don't understand why LyX
> should parse the comments.
i'm just copying other modules/layouts. if i understand it correctly
the comment is not for lyx binary but for configure.py to work.
pavel
Pavel Sanda wrote:
Abdelrazak Younes wrote:
If this is something that will be parsed by LyX, it should not be in
comments.
yes it should :)
Could you please develop?
The layout format is a LyX internal format, I don't understand why LyX
should parse the comments.
Abdel.
Abdelrazak Younes wrote:
> If this is something that will be parsed by LyX, it should not be in
> comments.
yes it should :)
pavel
Pavel Sanda wrote:
hi,
what about adding this into trunk?
If this is something that will be parsed by LyX, it should not be in
comments.
Abdel.
hi,
what about adding this into trunk?
pavel
#\DeclareLyXModule[comment.sty]{Print Comments}
#DescriptionBegin
#Typeset comment notes in LyX. When used with notes-mutate lfun,
#it can be used even for normal LyX notes.
#DescriptionEnd
Format 11
AddToPreamble
\usepackage{comment}
\
22 matches
Mail list logo
