According to the current README I've removed XForms 0.89.6
and tried to use XForms 1.0 and/or Qt!
A new Cygwin release with a new gcc 3.2 compiler. The new xforms 1.0 as well
as the new choice to use the Qt frontend and the new lyx 1.3.0 sources: Too
much changes in a too short time 8((
According to the current README I've removed XForms 0.89.6
and tried to use XForms 1.0 and/or Qt!
A new Cygwin release with a new gcc 3.2 compiler. The new xforms 1.0 as well
as the new choice to use the Qt frontend and the new lyx 1.3.0 sources: Too
much changes in a too short time 8((
Not with Win32! Have a look into src/support/os_win32.C. There
os::read:mode() does return rb for Win32!
I think this has nothing to do with the \r in LaTeX.C. There an ordinary
ifstream is used without giving the std::ios_base::binary flag, so this
should read in text mode.
What the *
| Of course it could be done easier with
| ifstream ifs(tmp.c_str(), ios::in | ios::text);
| Maybe we should include that instead ;-) And we can rewrite all calls
to
| open a file for both reading and writing.
|
| Does that work?
No, not with gcc, because gcc is conform with ANSI.
| ios::text? No. It is a non-standard flag.
| ...
| ios::binary otoh is a standard flag and should work everywhere.
|
| So there seems not to be another way then removong those trailing \r's
the
| way I'v done. We do need that in all cases where text read from a
(binary)
| opened file is
> > Not with Win32! Have a look into src/support/os_win32.C. There
> > os::read:mode() does return "rb" for Win32!
>
> I think this has nothing to do with the \r in LaTeX.C. There an ordinary
> ifstream is used without giving the std::ios_base::binary flag, so this
> should read in text mode.
>
>
> | > Of course it could be done easier with
> | > ifstream ifs(tmp.c_str(), ios::in | ios::text);
> | > Maybe we should include that instead ;-) And we can rewrite all calls
to
> | > open a file for both reading and writing.
> |
> | Does that work?
No, not with gcc, because gcc is conform
> | > ios::text? No. It is a non-standard flag.
> | > ...
> | > ios::binary otoh is a standard flag and should work everywhere.
> |
> | So there seems not to be another way then removong those trailing \r's
the
> | way I'v done. We do need that in all cases where text read from a
(binary)
> |
Lars Andre Poenitz [EMAIL PROTECTED] writes:
Lars | On Tue, Jan 07, 2003 at 12:31:00PM +0100, Andre' Poenitz wrote:
Lars | I just got confirmation from de.comp.lang.iso-c++ that |
Lars getline() should never return the '\r' if the stream is in |
Lars text mode.
That's the reason! In Lyx
That's the reason! In Lyx we do open *all* files the same way, i.e. in
binary mode by default.
No, the default mode is text.
Not with Win32! Have a look into src/support/os_win32.C. There
os::read:mode() does return rb for Win32!
To distinguish between text/binary mode we should have to
> Lars> Andre Poenitz <[EMAIL PROTECTED]> writes:
> Lars> | On Tue, Jan 07, 2003 at 12:31:00PM +0100, Andre' Poenitz wrote:
> Lars> | > I just got confirmation from de.comp.lang.iso-c++ that | >
> Lars> getline() should never return the '\r' if the stream is in | >
> Lars> text mode.
That's the
> > That's the reason! In Lyx we do open *all* files the same way, i.e. in
> > binary mode by default.
>
> No, the default mode is text.
Not with Win32! Have a look into src/support/os_win32.C. There
os::read:mode() does return "rb" for Win32!
> > To distinguish between text/binary mode we
Trying to compile release 1.2.1 on both Win32/Cygwin and SuSE 8.0 I do get
errors, because
#include FORMS_H_LOCATION
can't be resolved by the C-preprocessor. A diff with 1.2.0 shows that
src/config.h does not include any xforms stuff in particular that #define
FORMS_H_LOCATION needed above.
Trying to compile release 1.2.1 on both Win32/Cygwin and SuSE 8.0 I do get
errors, because
#include FORMS_H_LOCATION
can't be resolved by the C-preprocessor. A diff with 1.2.0 shows that
src/config.h does not include any xforms stuff in particular that #define
FORMS_H_LOCATION needed above.
Because I neither haven't got an answer from JMarc nor have found the win32
announcement at lyx.org I do forward my Win32 patch to this list directly.
- Original Message -
From: Claus Hentschel [EMAIL PROTECTED]
To: Jean-Marc Lasgouttes [EMAIL PROTECTED]
Sent: Friday, June 21, 2002 12:07
I'd a problem to control the margins with Lyx 1.2.0 some days ago (and a quick
and dirty(?)fix for it):
If you do use A4 paper as your default papersize and you decide to make own
margin settings in Layout-Document then package geometry will be called in
the tex file. But those values you do
Because I neither haven't got an answer from JMarc nor have found the win32
announcement at lyx.org I do forward my Win32 patch to this list directly.
- Original Message -
From: "Claus Hentschel" <[EMAIL PROTECTED]>
To: "Jean-Marc Lasgouttes" <[EMAIL PROT
I'd a problem to control the margins with Lyx 1.2.0 some days ago (and a quick
and dirty(?)fix for it):
If you do use A4 paper as your default papersize and you decide to make own
margin settings in Layout->Document then package geometry will be called in
the tex file. But those values you do
Ruurd,
Lyx 1.2.0 seems to run stable on my system now. I've started to rewrite the
html docu because of many changes in setting up Lyx.
I've packages Lyx together with the following
1) newest XFree-DLL's
2) ImageMagick compiles under Cygwin
3) epstopdf.exe compiled under Cygwin
The
Ruurd,
Lyx 1.2.0 seems to run stable on my system now. I've started to rewrite the
html docu because of many changes in setting up Lyx.
I've packages Lyx together with the following
1) newest XFree-DLL's
2) ImageMagick compiles under Cygwin
3) epstopdf.exe compiled under Cygwin
The
It works 8-)) i.e. XPM files can be viewed inside Lyx!
You wrote:
To reiterate what Angus says, there is the following in rgb_db.c in
xforms 1.0rc4:
static char *rgbfile[] =
{
/usr/lib/X11/rgb.txt, /* typical */
/usr/local/lib/X11/rgb.txt, /* try */
#if defined(sun) ||
It works 8-)) i.e. XPM files can be viewed inside Lyx!
You wrote:
> To reiterate what Angus says, there is the following in rgb_db.c in
> xforms 1.0rc4:
>
> static char *rgbfile[] =
> {
> "/usr/lib/X11/rgb.txt", /* typical */
> "/usr/local/lib/X11/rgb.txt", /* try */
> #if
First of all: The new Lyx really looks great ;-)
I'm still preparing the Win32 port of Lyx 1.2.0. So far I've successfully
compiled 1.2.0 on Win32/Cygwin after some manually changes in config.h. These
changes were necessary because autoconf/configure wasn't able to check the
existance of some
Hi, it's me again ;-)
Obviously XPM now is the preferred image format in Lyx, right?!
I've found, too the problem to convert EPS into XPM format and it have it
fixed. As always before it's a pathname problem, i.e. pathes should be
os::external_path()'ed when building the convert script.
But
First of all: The new Lyx really looks great ;-)
I'm still preparing the Win32 port of Lyx 1.2.0. So far I've successfully
compiled 1.2.0 on Win32/Cygwin after some manually changes in config.h. These
changes were necessary because autoconf/configure wasn't able to check the
existance of some
Hi, it's me again ;-)
Obviously XPM now is the preferred image format in Lyx, right?!
I've found, too the problem to convert EPS into XPM format and it have it
fixed. As always before it's a pathname problem, i.e. pathes should be
os::external_path()'ed when building the convert script.
But
Attached is my patch against the sources to make Lyx running on Win32 using
the Cygwin environment (release 1.3.6). Maybe someone is interested and this
patch will be included in future releases.
Some remarks to that patch:
1) lib/configure.m4 wasn't part of the sources tarball. I've picked
Attached is my patch against the sources to make Lyx running on Win32 using
the Cygwin environment (release 1.3.6). Maybe someone is interested and this
patch will be included in future releases.
Some remarks to that patch:
1) lib/configure.m4 wasn't part of the sources tarball. I've picked
JMarc and me are trying to merge all current diffs concerning Win32 into the
current cvs. I have downloaded it today from the US and changed all things
which still are not merged into cvs taken from Ruurds patch file.
I've tried to configure and compile LyX. But I do have many problems because
JMarc and me are trying to merge all current diffs concerning Win32 into the
current cvs. I have downloaded it today from the US and changed all things
which still are not merged into cvs taken from Ruurds patch file.
I've tried to configure and compile LyX. But I do have many problems because
I don't know if the pdflatex problem already has been fixed but here is what
I have made to fix the problem for Win32 (just inserted one character into
the sources):
Problem:
pdflatex writes the following third line into the log:
(sample.tex{pdftex.cfg}
instead of latex where the
I don't know if the pdflatex problem already has been fixed but here is what
I have made to fix the problem for Win32 (just inserted one character into
the sources):
Problem:
pdflatex writes the following third line into the log:
(sample.tex{pdftex.cfg}
instead of latex where the
Ruurd,
what's going wrong is, that the full path of the bib-file (as well as an
entry to plain.bst which furthermore has an ^M in its dep-file line near the
end) should not be appended to the tmpdir-pathname!
So far as I have tested, the bib-entry into the dep-file will NOT be done in
Ruurd,
what's going wrong is, that the full path of the bib-file (as well as an
entry to plain.bst which furthermore has an ^M in its dep-file line near the
end) should not be appended to the tmpdir-pathname!
So far as I have tested, the bib-entry into the dep-file will NOT be done in
I have made some tests on Linux and Win32. There are two problems (one new):
1. Under Linux the dep-file has an entry 'sample.idx' under Win32 there is
no entry in th edep file!?!?! So far as I have tested: if this will be
written into the dep file, all the makeindex stuff runs well!
The error
I have made some tests on Linux and Win32. There are two problems (one new):
1. Under Linux the dep-file has an entry 'sample.idx' under Win32 there is
no entry in th edep file!?!?! So far as I have tested: if this will be
written into the dep file, all the makeindex stuff runs well!
The error
Following message I have sent to JMarc and Ruurd
([EMAIL PROTECTED]) who helped me porting Lyx to Win32. I don't
know if this is only a Win32 problem but makeindex will not be called
although a missing *.ind file has been detected by latex (and not by LyX):
= begin
Following message I have sent to JMarc and Ruurd
([EMAIL PROTECTED]) who helped me porting Lyx to Win32. I don't
know if this is only a Win32 problem but makeindex will not be called
although a missing *.ind file has been detected by latex (and not by LyX):
= begin
I am using LyX since Lyx 1.0.4 on both Linux and Windows system. Up to Lyx
1.1.6 (fix1) I always was able to use LyX's source files on both systems
regardless where they have been written!
Now I have many problems with tables in
1) newly created files, i.e. with 1.1.6fix1
2) some old
Allan (Allan Rae [EMAIL PROTECTED]) had mentioned the solution:
The new tabular code can't handle CR (\r)!
Although I have tried to remove them within Win32 (maybe I had made anything
wrong;-)) using vim, another test in Linux makes all things as expected!
Conclusion:
Removing those
I am using LyX since Lyx 1.0.4 on both Linux and Windows system. Up to Lyx
1.1.6 (fix1) I always was able to use LyX's source files on both systems
regardless where they have been written!
Now I have many problems with tables in
1) newly created files, i.e. with 1.1.6fix1
2) some old
Allan (Allan Rae <[EMAIL PROTECTED]>) had mentioned the solution:
The new tabular code can't handle CR (\r)!
Although I have tried to remove them within Win32 (maybe I had made anything
wrong;-)) using vim, another test in Linux makes all things as expected!
Conclusion:
Removing those
Please note that I am NOT subscribed to lyx-devel!
So please at least don't forget to send a copy to me! Thank you!
Beginning with 1.1.6 LyX by default offers the new menu layout. If using
this (what is recommended) together with
Please note that I am NOT subscribed to lyx-devel!
So please at least don't forget to send a copy to me! Thank you!
Beginning with 1.1.6 LyX by default offers the new menu layout. If using
this (what is recommended) together with
At the moment I am not subscribed at lyx-devel, so please at least CC to
[EMAIL PROTECTED]
if answering to that topic! (thank you!)
I am now trying to get 1.1.6 run on Win32. Obviously there has been changed
so much in
for all insets, or only for "new" ones that use sigc++
signals
and slots to trigger the dialog?
Eg: Citation is new but Bibtex and Bibitem are old.
Angus
On Friday 19 January 2001 09:31, Claus Hentschel wrote:
At the moment I am not subscribed at lyx-devel, so please a
At the moment I am not subscribed at lyx-devel, so please at least CC to
[EMAIL PROTECTED]
if answering to that topic! (thank you!)
I am now trying to get 1.1.6 run on Win32. Obviously there has been changed
so much in
rue for all insets, or only for "new" ones that use sigc++
signals
> and slots to trigger the dialog?
>
> Eg: Citation is new but Bibtex and Bibitem are old.
>
> Angus
>
>
>
> On Friday 19 January 2001 09:31, Claus Hentschel wrote:
> > At the moment I am n
Jean-Marc Lasgouttes wrote:
"Claus" == Claus Hentschel [EMAIL PROTECTED]
writes:
Claus Am i right when I patch the fix1 sources and after that install
Claus the fix2 patch?
Yes the right order is:
get 1.1.4
apply 1.1.4fix1
apply 1.1.4fix2
apply any other patch you like
Jean-Marc Lasgouttes wrote:
> >>>>> "Claus" == Claus Hentschel <[EMAIL PROTECTED]>
writes:
>
> Claus> Am i right when I patch the fix1 sources and after that install
> Claus> the fix2 patch?
>
> Yes the right order is:
>
> get 1.1.4
&g
From: Dekel wrote:
| If there is an error - and there still are a lot of in my files which
did
| not come up in fix1 - than in fix2 near the error boxes there are some
| characters removed from what I have written before. So fixing one
| error and
That is a bug. Kaywan posted a fix
I've patched 1.1.4fix1 with your sent patch and have compiled it. This
results in an unresolved external 'sort' when linking lyx(.exe) 8-( What am
I missing, what is not part of the LyX source code?
Regards
Claus
From: Dekel wrote:
> > | If there is an error - and there still are a lot of in my files which
did
> > | not come up in fix1 - than in fix2 near the error boxes there are some
> > | characters removed from what I have written before. So fixing one
> > | error and
> >
> > That is a bug. Kaywan
I've patched 1.1.4fix1 with your sent patch and have compiled it. This
results in an unresolved external 'sort' when linking lyx(.exe) 8-( What am
I missing, what is not part of the LyX source code?
Regards
Claus
Jaen-Marc wrote:
Claus BTW: What about that "file not found error" with relative files
Claus included? The problem could be fixed when setting \use_tempdir
Claus false But: in that case I can't access the Logfile, so 'View
Claus Latex Logfile..' results in a window, telling me that it cannot
Jaen-Marc wrote:
> Claus> BTW: What about that "file not found error" with relative files
> Claus> included? The problem could be fixed when setting \use_tempdir
> Claus> false But: in that case I can't access the Logfile, so 'View
> Claus> Latex Logfile..' results in a window, telling me that it
I've got some information that cygwin has fixed some problems concerning
process generation in a new (although beta) cygwin.dll. So I fetched that
dll and recompiled 1.1.4fix1 with only one change in the sources. This
change (I mailed this some days ago) is the flag
O_RDONLY | O_BINARY
Yes, the parsing of log file is improved in fix2.
Does this mean that beginning with fix2 you can't use all style files within
LyX, although they could be used before and in pure LaTeX?
Claus
Jean-Marc Lasgouttes wrote:
No, that means that there was an error in the way you used the file,
and now LyX tells you about it (I think). If you send a short example
file, along with the .log and .tex, we might be able to help.
I've included all necessary files to reproduce that error. Try
I've got some information that cygwin has fixed some problems concerning
process generation in a new (although beta) cygwin.dll. So I fetched that
dll and recompiled 1.1.4fix1 with only one change in the sources. This
change (I mailed this some days ago) is the flag
O_RDONLY | O_BINARY
> Yes, the parsing of log file is improved in fix2.
Does this mean that beginning with fix2 you can't use all style files within
LyX, although they could be used before and in pure LaTeX?
Claus
Jean-Marc Lasgouttes wrote:
> No, that means that there was an error in the way you used the file,
> and now LyX tells you about it (I think). If you send a short example
> file, along with the .log and .tex, we might be able to help.
I've included all necessary files to reproduce that error.
Hi anybody!
Maybe you Know, that I'm working on ports for Win32 of Lyx. There were some
messages a few weeks ago, concerning that port!
Now some people asked me because it is not possible to enable german, dutch
or whatever menus in Lyx? And of course this does not work with my port -
But it
Hi anybody!
Maybe you Know, that I'm working on ports for Win32 of Lyx. There were some
messages a few weeks ago, concerning that port!
Now some people asked me because it is not possible to enable german, dutch
or whatever menus in Lyx? And of course this does not work with my port -
But it
I've fetched lyx-1.1.4fix1.gz from the official web site. How can I patch my
source files using the included text file?
Thanks in advance
Claus
I've fetched lyx-1.1.4fix1.gz from the official web site. How can I patch my
source files using the included text file?
Thanks in advance
Claus
Lars Jensen wrote:
Is there a specific site where the latest win32 port can always be
found? I noticed that www.lyx.org has a link to v.1.0.4, while others on
the mailing list appear to have v.1.1.4.
It seems that Steven van Dijk has released the 'official' win32 port for
LyX. I Don't know
> Lars Jensen wrote:
> Is there a specific site where the latest win32 port can always be
> found? I noticed that www.lyx.org has a link to v.1.0.4, while others on
> the mailing list appear to have v.1.1.4.
It seems that Steven van Dijk has released the 'official' win32 port for
LyX. I Don't
:
# --
-
On Thu, 25 Nov 1999, Claus Hentschel wrote:
Is it true, that mingw32 do not support signals due to the underlaying
windows opsys? I got messages that struct sigaction (usually defined in
sys/signal.h) is not known, so my
lowing
mail some time ago:
# --
-----
On Thu, 25 Nov 1999, Claus Hentschel wrote:
> Is it true, that mingw32 do not support signals due to the underlaying
> windows opsys? I got messages that struct sigaction (us
I tried to compile Lyx 1.1.4 on Win98 using cygnus. The problrm is, that on
my system originally regex was NOT installed! The configuration didn't set
HAVE_REGEX_H so it should be lyxregex.h included -- BUT LYXREGEX.H IS NOT
PART OF THE SOURCE PACKAGE!
I fetched regex-0.12 and installed regex.h
Thank you for the inlined lyxregex.h! I removed my symblink and installed
your file instead -- and all went well ;) So Lyx 1.1.4 is running under
Win98!! I will make a distribution file (ZIP) and put it into the web for
others, who are interested in the next days! I send a message to
@lyx-users@!
LyX 1.1.4 could be compiled on Win98 using the cygnus environment with the
released source tar file when the missing file lyxregex.h is available.
Furthermore one needs regex-0.12, i.e. regex.c and regex.h both copied into
src/support.
This compiled out-of-the-box-Lyx runs stable so long as you
I tried to compile Lyx 1.1.4 on Win98 using cygnus. The problrm is, that on
my system originally regex was NOT installed! The configuration didn't set
HAVE_REGEX_H so it should be lyxregex.h included -- BUT LYXREGEX.H IS NOT
PART OF THE SOURCE PACKAGE!
I fetched regex-0.12 and installed regex.h
Thank you for the inlined lyxregex.h! I removed my symblink and installed
your file instead -- and all went well ;) So Lyx 1.1.4 is running under
Win98!! I will make a distribution file (ZIP) and put it into the web for
others, who are interested in the next days! I send a message to
@lyx-users@!
LyX 1.1.4 could be compiled on Win98 using the cygnus environment with the
released source tar file when the missing file lyxregex.h is available.
Furthermore one needs regex-0.12, i.e. regex.c and regex.h both copied into
src/support.
This compiled out-of-the-box-Lyx runs stable so long as you
I tried to debug a little bit in figinset.C to learn a little bit about what
the child process is doing. I tried the following:
if (pid == 0) { // child
char **env, rbuf[80], gbuf[40];
int ne = 0;
Display* tempdisp = XOpenDisplay(XDisplayName(0));
FilePtr
I tried to debug a little bit in figinset.C to learn a little bit about what
the child process is doing. I tried the following:
if (pid == 0) { // child
char **env, rbuf[80], gbuf[40];
int ne = 0;
Display* tempdisp = XOpenDisplay(XDisplayName(0));
FilePtr
I've succesfully compiled Lyx 1.1.2 with Cygnus B20.1 on my system. I don't
know how to make this public, so I tell you what problems I had and what
I've done to fix those!
1. I've got the source lyx.1.1.2.tar.gz from a mentioned ftp server.
2. I've configured lyx with following options:
I've succesfully compiled Lyx 1.1.2 with Cygnus B20.1 on my system. I don't
know how to make this public, so I tell you what problems I had and what
I've done to fix those!
1. I've got the source lyx.1.1.2.tar.gz from a mentioned ftp server.
2. I've configured lyx with following options:
I tried to port Lyx 1.1.2 to Win98 using the cygwin-b20.1 environment, i.e
gcc 2.95. What I first have done is to configure Lyx as by calling following
script:
===
#!/bin/sh
./configure --prefix=/apps/lyx112 \
--x-includes=/usr/X11r64/include \
I tried to port Lyx 1.1.2 to Win98 using the cygwin-b20.1 environment, i.e
gcc 2.95. What I first have done is to configure Lyx as by calling following
script:
===
#!/bin/sh
./configure --prefix=/apps/lyx112 \
--x-includes=/usr/X11r64/include \
Hi anybody!
I'm still moving from Microsoft Word 97 to Lyx, because I need to write text
with many math. formulas. That's obviously too hard for that tool :-((
Lyx seems to be great! But I found a minor bug in the MathEditor. When
inserting a math. logical or (like a letter 'v') than you see
Hi anybody!
I'm still moving from Microsoft Word 97 to Lyx, because I need to write text
with many math. formulas. That's obviously too hard for that tool :-((
Lyx seems to be great! But I found a minor bug in the MathEditor. When
inserting a math. logical or (like a letter 'v') than you see
84 matches
Mail list logo
