Am 14.11.2010 um 23:01 schrieb Jean-Marc Lasgouttes:
Le 14/11/2010 00:07, Stephan Witt a écrit :
Yes, I know. I've to admit that you're a little bit right, too.
My work-around patch was targeted for 1.6 and 2.0 includes it already.
It was said to make both environments similar... what would
Stephan Witt wrote:
Another question regarding lyx's trac:
I've changed the component of #7035 to version control.
http://www.lyx.org/trac/ticket/7035
After that it's owned by nob...@lyx.org.
Shouldn't it be some real person?
I allocated it to sanda now.
Jürgen
Jürgen Spitzmüller spitz at lyx.org writes:
I've uploaded a tarball here:
ftp://ftp.devel.lyx.org/pub/lyx/devel/lyx-1.6.8.tar.gz
Please give it a try!
With Debian Lenny, and this config:
Host type:i686-pc-linux-gnu
Special build flags: use-aspell
Jean-Pierre Chrétien wrote:
I get these two warnings, which must be harmless I guess:
insets/InsetCitation.cpp: In function ‘lyx::docstring
lyx::unnamed::complexLabel(const lyx::Buffer, const std::string, const
lyx::docstring, const lyx::docstring, const lyx::docstring,
lyx::CiteEngine)’:
This morning I configured lyx beta 1 and start the compilation.
During the course of the compilation it appeared a message of error: segment
violation.
It was trying to read the error message when I noticed that the computer was
hung.
I reset it and now, during the starting, shows an error as if
On Mon, 15 Nov 2010 04:15:39 -0800 (PST)
Marcelo == Marcelo Acuña mv...@yahoo.com.ar wrote:
Marcelo This morning I configured lyx beta 1 and start the compilation.
Marcelo During the course of the compilation it appeared a message of
Marcelo error: segment violation. It was trying to read the
Marcelo Acu?a wrote:
This morning I configured lyx beta 1 and start the compilation.
During the course of the compilation it appeared a message of error: segment
violation.
the only case i have seen such strange messages during compilation of anything
was
when my memory chipset got
Am 15.11.2010 um 13:20 schrieb Gour:
On Mon, 15 Nov 2010 04:15:39 -0800 (PST)
Marcelo == Marcelo Acuña mv...@yahoo.com.ar wrote:
Marcelo This morning I configured lyx beta 1 and start the compilation.
Marcelo During the course of the compilation it appeared a message of
Marcelo error:
Am 15.11.2010 um 13:42 schrieb LyX Ticket Tracker:
#7035: version tracking fails with error in running RCS ci
-+--
Reporter: kuhn | Owner: nob...@…
Type: defect | Status: new
Stephan Witt wrote:
it's not clear which LyX version was used by the ticket creator kuhn
1.6.6
Are you sure?
The LyX-version in ticket is 2.0.0svn... (is it the default?)
sorry, i meant the file is done in 1.6.6. the error is from 2.0.0 of course
pavel
Am 15.11.2010 um 14:00 schrieb Pavel Sanda:
Stephan Witt wrote:
it's not clear which LyX version was used by the ticket creator kuhn
1.6.6
Are you sure?
The LyX-version in ticket is 2.0.0svn... (is it the default?)
sorry, i meant the file is done in 1.6.6. the error is from 2.0.0 of
Stephan Witt wrote:
Stephan Witt wrote:
it's not clear which LyX version was used by the ticket creator kuhn
1.6.6
Are you sure?
The LyX-version in ticket is 2.0.0svn... (is it the default?)
sorry, i meant the file is done in 1.6.6. the error is from 2.0.0 of course
Ok, it
During the course of the compilation it appeared a
message of error: segment violation.
the only case i have seen such strange messages during
compilation of anything was
when my memory chipset got subverted. so maybe time to run
memory check tests...
the only other way i'm aware how
On Mon, 15 Nov 2010 05:27:12 -0800 (PST)
Marcelo == Marcelo Acuña mv...@yahoo.com.ar wrote:
Marcelo My excuses by the false alarm. I am very ashamed for that reason.
No problem. It happens to everyone...we are just curios what has
happened with your cat? ;)
Sincerely,
Gour
--
Gour |
Juergen,
at certain time i would like to switch our web page with translation status
to show trunk state. do you have some preference when?
pavel
Pavel Sanda wrote:
at certain time i would like to switch our web page with translation status
to show trunk state. do you have some preference when?
How about two separate pages for branch and trunk? This would be useful
anyway.
Jürgen
Jürgen Spitzmüller wrote:
Pavel Sanda wrote:
at certain time i would like to switch our web page with translation status
to show trunk state. do you have some preference when?
How about two separate pages for branch and trunk? This would be useful
anyway.
confusing and not needed for
Pavel Sanda wrote:
confusing and not needed for most of the time. but if you want to keep it
for branch there's probably no other solution.
Yes, I prefer to keep it for branch. I don't understand why you find it
confusing.
Jürgen
Jürgen Spitzmüller wrote:
Pavel Sanda wrote:
confusing and not needed for most of the time. but if you want to keep it
for branch there's probably no other solution.
Yes, I prefer to keep it for branch. I don't understand why you find it
confusing.
for people peeping through web the
Pavel Sanda wrote:
for people peeping through web the words like 'trunk' have no meaning.
they just want to know how lyx knows their lang.
We can very well also write Development version (LyX 2.0svn) and Stable
version (LyX 1.6.9svn) instead of branch and trunk. We can grab the
actual version
On 11/13/2010 07:38 PM, Pavel Sanda wrote:
perhaps Richard? - 6733 (LyX allows split environment...)
The only thing that can really be done here now is to try to get rid of
that extra line after \end{split}. I don't know why that is there, as I
don't know the math code at all. But I think it
sa...@lyx.org wrote:
-include($FarmD/cookbook/LyX/i18n.inc);
+if (strpos($_REQUEST['obtain'],'runk'))
+ include($FarmD/cookbook/LyX/i18n_trunk.inc);
+else include($FarmD/cookbook/LyX/i18n.inc);
some PHPist could post correct version of this hack...
p
On 11/14/2010 03:34 AM, Abdel Younes wrote:
Hi Richard,
Just a simple report of the LyXHTML export of the with latest trunk under MacOS
and no LaTeX installed. The export went fine (and instantaneous!). Except for
the expected errors for the pdf and eps to png conversion, I had absolutely no
(apologies if this doesn't go here)
When I backspace to delete the last character of a Lyx document, Lyx goes
away. No graceful shut down, just gone.
It can be started up again fine.
I am running version 1.6.5 of Lyx.
My laptop is running Ubuntu 10.04 ... 64 bit.
I've had some problems with
On 11/15/2010 03:55 PM, Patrick Smith wrote:
(apologies if this doesn't go here)
When I backspace to delete the last character of a Lyx document, Lyx
goes away. No graceful shut down, just gone.
It can be started up again fine.
I am running version 1.6.5 of Lyx.
My laptop is running Ubuntu
Hello
On Mon, Nov 15, 2010 at 9:55 PM, Patrick Smith cha...@gmail.com wrote:
(apologies if this doesn't go here)
When I backspace to delete the last character of a Lyx document, Lyx goes
away. No graceful shut down, just gone.
It can be started up again fine.
I am running version 1.6.5 of
Hah hah! Thanks and praise be to the mighty Lyxialites!
Seriously, thank you. Lyx is pretty awesome - one of those things that seems
so obvious only after you've seen it. And now my package version should keep
pace. Thanks!
Patrick
On Mon, Nov 15, 2010 at 3:01 PM, Liviu Andronic
On Mon, Nov 15, 2010 at 11:20:34AM -0500, Richard Heck wrote:
On 11/13/2010 07:38 PM, Pavel Sanda wrote:
perhaps Richard? - 6733 (LyX allows split environment...)
The only thing that can really be done here now is to try to get rid
of that extra line after \end{split}. I don't know why that
On Mon, Nov 15, 2010 at 10:38:00PM +0100, Enrico Forestieri wrote:
On Mon, Nov 15, 2010 at 11:20:34AM -0500, Richard Heck wrote:
On 11/13/2010 07:38 PM, Pavel Sanda wrote:
perhaps Richard? - 6733 (LyX allows split environment...)
The only thing that can really be done here now is to try
Le 15 nov. 10 à 23:48, Enrico Forestieri a écrit :
See attached patch. This solves the problem of the extra line after
\end{split}, but the code should be audited for other occurrences
of extra newlines.
I think we could also use this method for properly ending math
environments on a new line
On Tue, Nov 16, 2010 at 12:01:59AM +0100, Jean-Marc Lasgouttes wrote:
Le 15 nov. 10 à 23:48, Enrico Forestieri a écrit :
See attached patch. This solves the problem of the extra line after
\end{split}, but the code should be audited for other occurrences
of extra newlines.
I think we could
On Tue, Nov 16, 2010 at 01:09:06AM +0100, Enrico Forestieri wrote:
On Tue, Nov 16, 2010 at 12:01:59AM +0100, Jean-Marc Lasgouttes wrote:
Le 15 nov. 10 à 23:48, Enrico Forestieri a écrit :
See attached patch. This solves the problem of the extra line after
\end{split}, but the code should be
On 11/15/10 7:09 PM, Enrico Forestieri wrote:
On Tue, Nov 16, 2010 at 12:01:59AM +0100, Jean-Marc Lasgouttes wrote:
Le 15 nov. 10 à 23:48, Enrico Forestieri a écrit :
See attached patch. This solves the problem of the extra line after
\end{split}, but the code should be audited for other
On 11/15/10 7:09 PM, Enrico Forestieri wrote:
On Tue, Nov 16, 2010 at 12:01:59AM +0100, Jean-Marc Lasgouttes wrote:
Le 15 nov. 10 à 23:48, Enrico Forestieri a écrit :
See attached patch. This solves the problem of the extra line after
\end{split}, but the code should be audited for other
On Sun, Nov 14, 2010 at 1:23 PM, Jürgen Spitzmüller sp...@lyx.org wrote:
BH wrote:
I take that back. It'll have to be tomorrow. (New computer here, and I
neglected to bring self-compiled Qt-4.4 over from my old one.)
There's no need to hurry, Bennett.
I've put it here:
On Mon, Nov 15, 2010 at 08:41:20PM -0500, Richard Heck wrote:
On 11/15/10 7:09 PM, Enrico Forestieri wrote:
On Tue, Nov 16, 2010 at 12:01:59AM +0100, Jean-Marc Lasgouttes wrote:
Le 15 nov. 10 à 23:48, Enrico Forestieri a écrit :
See attached patch. This solves the problem of the extra line
The attached patch for http://www.lyx.org/trac/ticket/7026 seems to be correct.
The only thing: I don't understand why it should crash with isdigit() instead
of iswdigit()...
Stephan
Index: src/support/lstrings.cpp
===
---
On 11/15/2010 09:47 PM, Richard Heck wrote:
On 11/14/2010 03:34 AM, Abdel Younes wrote:
Hi Richard,
Just a simple report of the LyXHTML export of the with latest trunk
under MacOS and no LaTeX installed. The export went fine (and
instantaneous!). Except for the expected errors for the pdf
Am 14.11.2010 um 23:01 schrieb Jean-Marc Lasgouttes:
> Le 14/11/2010 00:07, Stephan Witt a écrit :
>> Yes, I know. I've to admit that you're a little bit right, too.
>> My work-around patch was targeted for 1.6 and 2.0 includes it already.
>> It was said to make both environments similar... what
Stephan Witt wrote:
> Another question regarding lyx's trac:
> I've changed the component of #7035 to version control.
> http://www.lyx.org/trac/ticket/7035
> After that it's owned by nob...@lyx.org.
> Shouldn't it be some real person?
I allocated it to sanda now.
Jürgen
Jürgen Spitzmüller lyx.org> writes:
>
> I've uploaded a tarball here:
> ftp://ftp.devel.lyx.org/pub/lyx/devel/lyx-1.6.8.tar.gz
>
> Please give it a try!
With Debian Lenny, and this config:
Host type:i686-pc-linux-gnu
Special build flags: use-aspell
Jean-Pierre Chrétien wrote:
> I get these two warnings, which must be harmless I guess:
>
> insets/InsetCitation.cpp: In function ‘lyx::docstring
> lyxcomplexLabel(const lyx::Buffer&, const std::string&, const
> lyx::docstring&, const lyx::docstring&, const lyx::docstring&,
>
This morning I configured lyx beta 1 and start the compilation.
During the course of the compilation it appeared a message of error: segment
violation.
It was trying to read the error message when I noticed that the computer was
hung.
I reset it and now, during the starting, shows an error as if
On Mon, 15 Nov 2010 04:15:39 -0800 (PST)
>> "Marcelo" == Marcelo Acuña wrote:
Marcelo> This morning I configured lyx beta 1 and start the compilation.
Marcelo> During the course of the compilation it appeared a message of
Marcelo> error: segment violation. It was trying
Marcelo Acu?a wrote:
> This morning I configured lyx beta 1 and start the compilation.
> During the course of the compilation it appeared a message of error: segment
> violation.
the only case i have seen such strange messages during compilation of anything
was
when my memory chipset got
Am 15.11.2010 um 13:20 schrieb Gour:
> On Mon, 15 Nov 2010 04:15:39 -0800 (PST)
>>> "Marcelo" == Marcelo Acuña wrote:
>
> Marcelo> This morning I configured lyx beta 1 and start the compilation.
> Marcelo> During the course of the compilation it appeared a message of
>
Am 15.11.2010 um 13:42 schrieb LyX Ticket Tracker:
> #7035: version tracking fails with error in running RCS ci
> -+--
> Reporter: kuhn | Owner: nob...@…
> Type: defect | Status:
Stephan Witt wrote:
> >> it's not clear which LyX version was used by the ticket creator kuhn
> >
> > 1.6.6
>
> Are you sure?
> The LyX-version in ticket is 2.0.0svn... (is it the default?)
sorry, i meant the file is done in 1.6.6. the error is from 2.0.0 of course
pavel
Am 15.11.2010 um 14:00 schrieb Pavel Sanda:
> Stephan Witt wrote:
it's not clear which LyX version was used by the ticket creator kuhn
>>>
>>> 1.6.6
>>
>> Are you sure?
>> The LyX-version in ticket is 2.0.0svn... (is it the default?)
>
> sorry, i meant the file is done in 1.6.6. the
Stephan Witt wrote:
> > Stephan Witt wrote:
> it's not clear which LyX version was used by the ticket creator kuhn
> >>>
> >>> 1.6.6
> >>
> >> Are you sure?
> >> The LyX-version in ticket is 2.0.0svn... (is it the default?)
> >
> > sorry, i meant the file is done in 1.6.6. the error is
> > During the course of the compilation it appeared a
>> message of error: segment violation.
> the only case i have seen such strange messages during
> compilation of anything was
> when my memory chipset got subverted. so maybe time to run
> memory check tests...
>
> the only other way i'm
On Mon, 15 Nov 2010 05:27:12 -0800 (PST)
>> "Marcelo" == Marcelo Acuña wrote:
Marcelo> My excuses by the false alarm. I am very ashamed for that reason.
No problem. It happens to everyone...we are just curios what has
happened with your cat? ;)
Sincerely,
Gour
--
Juergen,
at certain time i would like to switch our web page with translation status
to show trunk state. do you have some preference when?
pavel
Pavel Sanda wrote:
> at certain time i would like to switch our web page with translation status
> to show trunk state. do you have some preference when?
How about two separate pages for branch and trunk? This would be useful
anyway.
Jürgen
Jürgen Spitzmüller wrote:
> Pavel Sanda wrote:
> > at certain time i would like to switch our web page with translation status
> > to show trunk state. do you have some preference when?
>
> How about two separate pages for branch and trunk? This would be useful
> anyway.
confusing and not
Pavel Sanda wrote:
> confusing and not needed for most of the time. but if you want to keep it
> for branch there's probably no other solution.
Yes, I prefer to keep it for branch. I don't understand why you find it
confusing.
Jürgen
Jürgen Spitzmüller wrote:
> Pavel Sanda wrote:
> > confusing and not needed for most of the time. but if you want to keep it
> > for branch there's probably no other solution.
>
> Yes, I prefer to keep it for branch. I don't understand why you find it
> confusing.
for people peeping through web
Pavel Sanda wrote:
> for people peeping through web the words like 'trunk' have no meaning.
> they just want to know how lyx knows their lang.
We can very well also write "Development version (LyX 2.0svn)" and "Stable
version (LyX 1.6.9svn)" instead of "branch" and "trunk". We can grab the
On 11/13/2010 07:38 PM, Pavel Sanda wrote:
perhaps Richard? - 6733 (LyX allows split environment...)
The only thing that can really be done here now is to try to get rid of
that extra line after \end{split}. I don't know why that is there, as I
don't know the math code at all. But I think it
sa...@lyx.org wrote:
>
> -include("$FarmD/cookbook/LyX/i18n.inc");
> +if (strpos($_REQUEST['obtain'],'runk'))
> + include("$FarmD/cookbook/LyX/i18n_trunk.inc");
> +else include("$FarmD/cookbook/LyX/i18n.inc");
some PHPist could post correct version of this hack...
p
On 11/14/2010 03:34 AM, Abdel Younes wrote:
Hi Richard,
Just a simple report of the LyXHTML export of the with latest trunk under MacOS
and no LaTeX installed. The export went fine (and instantaneous!). Except for
the expected errors for the pdf and eps to png conversion, I had absolutely no
(apologies if this doesn't go here)
When I backspace to delete the last character of a Lyx document, Lyx goes
away. No graceful shut down, just gone.
It can be started up again fine.
I am running version 1.6.5 of Lyx.
My laptop is running Ubuntu 10.04 ... 64 bit.
I've had some problems with
On 11/15/2010 03:55 PM, Patrick Smith wrote:
(apologies if this doesn't go here)
When I backspace to delete the last character of a Lyx document, Lyx
goes away. No graceful shut down, just gone.
It can be started up again fine.
I am running version 1.6.5 of Lyx.
My laptop is running Ubuntu
Hello
On Mon, Nov 15, 2010 at 9:55 PM, Patrick Smith wrote:
> (apologies if this doesn't go here)
> When I backspace to delete the last character of a Lyx document, Lyx goes
> away. No graceful shut down, just gone.
> It can be started up again fine.
> I am running version
Hah hah! Thanks and praise be to the mighty Lyxialites!
Seriously, thank you. Lyx is pretty awesome - one of those things that seems
so obvious only after you've seen it. And now my package version should keep
pace. Thanks!
Patrick
On Mon, Nov 15, 2010 at 3:01 PM, Liviu Andronic
On Mon, Nov 15, 2010 at 11:20:34AM -0500, Richard Heck wrote:
> On 11/13/2010 07:38 PM, Pavel Sanda wrote:
> >perhaps Richard? - 6733 (LyX allows split environment...)
> >
> The only thing that can really be done here now is to try to get rid
> of that extra line after \end{split}. I don't know
On Mon, Nov 15, 2010 at 10:38:00PM +0100, Enrico Forestieri wrote:
> On Mon, Nov 15, 2010 at 11:20:34AM -0500, Richard Heck wrote:
> > On 11/13/2010 07:38 PM, Pavel Sanda wrote:
> > >perhaps Richard? - 6733 (LyX allows split environment...)
> > >
> > The only thing that can really be done here now
Le 15 nov. 10 à 23:48, Enrico Forestieri a écrit :
See attached patch. This solves the problem of the extra line after
\end{split}, but the code should be audited for other occurrences
of extra newlines.
I think we could also use this method for properly ending math
environments on a new line
On Tue, Nov 16, 2010 at 12:01:59AM +0100, Jean-Marc Lasgouttes wrote:
> Le 15 nov. 10 à 23:48, Enrico Forestieri a écrit :
> >See attached patch. This solves the problem of the extra line after
> >\end{split}, but the code should be audited for other occurrences
> >of extra newlines.
> >
> >I
On Tue, Nov 16, 2010 at 01:09:06AM +0100, Enrico Forestieri wrote:
> On Tue, Nov 16, 2010 at 12:01:59AM +0100, Jean-Marc Lasgouttes wrote:
> > Le 15 nov. 10 à 23:48, Enrico Forestieri a écrit :
> > >See attached patch. This solves the problem of the extra line after
> > >\end{split}, but the code
On 11/15/10 7:09 PM, Enrico Forestieri wrote:
On Tue, Nov 16, 2010 at 12:01:59AM +0100, Jean-Marc Lasgouttes wrote:
Le 15 nov. 10 à 23:48, Enrico Forestieri a écrit :
See attached patch. This solves the problem of the extra line after
\end{split}, but the code should be audited for other
On 11/15/10 7:09 PM, Enrico Forestieri wrote:
On Tue, Nov 16, 2010 at 12:01:59AM +0100, Jean-Marc Lasgouttes wrote:
Le 15 nov. 10 à 23:48, Enrico Forestieri a écrit :
See attached patch. This solves the problem of the extra line after
\end{split}, but the code should be audited for other
On Sun, Nov 14, 2010 at 1:23 PM, Jürgen Spitzmüller wrote:
> BH wrote:
>> I take that back. It'll have to be tomorrow. (New computer here, and I
>> neglected to bring self-compiled Qt-4.4 over from my old one.)
>
> There's no need to hurry, Bennett.
I've put it here:
On Mon, Nov 15, 2010 at 08:41:20PM -0500, Richard Heck wrote:
> On 11/15/10 7:09 PM, Enrico Forestieri wrote:
> >On Tue, Nov 16, 2010 at 12:01:59AM +0100, Jean-Marc Lasgouttes wrote:
> >>Le 15 nov. 10 à 23:48, Enrico Forestieri a écrit :
> >>>See attached patch. This solves the problem of the
The attached patch for http://www.lyx.org/trac/ticket/7026 seems to be correct.
The only thing: I don't understand why it should crash with isdigit() instead
of iswdigit()...
Stephan
Index: src/support/lstrings.cpp
===
---
On 11/15/2010 09:47 PM, Richard Heck wrote:
On 11/14/2010 03:34 AM, Abdel Younes wrote:
Hi Richard,
Just a simple report of the LyXHTML export of the with latest trunk
under MacOS and no LaTeX installed. The export went fine (and
instantaneous!). Except for the expected errors for the pdf
76 matches
Mail list logo