Martin Vermeer a écrit :
On Sat, Apr 22, 2006 at 11:22:53AM +0200, Abdelrazak Younes wrote:
Michael Gerz a écrit :
[EMAIL PROTECTED] wrote:
...
Martin,
as you (as well as many others) want the outlining stuff to go into
1.4.X: Did you keep track of all the patches that were committed afte
On Sat, Apr 22, 2006 at 11:22:53AM +0200, Abdelrazak Younes wrote:
> Michael Gerz a écrit :
> >[EMAIL PROTECTED] wrote:
...
> >Martin,
> >
> >as you (as well as many others) want the outlining stuff to go into
> >1.4.X: Did you keep track of all the patches that were committed after
> >the init
On Sat, Apr 22, 2006 at 06:42:53PM -0500, Garst R. Reese wrote:
> Martin Vermeer wrote:
>
> >On Thu, Apr 20, 2006 at 10:28:51PM -0500, Garst R. Reese wrote:
> >
> >
> >>Martin Vermeer wrote:
> >>
> >>
> >I don't agree. You're right in that the only place where a
> >_correspondence_ is defined
Dear developers,
Attached is a complete patch that, under windows,
1. configure.py generates "auto" as viewers.
2. when no user specified viewer exists, the default viewer through
windows ShellExecute will be used.
Windows users will never again need to worry about viewers.
Will be applied to
SH: A new winlyx user should have 1.3.7 installed.
I think that will avoid most of the problems
you mentioned at least it does for me.
Bo: I did not experience these problems with Uwe's
1.3.7 installer, but that was for user accounts with
administrative privilege. Maybe this made a big difference
Is anyone looking at this problem?
Do a "make dist" and try to use the tarball. You won't succeed, since
lyx2lyx_version.py is not there.
- Forwarded message from "Kayvan A. Sylvan" <[EMAIL PROTECTED]> -
Date: Mon, 17 Apr 2006 22:54:13 -0700
From: "Kayvan A. Sylvan" <[EMAIL PROTECTED]>
T
Martin Vermeer wrote:
On Thu, Apr 20, 2006 at 10:28:51PM -0500, Garst R. Reese wrote:
Martin Vermeer wrote:
I don't agree. You're right in that the only place where a
_correspondence_ is defined between the old numerical parameters and the
new character ones is, precisely, lyx2lyx. And
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> > scp mylyx.exe [EMAIL PROTECTED]:.
> > ssh [EMAIL PROTECTED]
>
> Hi Angus, the addresses got mixed up by gmane could you repost that please?
Lars, the guy who was so keen that we do this encryption nonsense has been long
gone for ever and ever. Can
Paul A. Rubin <[EMAIL PROTECTED]> writes:
> Is there a reason why it's now named tex2lyx.1.4.x.exe,
Yes.
I wanted LyX 1.3.x to work alongside LyX 1.4. LyX 1.3.7 is the most stable
version of LyX ever. LyX 1.4.1 isn't...
By configuring the build process "--with-version-suffix" I ensured that our
On 4/22/06, Chunpeng Yan <[EMAIL PROTECTED]> wrote:
> Can someone please look at the simple equation in attached the file?
> lyx1.4.1 for windows crashes when View->DVI. No such a problem for
> lyx1.3.7 windows.
I can confirm this under windows (1.5.xsvn), but not linux (where I do
not have ieee t
Angus Leeming a écrit :
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
I can put an experimental windows executable on the web if there's
interest. I use it myself and it's stable enough.
http://wiki.lyx.org/Windows/LyX150_experimental ?
I shove executables into the equivalent location in the
Can someone please look at the simple equation in attached the file?
lyx1.4.1 for windows crashes when View->DVI. No such a problem for
lyx1.3.7 windows.
lyx141_test_1.lyx
Description: application/lyx
Enrico Forestieri wrote:
I've added a bullet on the Windows installation tips wiki page
(http://wiki.lyx.org/Windows/LyX14x) with the hard link work-around for now.
I suggest that you change "ln" to "mv" as it is simply a waste of disk
space leaving around tex2lyx1.4.x.exe (if "ln" simply ma
Jean-Marc Lasgouttes a écrit :
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Abdelrazak Younes a écrit :
I'll put it in later today if there's no objection in the mean
time.
Abdelrazak> Done. Weird that my patches do not generate heated
Abdelrazak> discussions any
Ouch, I have to confess I use --disable-concept-check, it dates back to
my first attempt to compile under windows and I never changed that. I
don't even know what exactly it does. I have checked in a fix that
should enable you to compile. I am going to reconfigure with
enable-concept-check to v
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Not really. The .layout files are a separate problem (because
Georg> just including them is not enough). For the other files I would
Georg> use a very simple rule: Don't include anything that can be
Georg> found via TEXMF, only include
On 4/22/06, Abdelrazak Younes <[EMAIL PROTECTED]> wrote:
> Abdelrazak Younes a écrit :
> > I'll put it in later today if there's no objection in the mean time.
>
> Done.
> Weird that my patches do not generate heated discussions anymore... I am
> wondering if they are just not interesting... or may
> "Bo" == Bo Peng <[EMAIL PROTECTED]> writes:
>> I could probably help here (I am not considering myself a qt newbie
>> anymore :-) ) but it would sure be better if you'd like to learn
>> ;-)
Bo> Because of the license problem, I chose wxWidget and wxPython for
Bo> my GUI needs. Now, I still
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Abdelrazak Younes a écrit :
>> I'll put it in later today if there's no objection in the mean
>> time.
Abdelrazak> Done. Weird that my patches do not generate heated
Abdelrazak> discussions anymore... I am wondering i
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Jean-Marc Lasgouttes wrote:
>> Georg, do you have a patch for 1.4? I'll look at it next week,
>> along with several excellent patches that I saw floating around
>> this week.
Georg> You mean one for using comfigure.py in 1.4, or one t
Bo Peng <[EMAIL PROTECTED]> writes:
> Please advise on a good place to put an openFile(filename,
> mode=view/edit, command="", parameter="") function.
src/support/filetools.[Ch]
Angus
Enrico Forestieri <[EMAIL PROTECTED]> writes:
> It is much like the fact that when inserting a graphic only file names
> with a given extension are shown in the graphics inset. But I can name
> foo.myfig an xfig file and have it correctly recognized by gnome and
> kde--but not LyX!
We have our own
> It may work but there's no way that core code
> should contain #ifdef WIN32 blocks. You should
> add a function to lyx::support.
Please advise on a good place to put an openFile(filename,
mode=view/edit, command="", parameter="") function.
Bo
On Sat, Apr 22, 2006 at 02:26:32PM -0500, Bo Peng wrote:
> > I am concerned about being able to recognize a .lyx file, as there is
> > software relying on the fact a .lyx file starts with "#LyX".
> > It has been so from day 1 and it would be a real nuisance if it changes.
>
> The signature is the
Making all in .
make[3]: Entering directory `/home/bpeng/lyx-devel/lyx-win/src'
if g++ -DHAVE_CONFIG_H -I. -I. -I. -Winvalid-pch --include=./pch.h
-I../boost -Wextra -Wall-I/usr/X11R6/include -g -O -MT toc.o -MD
-MP -MF ".deps/toc.Tpo" -c -o toc.o toc.C; \
then mv -f ".deps/toc.Tpo" ".deps/to
> Bo is probably thinking of Qt on Windows which has only recently been GPL-ed.
> But LyX on Windows is only recent too...
When I was choosing between wxWidget/wxPython and qt/pyQt,
qt was free under linux (for GPL application only?), but was not under
windows. There was a qt3 GPL/free version, bu
> I am concerned about being able to recognize a .lyx file, as there is
> software relying on the fact a .lyx file starts with "#LyX".
> It has been so from day 1 and it would be a real nuisance if it changes.
The signature is the standard gz file signature. If the file is
decompressed, #LyX will
> It may work but there's no way that core code
> should contain #ifdef WIN32 blocks. You should
> add a function to lyx::support.
Not a problem. I will have to send format, command, etc separately to
a lyx::support function. The format.empty() check should be removed
from format.C though. I will
Abdelrazak Younes a écrit :
I'll put it in later today if there's no objection in the mean time.
Done.
Weird that my patches do not generate heated discussions anymore... I am
wondering if they are just not interesting... or maybe they are just
perfect? Just kidding :-)
Abdel.
Abdelrazak
This patch fixes a typo and goes in right now. Did nobody see the warning on
stderr?
GeorgIndex: src/lyxrc.C
===
--- src/lyxrc.C (Revision 13709)
+++ src/lyxrc.C (Arbeitskopie)
@@ -1795,7 +1795,7 @@ void LyXRC::write(ostream & os, bo
On Sat, Apr 22, 2006 at 08:27:34AM -0500, Bo Peng wrote:
> > Do they? I have been googling around, and what comes up is krun (KDE
> > specific) and "alternatives" (Debian origin, but available for rpm-based
> > distros as well). What comes up is mainly problems and complaints...
>
> On any system,
On Sat, Apr 22, 2006 at 09:28:50AM -0500, Bo Peng wrote:
> > Please, instead of
> >
> > #ifdef _WIN32
> > #ifndef _WIN32
> >
> > use
> >
> > #if defined(_WIN32) || defined(__CYGWIN__)
> > #if !defined(_WIN32) && !defined(__CYGWIN__)
> >
> > in this code, as it will also work on Cygwin.
>
> Please
> Please, instead of
>
> #ifdef _WIN32
> #ifndef _WIN32
>
> use
>
> #if defined(_WIN32) || defined(__CYGWIN__)
> #if !defined(_WIN32) && !defined(__CYGWIN__)
>
> in this code, as it will also work on Cygwin.
Please fix that yourself, and test this feature with the attached
configure.py patch. My w
Bo Peng <[EMAIL PROTECTED]> writes:
> > I packaged up compiled with the
> > USE_COMPRESSION macro defined, then no.
> Is it because of the difficulty to pack zlib.dll?
Nope. It was a question of priorities. I didn't feel
the feature was so important that it needed time and
effort spending on it b
On Fri, Apr 21, 2006 at 11:21:06PM -0500, Bo Peng wrote:
> 2. If viewer() is empty or "auto", ShellExecute will be called, and
> call the default viewer under windows. Otherwise, the specified viewer
> will be called.
Please, instead of
#ifdef _WIN32
#ifndef _WIN32
use
#if defined(_WIN32) || d
Bo Peng wrote:
> Since lyx/latex often uses external files, we need to have a clear
> mind what to do exactly. I haven't thought about this clearly, but
> figures etc may be all over the places, and in subdirectories.
Yes. It does not matter where exactly these files are, the different insets
kno
Georg Baum <[EMAIL PROTECTED]> writes:
> Bo Peng wrote:
> > Because of the license problem, I chose wxWidget and wxPython for my
> > GUI needs. Now, I still have to learn qt? ! I am wondering why, from
> > the very beginning, qt, instead of a GPL tool was used for lyx.
klyx was a port of LyX 0.12
Bo Peng <[EMAIL PROTECTED]> writes:
>> A new winlyx user should have 1.3.7 installed. I think that will
>> avoid most of the problems you mentioned at least it does for me.
> I did not experience these problems with Uwe's 1.3.7 installer, but
> that was for user accounts with administrative privil
On Fri, Apr 21, 2006 at 06:35:41PM -0500, Bo Peng wrote:
> > That said, I don't know how compression is handled, but I think that
> > it should be done such that a LyX file starts with "#LyX" such that it
> > is still possible to recognize it whatever its extension or
> > compression status.
>
>
Martin Vermeer <[EMAIL PROTECTED]> writes:
> Note BTW that the Tabular user interface for doing this has been
> criticized and should probably be reworked as well.
André and I had a half-hearted attempt at reusing the existing tabular dialog
for math array a couple of years ago. At the time the ma
Bo Peng wrote:
> Because of the license problem, I chose wxWidget and wxPython for my
> GUI needs. Now, I still have to learn qt? ! I am wondering why, from
> the very beginning, qt, instead of a GPL tool was used for lyx.
qt is GPL since several years.
In the very beginning there was only xfor
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
> I can put an experimental windows executable on the web if there's
> interest. I use it myself and it's stable enough.
http://wiki.lyx.org/Windows/LyX150_experimental ?
I shove executables into the equivalent location in the "uploads" section of th
On Sat, Apr 22, 2006 at 01:48:00PM +0200, Georg Baum wrote:
> Abdelrazak Younes wrote:
>
> > You know what would be great instead of a lyx compressed file? A
> > portable lyx format. Quite frankly I don't see much the interest of
> > having the lyx text file compressed as it is alreday quite smal
Bo Peng <[EMAIL PROTECTED]> writes:
> I am surprised that the attached short patch simply works, using
> mingw/win32api. Zlib.dll does not cause any trouble.
It may work but there's no way that core code
should contain #ifdef WIN32 blocks. You should
add a function to lyx::support. That might soun
Lars Gullik Bjønnes wrote:
> If we want it automake-based then configure must do the job.
This is not possible since lib/lyx2lyx/lyx2lyx_version.py is needed for make
dist.
> I'll think a bit about it... but I am not sure I'll find a good
> solution.
Lars, did you find a solution? If not I woul
> If this goes into trunk/1.4.X, we should also check for obsolete code,
> especially in the installers.
Please test the patch, and do the rest later. To avoid changing too
many code, and allow users to specify viewers explicitly, the viewer
entries in the rc file are still used. What we need to d
> Do they? I have been googling around, and what comes up is krun (KDE
> specific) and "alternatives" (Debian origin, but available for rpm-based
> distros as well). What comes up is mainly problems and complaints...
On any system, if double-click-on-icon works, such a facility exists.
Whether or
> A new winlyx user should have 1.3.7 installed. I think that will
> avoid most of the problems you mentioned at least it does for me.
I did not experience these problems with Uwe's 1.3.7 installer, but
that was for user accounts with administrative privilege. Maybe this
made a big difference.
Bo
> I packaged up compiled with the
> USE_COMPRESSION macro defined, then no.
Is it because of the difficulty to pack zlib.dll?
Bo
> I could probably help here (I am not considering myself a qt newbie
> anymore :-) ) but it would sure be better if you'd like to learn ;-)
Because of the license problem, I chose wxWidget and wxPython for my
GUI needs. Now, I still have to learn qt? ! I am wondering why, from
the very beginning
> You know what would be great instead of a lyx compressed file? A
> portable lyx format. Quite frankly I don't see much the interest of
> having the lyx text file compressed as it is alreday quite small even
> for very big file.
A while ago, a few users, actually only two, including me, reported
Jean-Marc Lasgouttes wrote:
> Georg, do you have a patch for 1.4? I'll look at it next week, along
> with several excellent patches that I saw floating around this week.
You mean one for using comfigure.py in 1.4, or one that corrects the tex2lyx
finding problem, or both? I have none of these cur
Angus Leeming wrote:
> The .ui files were all generated and maintained with Qt2's designer, yes.
> However, LyX 1.5 has dropped support for Qt2 so you should feel free to
> use Qt3's designer with the .ui files in the qt2 tree. Perhaps someone
> might rename the qt2 directory as qt3 to avoid conf
Abdelrazak Younes wrote:
> You know what would be great instead of a lyx compressed file? A
> portable lyx format. Quite frankly I don't see much the interest of
> having the lyx text file compressed as it is alreday quite small even
> for very big file. IMHO, a "portable lyx file" that would cont
Bo Peng <[EMAIL PROTECTED]> writes:
>
> Dear list,
>
> When I compile current svn under windows, boost::iostreams looks for
> zlib.h etc. They are standard under linux but I have to supply them
> under windows. I am sure I will have some trouble in linking lyx with
> zlib.dll later.
>
> My ques
Bo Peng wrote: Hi,
Just helped another guy to install lyx/win on his windows machine,
again frustrated. Briefly,
1. download everything, install, until we are told that miktex can not
be installed without adminstrative priveledge.
---
SH: An expe
Enrico Forestieri <[EMAIL PROTECTED]> writes:
> Perhaps the old file was generated with an older designer and I don't
> know if my changes would be compatible with Qt2.
The .ui files were all generated and maintained with Qt2's designer, yes.
However, LyX 1.5 has dropped support for Qt2 so you sh
On Sat, Apr 22, 2006 at 09:49:10AM +0200, Michael Gerz wrote:
> [EMAIL PROTECTED] wrote:
>
> >Author: vermeer
> >Date: Sat Apr 22 00:51:39 2006
> >New Revision: 13709
> >
> >Log:
> >
> > Grey out outlining movement buttons for non-ToC
> >
> >
> Martin,
>
> as you (as well as many others) wan
On Fri, Apr 21, 2006 at 11:21:06PM -0500, Bo Peng wrote:
> Dear all,
...
> Gnome, KDE, mac all have such facilities
Do they? I have been googling around, and what comes up is krun (KDE
specific) and "alternatives" (Debian origin, but available for rpm-based
distros as well). What comes u
Michael Gerz a écrit :
[EMAIL PROTECTED] wrote:
Author: vermeer
Date: Sat Apr 22 00:51:39 2006
New Revision: 13709
Log:
Grey out outlining movement buttons for non-ToC
Martin,
as you (as well as many others) want the outlining stuff to go into
1.4.X: Did you keep track of all the pa
[EMAIL PROTECTED] wrote:
Author: vermeer
Date: Sat Apr 22 00:51:39 2006
New Revision: 13709
Log:
Grey out outlining movement buttons for non-ToC
Martin,
as you (as well as many others) want the outlining stuff to go into
1.4.X: Did you keep track of all the patches that were comm
Bo Peng a écrit :
That said, I don't know how compression is handled, but I think that
it should be done such that a LyX file starts with "#LyX" such that it
is still possible to recognize it whatever its extension or
compression status.
Current behavior:
1. When lyx opens a file, it checks it
Bo Peng wrote:
Please test. If it works, this should go into 1.4.x. No more path to
acroread, ghostview, mozilla, yap trouble ...
Wow, this is a very exciting LyxWin patch and a great simplification.
If this goes into trunk/1.4.X, we should also check for obsolete code,
especially in the i
I'll put it in later today if there's no objection in the mean time.
Abdel.
Abdelrazak Younes a écrit :
And with this yet another updated patch, the dialog will automatically
update itself if a new section is created or modified or deleted... Even
Microsoft Word doesn't do this correctly :-)
Bo Peng a écrit :
That said, I don't know how compression is handled, but I think that
it should be done such that a LyX file starts with "#LyX" such that it
is still possible to recognize it whatever its extension or
compression status.
Current behavior:
1. When lyx opens a file, it checks it
Angus Leeming a écrit :
Persio Barros <[EMAIL PROTECTED]> writes:
[...]
The good news is:
1. LyX 1.5 will have a Qt4 interface, using the official Qt4
library from Trolltech.
I can put an experimental windows executable on the web if there's
interest. I use it myself and it's stable enough.
On Fri, Apr 21, 2006 at 05:30:42PM -0700, Ling Li wrote:
> Hi,
>
> Table column options like l, r, c, @{}, >{}, are well supported in
> LyX for tables (tabular environment). I am wondering whether the
> same thing can be supported for math array. Were there
> discussions, conclusions, or plans? I
On Fri, Apr 21, 2006 at 06:46:43PM -0500, Bo Peng wrote:
> > Don't you _hate_ Windows?
>
> Not exactly. I have been a long time, even qualified as *experienced*
> windows user. For basic usage and entertainment, windows is fine. The
> reason why I am now basically a linux user is that for the area
68 matches
Mail list logo
