Pavel Sanda wrote:
> ooops sorry Juergen, committing from a wrong tree. i can revert if you
> want me.
No, it's OK.
Jürgen
On 11/11/2009 08:56 PM, Uwe Stöhr wrote:
Uwe Stöhr schrieb:
No it is not. What we have now in branch doesn't work. The correct
solution is http://www.lyx.org/trac/changeset/31949.
Here's the patch for branch that also works on Windows, please test.
This patch contains the bug Alex reported,
On 11/11/2009 08:30 PM, Uwe Stöhr wrote:
rgheck schrieb:
These two patches take different approaches to solving the same
problem. Alex's is correct, so I am committing it to trunk, too.
This solution didn't work on Windows, see my email in the actual
configure.py thread.
And your solution
Uwe Stöhr schrieb:
No it is not. What we have now in branch doesn't work. The correct
solution is http://www.lyx.org/trac/changeset/31949.
Here's the patch for branch that also works on Windows, please test.
regards Uwe
Index: configure.py
=
rgheck schrieb:
These two patches take different approaches to solving the same problem.
Alex's is correct, so I am committing it to trunk, too.
This solution didn't work on Windows, see my email in the actual configure.py
thread.
Pavel, as he said, accidentally committed it to branch, too,
rgheck schrieb:
The bigger problem is that I don't have elyxer on this machine. What's
happening is that configure.py has this:
path, elyxer = checkProg('a LyX -> HTML converter', ['elyxer.py',
'elyxer'],
rc_entry = [ r'\converter lyx html "python -tt elyxer.py --directory $$r
$$i $$o" ""'
On 11/10/2009 09:28 AM, Jean-Marc Lasgouttes wrote:
rgheck writes:
Richard, it is nice to see you working on that. One thing that would be
nice is to be able to have the graph depend on the document, or rather
of its class: this would allow to handle unsupported classes, which can
currently
On 11/11/2009 06:51 PM, rgheck wrote:
On 11/11/2009 06:38 PM, rgheck wrote:
The problem with the code is that we should NOT be refusing to check
for LaTeX-->HTML converters simply because we have found a LyX-->HTML
converter.
And by the way, not detecting LaTeX-->HTML converters as a way of
On 11/11/2009 06:38 PM, rgheck wrote:
There's still a problem, at least in trunk, with the elyxer detection
code, though the actual bug, I think, is somewhere else.
The problem with the code is that we should NOT be refusing to check
for LaTeX-->HTML converters simply because we have found a
There's still a problem, at least in trunk, with the elyxer detection
code, though the actual bug, I think, is somewhere else.
The problem with the code is that we should NOT be refusing to check for
LaTeX-->HTML converters simply because we have found a LyX-->HTML
converter. Once we have th
On Wed, Nov 11, 2009 at 6:09 PM, Gregory Jefferis wrote:
> I believe I have built LyX branch (1.6.5svn) using system installed Qt 4.4.1
> by using cmake + Xcode. See INSTALL.cmake for details - there is an
> Xcode/Mac section.
A question about this: does it produce a LyX binary that will run on
On 11/11/2009 06:18 PM, rgheck wrote:
On 11/11/2009 06:04 PM, Pavel Sanda wrote:
or try html:
instead of my html2latex i see something like dvi processing
happening and then some
binary code presented in firefox
Yes, I see the problem. Surely an issue with Graph.*. I'll fix it.
I think
Dear Jean-Marc and Bennett,
On 2009-11-11 20:25, "BH" wrote:
> I've posted a binary here:
>
> http://edisk.fandm.edu/bennett.helm/lyx/LyX-Snow-Leopard-Test2.app.zip
Many thanks for the patch and binary, respectively. I have tried Bennett's
binary without trouble on Leopard (edit, save, autosav
On 11/11/2009 06:04 PM, Pavel Sanda wrote:
or try html:
instead of my html2latex i see something like dvi processing happening and then
some
binary code presented in firefox
Yes, I see the problem. Surely an issue with Graph.*. I'll fix it.
Richard
These two patches take different approaches to solving the same problem.
Alex's is correct, so I am committing it to trunk, too.
Pavel, as he said, accidentally committed it to branch, too, but it is OK.
Richard
On 2009-11-11 20:47, "Anders Ekberg" wrote:
>> (b) built LyX for Mac using system wide, dynamically linked Qt libraries (as
>> installed by the Qt installer), rather than a custom-built-from-source static
>> library? If not, is there any reason other than limitations of the build
>> system?
> The
On Wed, Nov 11, 2009 at 11:23:29PM +0100, Alex Fernandez wrote:
>
> Ticket 6317 was created, the patches have also been attached there.
yep, that fixed it, thanks.
Richard, trunk seems to be broken as far viewing is concerned now and i guess
graphc.cpp
could be indeed related:
just new file, t
On Wed, Nov 11, 2009 at 11:32:39PM +0100, sa...@lyx.org wrote:
> Author: sanda
> Date: Wed Nov 11 23:32:38 2009
> New Revision: 31948
> URL: http://www.lyx.org/trac/changeset/31948
>
> Log:
> Fix elyxer detection. Patch from Alex Fernandez.
> Uwe, please check this works on Windows.
> http://www.m
On Wed, Nov 11, 2009 at 04:24:17PM -0500, rgheck wrote:
> I don't see the problems with the export or view menu in current trunk
...
> I do know why you're seeing the other error message, though. Since LyX
> thinks it can't export LaTeX directly---as JMarc has said, it actually
> could, just not
On Wed, Nov 11, 2009 at 11:00 PM, Pavel Sanda wrote:
> i double checked this and couldn't find such a thing.
> maybe the "-tt scripts/" is added somewhere else in the code.
Nope, it is right there in trunk:
http://www.lyx.org/trac/browser/lyx-devel/trunk/lib/configure.py#L623
With this patch it
On Wed, Nov 11, 2009 at 10:31:52PM +0100, Uwe Stöhr wrote:
> I cannot reproduce this.
> But I can reproduce a crash when opening the attached LyX file with LyX
> 2.0svn. When you export this file as LaTeX (plain) LyX crashes immediately
> without any console message.
> Do you also see this?
conf
On Wed, Nov 11, 2009 at 10:31:52PM +0100, Uwe Stöhr wrote:
> python -tt scripts/elyxer.py
> was the old entry that I replaced in branch and trunk in configure.py. It
> seems that you have an old copy of configure.py somewhere on your system.
i double checked this and couldn't find such a thing.
m
On Wed, Nov 11, 2009 at 04:24:17PM -0500, rgheck wrote:
resending again, some problem with emails coming from my ISP just now :)
> I don't see the problems with the export or view menu in current trunk
> or branch (just updated). It's still possible I broke something with the
> Graph.* changes,
2009/11/11 Pavel Sanda :
> i guess there is something fishy in the way we detect elyxer.
I wouldn't argue with that ;) By the way, trunk sure is missing the
fix that Uwe committed to branch. Please find it attached -- it uses
eLyXer as a module or as an executable file, whatever is found (and
not
rgheck schrieb:
i'm afraid we have broken something wrt configure workings.
when i open the document which has uninstalled latex class,
export and view menu is errorneusly filled "inaccesible" items.
I cannot reproduce this.
But I can reproduce a crash when opening the attached LyX file with L
On 11/11/2009 01:35 PM, Pavel Sanda wrote:
hi,
i'm afraid we have broken something wrt configure workings.
when i open the document which has uninstalled latex class,
export and view menu is errorneusly filled "inaccesible" items.
moreover when i do export->plain latex i see error messages:
/u
On 9 nov 2009, at 22.49, Hugo Vincent wrote:
> I asked this previously, but got no response.
>
> Has anyone:
> (a) got LyX to build as 64-bit on Snow Leopard? or
Not that I know of. I got it to build as 32 bit (didn't try 64 since QT only
compiled for 32 bit for me). But right now my system's go
On 11 nov 2009, at 21.25, BH wrote:
> On Wed, Nov 11, 2009 at 2:46 PM, Anders Ekberg wrote:
>
>> Bennett,
>>
>> Something is very wrong with my system (compiling crashes and sometimes
>> locks the entire OS, which is why I haven't mitigated the patch for
>> INSTALL.MacOSX yet). So I can't com
On 11/11/2009 01:35 PM, Pavel Sanda wrote:
hi,
i'm afraid we have broken something wrt configure workings.
when i open the document which has uninstalled latex class,
export and view menu is errorneusly filled "inaccesible" items.
moreover when i do export->plain latex i see error messages:
/u
On Wed, Nov 11, 2009 at 2:46 PM, Anders Ekberg wrote:
> Bennett,
>
> Something is very wrong with my system (compiling crashes and sometimes locks
> the entire OS, which is why I haven't mitigated the patch for INSTALL.MacOSX
> yet). So I can't compile it. But if you can mail me a binary I can
On 11 nov 2009, at 20.29, BH wrote:
> On Wed, Nov 11, 2009 at 2:23 PM, BH wrote:
>> On Wed, Nov 11, 2009 at 12:47 PM, Jean-Marc Lasgouttes
>> wrote:
Sure it is. But I do not have much time to spend in front of a mac :(
>>>
>>> OK, here is a new patch that applies to branch (replaces nofork
On Wed, Nov 11, 2009 at 2:23 PM, BH wrote:
> On Wed, Nov 11, 2009 at 12:47 PM, Jean-Marc Lasgouttes
> wrote:
>>> Sure it is. But I do not have much time to spend in front of a mac :(
>>
>> OK, here is a new patch that applies to branch (replaces nofork2).
>>
>> Could some kind mac users (and othe
On Wed, Nov 11, 2009 at 12:47 PM, Jean-Marc Lasgouttes
wrote:
>> Sure it is. But I do not have much time to spend in front of a mac :(
>
> OK, here is a new patch that applies to branch (replaces nofork2).
>
> Could some kind mac users (and others) try it out? I am running out of time.
>
> The par
hi,
i'm afraid we have broken something wrt configure workings.
when i open the document which has uninstalled latex class,
export and view menu is errorneusly filled "inaccesible" items.
moreover when i do export->plain latex i see error messages:
/usr/bin/python2.6: can't open file 'scripts/el
Le 25 oct. 09 à 09:42, Gyorgy SZEIDL a écrit :
After installation I made an attempt at importing some standard
LaTeX documents as LaTeX (plain) files created by WinEdt. I failed
in each case by receiving the following error message:
tex2lyx.exe has encountered a problem and needs to close. W
Sure it is. But I do not have much time to spend in front of a mac :(
OK, here is a new patch that applies to branch (replaces nofork2).
Could some kind mac users (and others) try it out? I am running out of
time.
The part in ForkedCalls should be applied anyway I think.
The autosave part
On Wednesday 11 November 2009 09:01:55 Sebastian Guttenberg wrote:
> > Your test exmaple is quite striking, as the latex file asks explicitly
> > for Type 1 fonts and the pdf output has Type 3 fonts :-(
> >
> > If you cretae pdf docs for others using ps2pdf, you will be better with
> > embedded fon
> Your test exmaple is quite striking, as the latex file asks explicitly for
> Type
> 1 fonts and the pdf output has Type 3 fonts :-(
>
> If you cretae pdf docs for others using ps2pdf, you will be better with
> embedded
> fonts as well. I have added an entry in the pdf FAQ about this in the wik
Sebastian Guttenberg writes:
>
> Well, it's one thing to optimize a file for the pdf-output and another
> that I am working usually with dvi and ps, but from time to time need
> to produce a pdf-version of it to somebody (who might use acroread on
> windows). It cannot be that the standard output
On 2009-11-10, Helge Hafting wrote:
> Enrico Forestieri wrote:
>>> ... Besides this, mhchem is our third package that is
>>> automatically loaded when formulas are edited.
More are automatically added by Unicode conversion.
We might need some package selection/deselection scheme for these too.
40 matches
Mail list logo
