Am 20.04.2011 um 01:07 schrieb BH:
> On Tue, Apr 19, 2011 at 6:43 PM, Tommaso Cucinotta wrote:
>> I tried this pattern on Linux Ubuntu. I only got this once:
>>
>> lassert.cpp(21): ASSERTION text_.size() <= 2 VIOLATED IN
>> GuiKeySymbol.cpp:673
>> Assertion triggered in void lyx::doAssert(const
Well.
Let's not start the endless discussion of "what's the better OS", right? :-)
However, of course there will be volunteers interested in Windows if you
decide to move to Linux. I'm one of them.
Don't take me wrong about my comment in this thread, and don't feel
responsible because there are bu
On Tue, 19 Apr 2011 21:42:49 -0300
Diego Queiroz wrote:
> I understand Michal, I was already aware of the discussion.
Then you should also understand that unstable/nonexisting installer
is not going to delay LyX release at all (please correct me if I'm
wrong, but that's what I've concluded fr
I understand Michal, I was already aware of the discussion.
The problem is that the normal installer (not the alternative one) isn't so
stable also.
In the present moment, your "alternative nonofficial installer" is the most
stable release for Windows IMO.
---
Diego Queiroz
2011/4/19 Michal Sk
On Tue, Apr 19, 2011 at 6:43 PM, Tommaso Cucinotta wrote:
> I tried this pattern on Linux Ubuntu. I only got this once:
>
> lassert.cpp(21): ASSERTION text_.size() <= 2 VIOLATED IN
> GuiKeySymbol.cpp:673
> Assertion triggered in void lyx::doAssert(const char*, const char*, long
> int) by failing c
Il 20/04/2011 00:29, BH ha scritto:
I've just discovered two bugs on Mac -- one crashing, the other merely annoying.
First the annoying bug:
Start LyX. Close all windows (either with the keyboard or the mouse).
Now (with the keyboard) enterN. This should open a new document;
instead sometimes -
I've just discovered two bugs on Mac -- one crashing, the other merely annoying.
First the annoying bug:
Start LyX. Close all windows (either with the keyboard or the mouse).
Now (with the keyboard) enter N. This should open a new document;
instead sometimes -- not always, but regularly -- my com
Il 20/09/2009 15:10, Tommaso Cucinotta ha scritto:
Just a simple button that creates an empty drawing copying a template
from a folder (and opening an external editor on it) seems really the
right way to go, it would solve your particular problem, it would leave
you with the complete freedom to p
Thanks!
I have filed a bug (#7468) for those cases where there should be
support from the layout file. I believe that the layout was known to
tex2lyx since the created LyX document used formatting that I had
defined in the same layout file.
Marcus
On Tue, 19 Apr 2011 17:03:14 -0300
Diego Queiroz wrote:
> I don't know about others, but the Windows installers are very
> unstable IMO. For example, all unofficial releases that I used until
> now appear to be using incorrect files (lyx1.6 configuration files).
The problem is described in th
On Tue, 19 Apr 2011 16:59:40 -0300
Diego Queiroz wrote:
> I'm not sure of what you said Michal.
> In my experience making a fresh install of LyX (see my previous mail),
> the PATH appear to be really preffixed.
Yes, from your last post to that thread things are clearer now.
Probably the PATH i
> For some reason I don't understand, LyX insert system32 folder
> reference before its own in PATH.
> I have no control over this behavior.
From what you've described, C:\Windows\system32 wasn't already
on the PATH before (I mean 'outside' of LyX). Then this might
exactly be the reason of its
So something moved the Python directory from after the LyX bin directory
(in the LyX prefix) to before it (in the environment in which the script
runs). That's odd.
On 04/19/2011 04:08 PM, Diego Queiroz wrote:
Copied from Tools > Preferences > Paths
C:\Program Files\LyX 2.0rc3\bin
C:\Program
I am trying to support a command with argument for run-in headings: It
produces a small vertical skip without indent and then writes the text
in the argument in a bold font. Is it possible to mimic this behavior
in LyX? I experimented with the "LabelType Manual" directive but could
not get it t
Copied from Tools > Preferences > Paths
C:\Program Files\LyX 2.0rc3\bin
C:\Program Files\Python\Python25
C:\Program Files\MiKTeX 2.9\miktex\bin
C:\Program Files\LyX 2.0rc3\etc\Ghostscript\bin
C:\Program Files\LyX 2.0rc3\etc\ImageMagick-6.6.9-5
C:\Program Files\GIMP-2.0\bin
C:\Program Files\Adobe\A
What is the value of \path_prefix in your LyX preferences file?
Paul
On 04/19/2011 03:51 PM, Diego Queiroz wrote:
Well... I think I wasn't clear. Sorry.
All this information I get *inside* "convertDefault.py".
To get this info, first I changed it to show me the contents of PATH
variable ( os.
I don't know about others, but the Windows installers are very unstable IMO.
For example, all unofficial releases that I used until now appear to be
using incorrect files (lyx1.6 configuration files).
Don't we need to get rid of these problems first?
Cheers,
---
Diego Queiroz
2011/4/18 Pavel
I'm not sure of what you said Michal.
In my experience making a fresh install of LyX (see my previous mail), the
PATH appear to be really preffixed.
So the question should be "Is there some condition that leads LyX don't
insert the PATH in beggining?"
Regards,
---
Diego Queiroz
2011/4/19 Mich
BTW, I created a virtual machine to try to reproduce the scenario in a fresh
Windows install.
Sadly, I wasn't able to reproduce.
Maybe this is happening due to files/configurations/anything left by other
instalations?
Regards,
---
Diego Queiroz
2011/4/19 Diego Queiroz
> Well... I think I wa
Well... I think I wasn't clear. Sorry.
All this information I get *inside* "convertDefault.py".
To get this info, first I changed it to show me the contents of PATH
variable ( os.environ['PATH'] ).
Then, *inside* conventDefault.py, the content of the PATH variable is what I
said.
For some reason
Marcus Kriele wrote:
> I also ran into various problems with tex2lyx when I tried to import
> tex-documents with LaTeX-commands that use required or optional
> arguments and that are supported in the layout. Are such problems well
> known or should I file a bug report?
Such problems are not know
Enrico Forestieri wrote:
> Are you sure it is pointless? runparams is a reference and even if
> it is constant, there are mutable members that could be changed.
> The copy you removed maybe tries to protect against that.
If the mutable members really make a difference then they should not be
mut
I am trying to support a command with argument for run-in headings: It
produces a small vertical skip without indent and then writes the text
in the argument in a bold font. Is it possible to mimic this behavior
in LyX? I experimented with the "LabelType Manual" directive but could
not get i
On 4/18/2011 10:16 PM, Diego Queiroz wrote:
Does someone know why "c:\Windows\System32" is included in the path?
That's standard on Windows systems AFAIK. I'm looking at the path on my
Win XP machine right now, and it has C:\WINDOWS\System32, C:\WINDOWS and
C:\WINDOWS\System32\wbem on the Sy
I haven't checked it myself, but from the recent discussion with
Diego Queiroz I conclude that the name 'PATH prefix' from LyX
preferences is misleading, because it is evident that PATH isn't
prefixed by it.
Instead of changing a name, I'd rather change the behavior of LyX to
really prepen
On Mon, 18 Apr 2011 23:16:01 -0300
Diego Queiroz wrote:
> But when this script is run, my environment variable PATH contains (in
> order):
>
> 1. The path to the temporary folder where the image should be created
> 2. The path of the Python executable
> 3. C:\Windows\System32 (???)
> 4. The valu
Pavel Sanda wrote:
> > Shouldn't it be added to LINGUAS now?
>
> you mean we should add all languages to the tarball?
No, I thought nl is more complete meanwhile. Please ignore if I'm wrong.
Jürgen
Jürgen Spitzmüller wrote:
> Pavel Sanda wrote:
> > > The translation in the output is done by babel, not LyX in this case. I
> > > suppose "Abstract" is simply not yet translated in the dutch po file.
> >
> > even if translated, dutch was in the red region of stripped languages,
> > so you wont f
Pavel Sanda wrote:
> > The translation in the output is done by babel, not LyX in this case. I
> > suppose "Abstract" is simply not yet translated in the dutch po file.
>
> even if translated, dutch was in the red region of stripped languages,
> so you wont find any nl.po in the tarball.
Shouldn
Jürgen Spitzmüller wrote:
> Vincent van Ravesteijn wrote:
> > I now see in the LyX Window "Abstract", but in the exported document
> > "Samenvatting". I guess this must be the same.
>
> The translation in the output is done by babel, not LyX in this case. I
> suppose "Abstract" is simply not yet
Vincent van Ravesteijn wrote:
> I now see in the LyX Window "Abstract", but in the exported document
> "Samenvatting". I guess this must be the same.
The translation in the output is done by babel, not LyX in this case. I
suppose "Abstract" is simply not yet translated in the dutch po file.
Jürg
On 14-4-2011 17:22, sa...@lyx.org wrote:
> Author: sanda
> Date: Thu Apr 14 17:22:15 2011
> New Revision: 38374
> URL: http://www.lyx.org/trac/changeset/38374
>
> Log:
> Add nl.po layout translations (Rick Block, Vincent)
> http://www.mail-archive.com/lyx-users@lists.lyx.org/msg86037.html
>
I n
32 matches
Mail list logo
