Sigh. Once again: tex2lyx _must not_ be changed unless somebody implements
the changes from format 245 to 254 first. Otherwise tex2lyx will generate
invalid files.
I was asking if someone can complete this patch with needed tex2lyx
changes so that this patch will *not* produce invalid files. Wha
Hi,
please see the email's subject.
Patch has been tested extensively and committed.
Time to go to bed! Good night!
Michael
Index: text.C
===
--- text.C (Revision 16031)
+++ text.C (Arbeitskopie)
@@ -1747,21 +1747,13 @@
if (cur
Hello,
today a colleague started with LyX 1.4.3 on WinXP. He reported that it crashed
several times. Just wondering:
- Is LyX on Linux much more stable than on WinXP?
- Or did he most likely see the crashes, because a new user does things which
experienced users/developers never test?
Thanks,
R
Sorry,
without sophisticated optimizations (which are outside of the scope of
1.5.X), several CT-related LFUNs are always enabled.
The attached patch has already been committed.
Michael
Index: text3.C
===
--- text3.C (Revision 16
Hello,
next patch:
the use of backspacePos0 is dangerous as it does not honour change tracking =>
make it a private method; clarify the description of backspacePos0 (it does not
always merge paragraphs)
As usual: committed!
Michael
Index: lyxtext.h
===
Hi,
this patch fixes a double-to-int conversion. (already committed)
Michael
Index: rowpainter.C
===
--- rowpainter.C (Revision 16028)
+++ rowpainter.C (Arbeitskopie)
@@ -48,7 +48,6 @@
using std::endl;
using std::max;
-using std
Hi,
this patch fixes two problems with end-of-par handling. I tested it
successfully and rigorously.
I already committed it to speed up development. If you think that
something is wrong, I will revert the patch instantly.
Michael
Index: text.C
===
Georg Baum wrote:
> If the integrated latex support is based on writer2latex, then I would do
> something else: Tell writer2latex to ignore visual markup, and only to
> export the document structure. This could be done with a config file, and
> I got very good results with that some time ago.
Ye
On Fri, Nov 24, 2006 at 03:17:56PM +0100, Abdelrazak Younes wrote:
> I am trying to convert a word document to lyx using OpenOffice newly
> integrated latex export. My problem is that there is an awful lot of ERT
> in the converted LyX document, things like '\clearpage', '{', '}',
> '\selectlan
Hi,
I have just started to use the newest LyX 1.4.3.
I have noticed that I can no longer use the lyx/kbd/european.kmap
properly. There is a problem with "umlaut". The line:
\kmod \" umlaut aAeEiIjJoOsSuUyY$\#~
does not work. As soon as I press the \" key on my keyboard, LyX changes
it uncon
On Fri, Nov 24, 2006 at 01:16:53PM +, Jean-Pierre Chrétien wrote:
> Configure runs OK, but now lyx fails at the very end of compilation with:
> ld: warning: file /usr/local/lib/libiconv.so: attempted multiple
> inclusion of file
> ld: warning: file /usr/local/lib/libstdc++.so: linked to
> /usr
On Fri, 24 Nov 2006, José Matos wrote:
> On Sunday 19 November 2006 2:42 am, Mason Deaver wrote:
> > I'm probably not the first to bring this to your attention, but here
> > goes anyway: The December 2006 issue of Linux Journal has an article
> > featuring LyX. It's part 1 of a 2-part article on
Abdelrazak Younes wrote:
> I would be interested in coding some kind of global ERT search and
> replace in LyX.
>
Why not a real search&replace function for LyX 1.5.x, where you can find
anything in your documment LyX, LaTeX in ERT, math, citations, styles ?
Cheers,
Charles
--
http://www.kde-f
Jean-Marc Lasgouttes wrote:
> At least \selectlanguage should be handled by tex2lyx.
Yes it should, but it is not.
Georg
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> Dear Georg, I am trying to convert a word document to lyx
Abdelrazak> using OpenOffice newly integrated latex export. My problem
Abdelrazak> is that there is an awful lot of ERT in the converted LyX
Abdelrazak> documen
Abdelrazak Younes wrote:
> Right now I have the impression that math in LyX is unusable. IMHO, not
> displaying the pink corners when navigating was not that huge regression
> and it would help the Mac platform tremendously. I mean, it would have
> been a good compromise. But we can still hack bac
Abdelrazak Younes wrote:
> Peter Kümmel wrote:
I've found a solution without ::exit(0) which I've tested with
msvc/Qt4.2.1
and Linux/Qt4.1.3.
>>> I don't understand. Current svn doesn't need the ::exit(0) on Linux and
>>> Windows, so why is it a solution?
>>
>> It is a solution becau
Abdelrazak Younes wrote:
> So I have two questions:
> 1) is it possible to tell tex2lyx to ignore all ERT? Would this be hard
> to implement?
No, have a look at handle_ert.
> 2) how would it be possible to filter out all ERT inside a LyX file?
>
> I would be interested in coding some kind of gl
Please update to cmake 2.4.4:
http://cmake.org/HTML/Download.html
Older versions does not work any more
with head.
Peter
Abdelrazak Younes wrote:
> The problems arrive when some options require one argument, others
> require two arguments, etc. Then it is very difficult to know which is a
> wrong option argument and which is a filename. At least LyX cannot make
> the difference, I noticed that with this command line
On Fri, Nov 24, 2006 at 02:44:15PM +0100, Jean-Marc Lasgouttes wrote:
> > "Jean-Marc" == Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>
> Jean-Marc> But I am very happy about the final outcome.
>
> Since I know you would be disappointed if I did not complain, I'll
> just point out that:
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> So what are you complaining about? That '-dbgx all' is not
Abdelrazak> recognized or that LyX tries to delete /tmp?
The second.
Abdelrazak> If the first, this is normal, try '-dbg any' instead. It
Abdelrazak> the lat
Dear Georg,
I am trying to convert a word document to lyx using OpenOffice newly
integrated latex export. My problem is that there is an awful lot of ERT
in the converted LyX document, things like '\clearpage', '{', '}',
'\selectlanguage{english}', ...
So I have two questions:
1) is it possi
Jean-Marc Lasgouttes wrote:
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
I was not trying to criticize the cleanup that was done.
I was just pushing the envelop because it's Friday.
The reason
why I asked you to take a look was because I know that tweaking this
to work we
Jean-Marc Lasgouttes wrote:
"Jean-Marc" == Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
Jean-Marc> But I am very happy about the final outcome.
Since I know you would be disappointed if I did not complain, I'll
just point out that:
So what are you complaining about? That '-dbgx all' is n
> "Jean-Marc" == Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
Jean-Marc> But I am very happy about the final outcome.
Since I know you would be disappointed if I did not complain, I'll
just point out that:
fantomas: src/lyx -dbgx all
Session management error: Could not open network socke
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>> I do not want this -f either. In general, we shall not introduce
>> such limitations for reason that are just our internal organization
>> of code (like the issue of mathed color corners).
Abdelrazak> The former organisation
Hello,
In a tcsh shell, with
setenv QT4DIR /usr/local/qt-4.1.4
./configure --with-frontend=qt4 --with-version-suffix=1.5.0alpha1
I get the message
checking size of wchar_t... configure: error: cannot compute sizeof (wchar_t),
77
See `config.log' for more details.
The log says:
configure:6941:
Georg Baum wrote:
Abdelrazak Younes wrote:
Not always, the -f option would be implicit if the filenames are given
first. For example these 4 command lines would be OK:
lyx UserGuide.lyx Intro.lyx -c 3 -dbg key
lyx UserGuide.lyx -c 3 -dbg key -f Intro.lyx
lyx -c 3 -dbg key -f UserGuide.lyx Intr
Georg Baum wrote:
Abdelrazak Younes wrote:
The former organisation of the code was the one completely _wrong_.
Compare the lyx_main.C in 1.4 and 1.5 and you'll see what I mean.
Generally speaking, the current organisation of the code is better
because cleaner. And because it is cleaner it is ea
On Sunday 19 November 2006 2:42 am, Mason Deaver wrote:
> I'm probably not the first to bring this to your attention, but here
> goes anyway: The December 2006 issue of Linux Journal has an article
> featuring LyX. It's part 1 of a 2-part article on getting your material
> (book, paper, etc) publ
Abdelrazak Younes wrote:
> Not always, the -f option would be implicit if the filenames are given
> first. For example these 4 command lines would be OK:
>
> lyx UserGuide.lyx Intro.lyx -c 3 -dbg key
> lyx UserGuide.lyx -c 3 -dbg key -f Intro.lyx
> lyx -c 3 -dbg key -f UserGuide.lyx Intro.lyx
> l
Abdelrazak Younes wrote:
> The former organisation of the code was the one completely _wrong_.
> Compare the lyx_main.C in 1.4 and 1.5 and you'll see what I mean.
> Generally speaking, the current organisation of the code is better
> because cleaner. And because it is cleaner it is easy to solve a
Jean-Marc Lasgouttes wrote:
Georg> No. I start LyX (and other programs) with filenames many times
Georg> a day, and always adding -f for LyX would be inconsistent and
Georg> too much work.
I do not want this -f either. In general, we shall not introduce such
limitations for reason that are just
This trivial fix is going in now: we have to use nb_NO instead of
no_NO, as we already to in po/.
JMarc
Index: lib/ChangeLog
===
--- lib/ChangeLog (revision 16023)
+++ lib/ChangeLog (working copy)
@@ -1,3 +1,7 @@
+2006-11-24 Jean-M
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> But this one (which we allow presently) would not be OK:
Abdelrazak> lyx -c 3 -dbg key UserGuide.lyx Intro.lyx
Abdelrazak> This last syntax IMHO this is bug prone and contains an
Abdelrazak> inherent ambiguity.
No,
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Actually this is still wrong. The order in 1.4 is:
Georg> - Parse all known LyX arguments in the LyX singleton and store
Georg> them - Let the frontend parse and remove all arguments that it
Georg> knows - Complain for all remaining a
Georg Baum wrote:
Abdelrazak Younes wrote:
Jean-Marc Lasgouttes wrote:
"Georg" == Georg Baum
<[EMAIL PROTECTED]>
writes:
Georg> I is a new bug and a regression WRT 1.4: Now unknown arguments
Georg> are simply ignored. That should not happen, because that would
Georg> mean that I can make a ty
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Jean-Marc Lasgouttes wrote:
>> +docstring const translateIfPossible(docstring const & name);
>> +
>>
>> Should this be named translateIfAscii?
Georg> If you prefer that I'll change it. I used translateIfPossible
Georg> because I did
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> IMO we should either use the version of Ugras, or not create
Georg> any new inset but let InsetPagebreak inherit from InsetCommand.
Georg> Then the command name would be an argument of the constructor,
Georg> and we could even implemen
Abdelrazak Younes wrote:
> Jean-Marc Lasgouttes wrote:
>>> "Georg" == Georg Baum
>>> <[EMAIL PROTECTED]>
>>> writes:
>>
>> Georg> I is a new bug and a regression WRT 1.4: Now unknown arguments
>> Georg> are simply ignored. That should not happen, because that would
>> Georg> mean that
> "Alain" == Alain Bertrand <[EMAIL PROTECTED]> writes:
Alain> Jean-Marc Lasgouttes a écrit :
>> This is quite funny actually... So the question may be: are there
>> any people interested in an alpha release and who are not able to
>> use svn? Should we really make releases before pre version
Jean-Marc Lasgouttes wrote:
"Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> I is a new bug and a regression WRT 1.4: Now unknown arguments
Georg> are simply ignored. That should not happen, because that would
Georg> mean that I can make a typo and don't recognize it. The order
Georg> o
Jean-Marc Lasgouttes wrote:
"Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> I is a new bug and a regression WRT 1.4: Now unknown arguments
Georg> are simply ignored. That should not happen, because that would
Georg> mean that I can make a typo and don't recognize it. The order
Georg> o
Jean-Marc Lasgouttes wrote:
> +docstring const translateIfPossible(docstring const & name);
> +
>
> Should this be named translateIfAscii?
If you prefer that I'll change it. I used translateIfPossible because I did
not want to emphasise the point that the string is ASCII if it comes from a
syste
45 matches
Mail list logo
