On Fri, May 03, 2024 at 02:41:19PM GMT, Jean-Marc Lasgouttes wrote:
> Le 03/05/2024 à 11:56, Jean-Marc Lasgouttes a écrit :
> > I have part of the answer: the slight delay comes from the fact that
> > updateBuffer() is invoked when the selection becomes empty, and since it
> > goes through all
Le 03/05/2024 à 11:56, Jean-Marc Lasgouttes a écrit :
I have part of the answer: the slight delay comes from the fact that
updateBuffer() is invoked when the selection becomes empty, and since it
goes through all documents, this takes some time.
Now I have to find out why.
Fixed in master
Le 22/04/2024 à 20:47, Scott Kostyshak a écrit :
To reproduce:
1. Move the attached file in the lib/docs directory.
2. Open the file.
3. Put the cursor before, e.g., the Additional.lyx include.
4. Press Shift + Down (or Shift + Up).
Result is that there is a small pause before the selection is
On Mon, Apr 22, 2024 at 04:19:33PM GMT, Richard Kimberly Heck wrote:
> On 4/22/24 14:47, Scott Kostyshak wrote:
> > To reproduce:
> >
> > 1. Move the attached file in the lib/docs directory.
> > 2. Open the file.
> > 3. Put the cursor before, e.g., the Additional.lyx include.
> > 4. Press Shift +
On Mon, Apr 22, 2024 at 09:52:56PM GMT, Kornel Benko wrote:
> Am Mon, 22 Apr 2024 14:47:10 -0400
> schrieb Scott Kostyshak :
>
> > To reproduce:
> >
> > 1. Move the attached file in the lib/docs directory.
> > 2. Open the file.
> > 3. Put the cursor before, e.g., the Additional.lyx include.
> >
On 4/22/24 14:47, Scott Kostyshak wrote:
To reproduce:
1. Move the attached file in the lib/docs directory.
2. Open the file.
3. Put the cursor before, e.g., the Additional.lyx include.
4. Press Shift + Down (or Shift + Up).
Result is that there is a small pause before the selection is
Am Mon, 22 Apr 2024 14:47:10 -0400
schrieb Scott Kostyshak :
> To reproduce:
>
> 1. Move the attached file in the lib/docs directory.
> 2. Open the file.
> 3. Put the cursor before, e.g., the Additional.lyx include.
> 4. Press Shift + Down (or Shift + Up).
>
> Result is that there is a small
To reproduce:
1. Move the attached file in the lib/docs directory.
2. Open the file.
3. Put the cursor before, e.g., the Additional.lyx include.
4. Press Shift + Down (or Shift + Up).
Result is that there is a small pause before the selection is finished.
Subsequent presses extending the
On Sat, Oct 24, 2020 at 11:10:47AM +0300, Yuriy Skalko wrote:
> >Dear LyX developers,
> >
> >I just tried to compile LyX (commit
> >2c1753a5265c59ebd11fc465cdb119ff589ad965) on windows 10 with MSVC 2017
> >toolkit, and encountered compiling errors of the sort:
> >
> >
> > src\DocIterator.h(335):
Dear LyX developers,
I just tried to compile LyX (commit
2c1753a5265c59ebd11fc465cdb119ff589ad965) on windows 10 with MSVC 2017
toolkit, and encountered compiling errors of the sort:
src\DocIterator.h(335): error C2039: 'min': is not a member of 'std
and another one about std::isspace.
Dear LyX developers,
I just tried to compile LyX (commit
2c1753a5265c59ebd11fc465cdb119ff589ad965) on windows 10 with MSVC 2017
toolkit, and encountered compiling errors of the sort:
src\DocIterator.h(335): error C2039: 'min': is not a member of 'std
Pavel, please check da8b5de97. Should
Dear LyX developers,
I just tried to compile LyX (commit
2c1753a5265c59ebd11fc465cdb119ff589ad965) on windows 10 with MSVC 2017
toolkit, and encountered compiling errors of the sort:
src\DocIterator.h(335): error C2039: 'min': is not a member of 'std
and another one about std::isspace.
It's
On Wed, Jul 06, 2016 at 09:13:16AM +0200, Stephan Witt wrote:
> Am 05.07.2016 um 18:40 schrieb Pavel Sanda :
> >
> > Guillaume Munch wrote:
> >> I am really curious to know Pavel's configure line given that he uses
> >> gcc. If I could reproduce the problems then I would be able to
Am 05.07.2016 um 18:40 schrieb Pavel Sanda :
>
> Guillaume Munch wrote:
>> I am really curious to know Pavel's configure line given that he uses
>> gcc. If I could reproduce the problems then I would be able to test
>> beforehand more thoroughly when useful.
>
> wrote in the other
Le 05/07/2016 18:40, Pavel Sanda a écrit :
wrote in the other mail, but to be clear i don't expect you to test
all possible gcc or auttools variants before commiting stuff, we have
to live with bugs like that. p
Thank you for your patience.
Guillaume Munch wrote:
> I am really curious to know Pavel's configure line given that he uses
> gcc. If I could reproduce the problems then I would be able to test
> beforehand more thoroughly when useful.
wrote in the other mail, but to be clear i don't expect you to test
all possible gcc or
Le 05/07/2016 00:33, Stephan Witt a écrit :
Am 05.07.2016 um 00:24 schrieb Guillaume Munch :
Le 04/07/2016 12:06, Stephan Witt a écrit :
Hi Guillaume,
now I’m getting: …
Where are we after Pavel's and your changes?
I’m able to build LyX again.
But as Pavel said already:
> Am 05.07.2016 um 00:24 schrieb Guillaume Munch :
>
> Le 04/07/2016 12:06, Stephan Witt a écrit :
>> Hi Guillaume,
>>
>> now I’m getting: …
>>
>
> Where are we after Pavel's and your changes?
I’m able to build LyX again.
But as Pavel said already: a git bisect was nearly
Le 04/07/2016 12:06, Stephan Witt a écrit :
Hi Guillaume,
now I’m getting: …
Where are we after Pavel's and your changes?
Stephan Witt wrote:
> Am 04.07.2016 um 22:35 schrieb Pavel Sanda <sa...@lyx.org>:
> >
> > Guillaume Munch wrote:
> >> commit 670efa8f646218f2a378f0cc614c4c37a9f6b89a
> >> Author: Guillaume Munch <g...@lyx.org>
> >> Date: Sun Jun 19
Am 04.07.2016 um 22:35 schrieb Pavel Sanda <sa...@lyx.org>:
>
> Guillaume Munch wrote:
>> commit 670efa8f646218f2a378f0cc614c4c37a9f6b89a
>> Author: Guillaume Munch <g...@lyx.org>
>> Date: Sun Jun 19 03:39:38 2016 +0100
>>
>>Rationalise incl
Guillaume Munch wrote:
> commit 670efa8f646218f2a378f0cc614c4c37a9f6b89a
> Author: Guillaume Munch <g...@lyx.org>
> Date: Sun Jun 19 03:39:38 2016 +0100
>
> Rationalise includes
>
> Modifying TexRow.h or texstream.h no longer triggers the recompilati
))
> ^~~
>
> Stephan
>
>> Am 04.07.2016 um 02:42 schrieb Guillaume Munch <g...@lyx.org>:
>>
>> commit 670efa8f646218f2a378f0cc614c4c37a9f6b89a
>> Author: Guillaume Munch <g...@lyx.org>
>> Date: Sun Jun 19 03:39:3
h <g...@lyx.org>:
>
> commit 670efa8f646218f2a378f0cc614c4c37a9f6b89a
> Author: Guillaume Munch <g...@lyx.org>
> Date: Sun Jun 19 03:39:38 2016 +0100
>
>Rationalise includes
>
>Modifying TexRow.h or texstream.h no longer triggers the recompil
. Especially gcc was known to pull in many unneeded includes, so it
is good that they reduce them.
> For example, the docs say that the header is required for
> std::count. However, on some sustems, it may happen that some other
> header does include already, so that an explicit loading is
Le 12/06/2016 12:14, Stephan Witt a écrit :
Different structure of headers, just switching between different gcc versions
and their accompanied libs is enough to trigger such errors on the same system.
I’m not used to this behavior with other development environment.
For example, the docs
n
>
>> I have to admit that I start to mistrust the GCC-compilers.
>> I don???t understand why our sources compile on some systems
>> and not on some other systems. Why do I need to add this
>> includes and on your system all is fine?
>
> Different structure
hy do I need to add this
> includes and on your system all is fine?
Different structure of headers, just switching between different gcc versions
and their accompanied libs is enough to trigger such errors on the same system.
Pavel
Am 11.06.2016 um 22:30 schrieb Pavel Sanda <sa...@lyx.org>:
>
> Stephan Witt wrote:
>> commit e8b15b5f0cd216a342dbcaef7b9e90722bc99fc3
>> Author: Stephan Witt <sw...@lyx.org>
>> Date: Sat Jun 11 09:56:35 2016 +0200
>>
>>Add missing includes
Le 11/06/2016 22:30, Pavel Sanda a écrit :
Stephan Witt wrote:
commit e8b15b5f0cd216a342dbcaef7b9e90722bc99fc3
Author: Stephan Witt <sw...@lyx.org>
Date: Sat Jun 11 09:56:35 2016 +0200
Add missing includes after change to boost signals2
diff --git a/src/Server.h b/src/Server.h
Stephan Witt wrote:
> commit e8b15b5f0cd216a342dbcaef7b9e90722bc99fc3
> Author: Stephan Witt <sw...@lyx.org>
> Date: Sat Jun 11 09:56:35 2016 +0200
>
> Add missing includes after change to boost signals2
>
> diff --git a/src/Server.h b/src/Server.h
>
Hi Vincent,
Scott last year moved some template files to the examples folder because they failed with new from
template. That was incorrect, they are still template files and instead of moving they should have
been changed so that LaTeX's xampl.bib file is used as discussed.
To do so, can I
Am 30.03.2014 16:05, schrieb Uwe Stöhr:
To do so, can I revert?:
http://www.lyx.org/trac/changeset/3471874ed09c8b78addb9a5df260379014cab52b/lyxgit
As this only affects documentation files I did this now. I furthermore moved the template file back
that were moved last summer to the examples
Uwe Stöhr schreef op 30-3-2014 17:46:
Am 30.03.2014 16:05, schrieb Uwe Stöhr:
To do so, can I revert?:
http://www.lyx.org/trac/changeset/3471874ed09c8b78addb9a5df260379014cab52b/lyxgit
As this only affects documentation files I did this now.
This stretches the phrase documentation
Am 30.03.2014 20:34, schrieb Vincent van Ravesteijn:
This stretches the phrase documentation update a bit too much to my liking.
OK.
Not only do you update
documentation, you move around a lot of files, you're reverting other's
commits, you mangle
Makefiles and you update the release
Hi Vincent,
Scott last year moved some template files to the examples folder because they failed with "new from
template". That was incorrect, they are still template files and instead of moving they should have
been changed so that LaTeX's xampl.bib file is used as discussed.
To do so, can I
Am 30.03.2014 16:05, schrieb Uwe Stöhr:
To do so, can I revert?:
http://www.lyx.org/trac/changeset/3471874ed09c8b78addb9a5df260379014cab52b/lyxgit
As this only affects documentation files I did this now. I furthermore moved the template file back
that were moved last summer to the examples
Uwe Stöhr schreef op 30-3-2014 17:46:
Am 30.03.2014 16:05, schrieb Uwe Stöhr:
To do so, can I revert?:
http://www.lyx.org/trac/changeset/3471874ed09c8b78addb9a5df260379014cab52b/lyxgit
As this only affects documentation files I did this now.
This stretches the phrase "documentation
Am 30.03.2014 20:34, schrieb Vincent van Ravesteijn:
This stretches the phrase "documentation update" a bit too much to my liking.
OK.
Not only do you update
documentation, you move around a lot of files, you're reverting other's
commits, you mangle
Makefiles and you update the release
On Fri, Mar 28, 2014 at 11:10 PM, Uwe Stöhr uwesto...@web.de wrote:
I bring this topic to the list because this affects a few files.
I think I am to blame here for some files because I used includes (bib-files
and images) for templates like in examples and documentation files. But of
course
2014-03-29 4:10 GMT+01:00 Uwe Stöhr:
I bring this topic to the list because this affects a few files.
I think I am to blame here for some files because I used includes
(bib-files and images) for templates like in examples and documentation
files. But of course this breaks new from template
Am 29.03.2014 09:59, schrieb Jürgen Spitzmüller:
xampl.bib is part of every TeX distro, it is part of BibTeX (the program).
So we should use this for all templates.
Thanks, I will fix the templates accordingly.
As for images, do you really need an image? I think, in most cases,
something
Am 29.03.2014 09:01, schrieb Scott Kostyshak:
There is also Springer and thesis, which I moved from templates to
examples in f5cf21d7.
For examples the includes should not be a problem. You cannot create a new file out of them. You can
instead use them and modify to make it your own document
On Fri, Mar 28, 2014 at 11:10 PM, Uwe Stöhr <uwesto...@web.de> wrote:
> I bring this topic to the list because this affects a few files.
> I think I am to blame here for some files because I used includes (bib-files
> and images) for templates like in examples and docu
2014-03-29 4:10 GMT+01:00 Uwe Stöhr:
> I bring this topic to the list because this affects a few files.
> I think I am to blame here for some files because I used includes
> (bib-files and images) for templates like in examples and documentation
> files. But of course this brea
Am 29.03.2014 09:59, schrieb Jürgen Spitzmüller:
xampl.bib is part of every TeX distro, it is part of BibTeX (the program).
So we should use this for all templates.
Thanks, I will fix the templates accordingly.
As for images, do you really need an image? I think, in most cases,
something
Am 29.03.2014 09:01, schrieb Scott Kostyshak:
There is also Springer and thesis, which I moved from templates to
examples in f5cf21d7.
For examples the includes should not be a problem. You cannot create a new file out of them. You can
instead use them and modify to make it your own document
I bring this topic to the list because this affects a few files.
I think I am to blame here for some files because I used includes (bib-files and images) for
templates like in examples and documentation files. But of course this breaks new from template.
For the future we should add a note
I bring this topic to the list because this affects a few files.
I think I am to blame here for some files because I used includes (bib-files and images) for
templates like in examples and documentation files. But of course this breaks "new from template".
For the future we should
Liviu Andronic landronim...@gmail.com wrote:
On Tue, Jun 26, 2012 at 7:17 PM, Wilfried wrote:
For the _Unix_ version we haven't yet found a better converter as in
rtf2latex2e version 2-0-1. We are experimenting with jodconverter which
in turn uses parts of OpenOffice for the conversion. It
On Wed, Jun 27, 2012 at 9:50 AM, Wilfried wh...@gmx.de wrote:
There is an issue with jodconverter and LibreOffice 3.5, see
http://code.google.com/p/jodconverter/issues/detail?id=103
but the author of jodconverter does not maintain it any longer and waits
for someone to fork and maintain it,
On Wed, Jun 27, 2012 at 9:50 AM, Wilfried wh...@gmx.de wrote:
There is an issue with jodconverter and LibreOffice 3.5, see
http://code.google.com/p/jodconverter/issues/detail?id=103
What about 'unoconv' [1], another cross-platform LibreOffice-based
converter. The programme has seen a recent
(This is a copy of the further discussion with Liviu by personal mail.)
Liviu Andronic wrote:
On Wed, Jun 27, 2012 at 9:50 AM, Wilfried wrote:
There is an issue with jodconverter and LibreOffice 3.5, see
http://code.google.com/p/jodconverter/issues/detail?id=103
What about 'unoconv' [1],
(This is a copy of the further discussion with Liviu by personal mail.)
Wilfried wrote:
1. If we need OpenOffice as helper app for rtf2latex2e, we could do the
conversion completely with OOo and don't need rtf2latex2e at all.
So - does it make sense to use OOo as helper for rtf2latex2e? In my
Liviu Andronic wrote:
> On Tue, Jun 26, 2012 at 7:17 PM, Wilfried wrote:
> > For the _Unix_ version we haven't yet found a better converter as in
> > rtf2latex2e version 2-0-1. We are experimenting with jodconverter which
> > in turn uses parts of OpenOffice for the
On Wed, Jun 27, 2012 at 9:50 AM, Wilfried wrote:
> There is an issue with jodconverter and LibreOffice 3.5, see
> http://code.google.com/p/jodconverter/issues/detail?id=103
> but the author of jodconverter does not maintain it any longer and waits
> for someone to fork and maintain
On Wed, Jun 27, 2012 at 9:50 AM, Wilfried wrote:
> There is an issue with jodconverter and LibreOffice 3.5, see
> http://code.google.com/p/jodconverter/issues/detail?id=103
>
What about 'unoconv' [1], another cross-platform LibreOffice-based
converter. The programme has seen a
(This is a copy of the further discussion with Liviu by personal mail.)
Liviu Andronic wrote:
> On Wed, Jun 27, 2012 at 9:50 AM, Wilfried wrote:
> > There is an issue with jodconverter and LibreOffice 3.5, see
> > http://code.google.com/p/jodconverter/issues/detail?id=103
> >
> What about
(This is a copy of the further discussion with Liviu by personal mail.)
Wilfried wrote:
> 1. If we need OpenOffice as helper app for rtf2latex2e, we could do the
> conversion completely with OOo and don't need rtf2latex2e at all.
> So - does it make sense to use OOo as helper for rtf2latex2e? In
Hello all,
as I am maintaining the Windows port of rtf2latex2e,
I was glad to find the Metafile to EPS converter at
http://wiki.lyx.org/Windows/MetafileToEPSConverter
and as that page sais it's under GPL, I decided to include it in the
rtf2latex2e distribution.
Please let me know whether there are
Wilfried wrote:
Hello all,
as I am maintaining the Windows port of rtf2latex2e,
I was glad to find the Metafile to EPS converter at
http://wiki.lyx.org/Windows/MetafileToEPSConverter
and as that page sais it's under GPL, I decided to include it in the
rtf2latex2e distribution.
Please let me
Hello,
some clarification.
The previous _Windows_ version of rtf2latex2e could only convert wmf,
not emf graphics. As the LyX metafile2eps converter converts both, I
think it's worth to switch to the new _Windows_ version.
For the _Unix_ version we haven't yet found a better converter as in
On Tue, Jun 26, 2012 at 7:17 PM, Wilfried wh...@gmx.de wrote:
For the _Unix_ version we haven't yet found a better converter as in
rtf2latex2e version 2-0-1. We are experimenting with jodconverter which
in turn uses parts of OpenOffice for the conversion. It works with some
versions of
+0200
removed unused includes
these files don't use the debug.h and also don't contain commented out
debug code
Please revert this.
It makes debugging via lyxerr twice as hard.
Pavel
Hello all,
as I am maintaining the Windows port of rtf2latex2e,
I was glad to find the Metafile to EPS converter at
http://wiki.lyx.org/Windows/MetafileToEPSConverter
and as that page sais it's under GPL, I decided to include it in the
rtf2latex2e distribution.
Please let me know whether there are
Wilfried wrote:
> Hello all,
> as I am maintaining the Windows port of rtf2latex2e,
> I was glad to find the Metafile to EPS converter at
> http://wiki.lyx.org/Windows/MetafileToEPSConverter
> and as that page sais it's under GPL, I decided to include it in the
> rtf2latex2e distribution.
> Please
Hello,
some clarification.
The previous _Windows_ version of rtf2latex2e could only convert wmf,
not emf graphics. As the LyX metafile2eps converter converts both, I
think it's worth to switch to the new _Windows_ version.
For the _Unix_ version we haven't yet found a better converter as in
On Tue, Jun 26, 2012 at 7:17 PM, Wilfried wrote:
> For the _Unix_ version we haven't yet found a better converter as in
> rtf2latex2e version 2-0-1. We are experimenting with jodconverter which
> in turn uses parts of OpenOffice for the conversion. It works with some
> versions of
t; Date: Tue Jun 26 22:41:53 2012 +0200
>
> removed unused includes
>
> these files don't use the debug.h and also don't contain commented out
> debug code
Please revert this.
It makes debugging via lyxerr<< twice as hard.
Pavel
The attached patch is an attempt to get a real start on fixing problems
with recursive includes. As you'll note, there are a couple places I
know still crash, but I wanted to see if anyone had a better idea. On
this approach, we basically have to make sure we NEVER try to recurse
via Buffer
Am 30.09.2010 um 19:03 schrieb Richard Heck:
The attached patch is an attempt to get a real start on fixing problems with
recursive includes. As you'll note, there are a couple places I know still
crash, but I wanted to see if anyone had a better idea. On this approach, we
basically have
Stephan Witt wrote:
There is a cool algorithm to detect infinite loops without global state:
Use two pointers, start both somewhere at the same point.
Increment the first by one, the second by two (if not hitting the end), until
one of the conditions is true:
1. Stop if one of the pointers
Pavel Sanda wrote:
there is a slight complication that we can branch in each document... so
either we have towards beginning or send pointer messenger in all possible
branches...
actually whats the depth where lyx crashes...? i guess thats posing maximum
depth for, say, 100 is enough for any
is
information about the overall structure, who is whose parent, etc. We
basically reconstruct that over and over again, which isn't so bad if
recursive includes aren't an issue but becomes serious when they are,
because, in that case, what structure the thing seems to have depends
upon where
Le 30/09/2010 23:03, Richard Heck a écrit :
It's not so much detecting the recursion. It's what to do about it once
you detect it. So, say, we have: A - B - A. What should
B.masterBuffer() return? What should A.masterBuffer() return? How do you
safely write recursions?
I would say the second A
something stable.
Maybe the place to do this is in Buffer::setParent(). I.e., every time
we are asked to set a parent, we check for recursive includes and refuse
to set it if doing saw causes recursion.
Of course, we'd like to accept:
A-B
\C-B
where B is inserted twice
something stable.
Maybe the place to do this is in Buffer::setParent(). I.e., every time
we are asked to set a parent, we check for recursive includes and refuse
to set it if doing saw causes recursion.
Of course, we'd like to accept:
A-B
\C-B
where B is inserted twice
The attached patch is an attempt to get a real start on fixing problems
with recursive includes. As you'll note, there are a couple places I
know still crash, but I wanted to see if anyone had a better idea. On
this approach, we basically have to make sure we NEVER try to recurse
via Buffer
Am 30.09.2010 um 19:03 schrieb Richard Heck:
>
> The attached patch is an attempt to get a real start on fixing problems with
> recursive includes. As you'll note, there are a couple places I know still
> crash, but I wanted to see if anyone had a better idea. On this approach, we
Stephan Witt wrote:
> There is a cool algorithm to detect infinite loops without global state:
>
> Use two pointers, start both somewhere at the same point.
> Increment the first by one, the second by two (if not hitting the end), until
> one of the conditions is true:
> 1. Stop if one of the
Pavel Sanda wrote:
> there is a slight complication that we can branch in each document... so
> either we have towards beginning or send pointer messenger in all possible
> branches...
actually whats the depth where lyx crashes...? i guess thats posing maximum
depth for, say, 100 is enough for
each Buffer, whereas what we seem to need here is
information about the overall structure, who is whose parent, etc. We
basically reconstruct that over and over again, which isn't so bad if
recursive includes aren't an issue but becomes serious when they are,
because, in that case, what structu
Le 30/09/2010 23:03, Richard Heck a écrit :
It's not so much detecting the recursion. It's what to do about it once
you detect it. So, say, we have: A -> B -> A. What should
B.masterBuffer() return? What should A.masterBuffer() return? How do you
safely write recursions?
I would say the second
B->A. We want something stable.
Maybe the place to do this is in Buffer::setParent(). I.e., every time
we are asked to set a parent, we check for recursive includes and refuse
to set it if doing saw causes recursion.
Of course, we'd like to accept:
A->B
\>C->B
wher
B->A. We want something stable.
Maybe the place to do this is in Buffer::setParent(). I.e., every time
we are asked to set a parent, we check for recursive includes and refuse
to set it if doing saw causes recursion.
Of course, we'd like to accept:
A->B
\>C->B
wher
Stephan Witt wrote:
This is LyX 2.0.0 on Linux running in place without having TeX installed.
Should this be fixed?
are there some bad consequences?
Not visible. But I'm a little bit nervous when arbitrary shell commands gets
executed.
I have no time to investigate and it seems to
Stephan Witt wrote:
> >> This is LyX 2.0.0 on Linux running in place without having TeX installed.
> >> Should this be fixed?
> >
> > are there some bad consequences?
>
> Not visible. But I'm a little bit nervous when arbitrary shell commands gets
> executed.
> I have no time to investigate and
This one I can see in output of reconfigure!
...
+checking for xsltproc... yes
sh: \nonstopmode\input{a b}: Kommando nicht gefunden.
Checking whether TeX allows spaces in file names... no
...
This is LyX 2.0.0 on Linux running in place without having TeX installed.
Should this be fixed?
Stephan
Stephan Witt wrote:
This is LyX 2.0.0 on Linux running in place without having TeX installed.
Should this be fixed?
are there some bad consequences?
pavel
Am 30.08.2010 um 01:08 schrieb Pavel Sanda:
Stephan Witt wrote:
This is LyX 2.0.0 on Linux running in place without having TeX installed.
Should this be fixed?
are there some bad consequences?
Not visible. But I'm a little bit nervous when arbitrary shell commands gets
executed.
I have no
This one I can see in output of reconfigure!
...
+checking for "xsltproc"... yes
sh: \nonstopmode\input{"a b"}: Kommando nicht gefunden.
Checking whether TeX allows spaces in file names... no
...
This is LyX 2.0.0 on Linux running in place without having TeX installed.
Should this be fixed?
Stephan Witt wrote:
> This is LyX 2.0.0 on Linux running in place without having TeX installed.
> Should this be fixed?
are there some bad consequences?
pavel
Am 30.08.2010 um 01:08 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> This is LyX 2.0.0 on Linux running in place without having TeX installed.
>> Should this be fixed?
>
> are there some bad consequences?
Not visible. But I'm a little bit nervous when arbitrary shell commands gets
executed.
I
Hello,
I just saw that LyX does not seem to support more than one level of nested
include files (Insert-File-Child Document).
I was surprised to get a compile time error and not an error when I try to
include a child document in a file which is included in a (referenced) master
document. Or
2010/6/28 Rainer Dorsch:
I just saw that LyX does not seem to support more than one level of nested
include files (Insert-File-Child Document).
LaTeX only supports one level with \include. LyX is restricted to what
LaTeX allows. OTOH, nesting is allowed with \input (and LyX is
supposed to
Am Monday 28 June 2010 15:26:07 schrieb Jürgen Spitzmüller:
2010/6/28 Rainer Dorsch:
I just saw that LyX does not seem to support more than one level of
nested include files (Insert-File-Child Document).
LaTeX only supports one level with \include. LyX is restricted to what
LaTeX allows.
Hello,
I just saw that LyX does not seem to support more than one level of nested
include files (Insert->File->Child Document).
I was surprised to get a compile time error and not an error when I try to
include a child document in a file which is included in a (referenced) master
document. Or
2010/6/28 Rainer Dorsch:
> I just saw that LyX does not seem to support more than one level of nested
> include files (Insert->File->Child Document).
LaTeX only supports one level with \include. LyX is restricted to what
LaTeX allows. OTOH, nesting is allowed with \input (and LyX is
supposed to
Am Monday 28 June 2010 15:26:07 schrieb Jürgen Spitzmüller:
> 2010/6/28 Rainer Dorsch:
> > I just saw that LyX does not seem to support more than one level of
> > nested include files (Insert->File->Child Document).
>
> LaTeX only supports one level with \include. LyX is restricted to what
> LaTeX
LyX Ticket Tracker t...@puben.org writes:
Changes (by uwestoehr):
* keywords: crash fixedintrunk fixedinbranch =
* status: reopened = closed
* resolution: = fixed
Uwe,
Why do you reset the keywords? While I can understand that fixedintrunk
and fixedinbranch are not necessary
1 - 100 of 249 matches
Mail list logo