Re: Mac Cursor and Math Mode problem

Hi Antonio, Antonio Rieser wrote: > Two problems. I'm using LyX on the Mac (OS X.3/4.?) Which Mac OS X and which LyX version? > for the > first time, and after I choose 'Section' and then type, the text on > the line I'm typing jumps to the right, but the cursor stays where it > is. It drives

Bug and thanks

Hi, all! I'm using LyX to write my doctoral mathematics thesis, and I love it! I never minded typing TeX commands, but I don't want to look at them, and then I found LyX... It's great! Keep it up! Just two problems. I'm using LyX on the Mac (OS X.3/4.?) for the first time, and after I choose 'S

Re: xy-pic manual

H. Peter Gumm wrote: > Dear Pavel, > thanks for reminding me and thanks for your offer to accept the files, so > that I can postpone learning the svn system to some later time when I have > less obligations. I have reworked the manual and I attach it in the form of > four files to this mail. He

Re: [PATCH] Re: Undo messages

Le 21 oct. 08 à 20:43, Pavel Sanda a écrit : Jean-Marc Lasgouttes wrote: case LFUN_VC_CHECK_OUT: - LASSERT(lyx_view_ && lyx_view_->buffer(), /**/); + LASSERT(lyx_view_ && buffer, /**/); if (!ensureBufferClean(vie

Re: Problem converting index from 1.5

On Tue, Oct 21, 2008 at 07:01:09PM +0100, José Matos wrote: > As far as I understand there are some problems compiling the resulting latex > files, that is why it returns 1. > > FWIW I am talking about the manual of sdcc that can be found in > http://www.lyx.org/~jamatos/sdccman.tgz > > In this

Re: LyX on Mac using Qt 4.2.0

Le 21 oct. 08 à 22:09, Pavel Sanda a écrit : LyX 1.6.x needs at least version 4.2.2. Why is that? it is the result of the discussion in the past. OK, I forgot, i seems. Is it documented? http://www.lyx.org/AdditionalSoftware INSTALL does not say a word about it, and actually there is

Re: resetting itemize to standard

if you are in itemize return: new item at current level m-return: standard in itemize at current level reset: reset to standard, and also reset level So there is no way to end the current 2nd level itemize and continue the 1st level one? And what is "reset"? The idea of having

RE: resetting itemize to standard

> No, but I'm with you on that case. I think Standard in itemize is fairly > normal. i am also with both of you, what i am suggesting is: if you are in itemize return: new item at current level m-return: standard in itemize at current level reset: reset to standard, and also reset l

Re: LyX on Mac using Qt 4.2.0

Jean-Marc Lasgouttes wrote: >>> Just to have it documented on the list, building Lyx (tested with >>> 1.6.0rc3) >>> with _Qt 4.2.0 (!!!)_ on the Mac fails with >> >> LyX 1.6.x needs at least version 4.2.2. > > Why is that? it is the result of the discussion in the past. >Is it documented? http:

Re: resetting itemize to standard

Jean-Marc Lasgouttes wrote: Can I suggest again the option of putting this in the layout file? It seems there are clear cases, such as section, where the sensible behavior is to unnest, even if that is not what one would always want to do. And if it's in the layout file, then of course it is c

Re: [PATCH] Re: Undo messages

On 21/10/2008 16:44, Jean-Marc Lasgouttes wrote: Pavel Sanda<[EMAIL PROTECTED]> writes: Jean-Marc Lasgouttes wrote: Since I am a nice guy, I prepared new patches just for you. - goodbuf-light is the one that does the useful things. It might look simpler, but all the difficult bu

Re: 1.6svn bug: open an included file, and the containing file gets "changed"?

Le 21 oct. 08 à 19:45, Helge Hafting a écrit : Open a master document that includes a child. click the child document to open it too. Now the master document think it is changed - but it was *not* changed at all. I merely looked at the child document. I committed a fix today, I think. JMarc

Re: LyX on Mac using Qt 4.2.0

Le 21 oct. 08 à 17:33, Pavel Sanda a écrit : Konrad Hofbauer wrote: Just to have it documented on the list, building Lyx (tested with 1.6.0rc3) with _Qt 4.2.0 (!!!)_ on the Mac fails with LyX 1.6.x needs at least version 4.2.2. Why is that? Is it documented? JMarc

Re: resetting itemize to standard

Can I suggest again the option of putting this in the layout file? It seems there are clear cases, such as section, where the sensible behavior is to unnest, even if that is not what one would always want to do. And if it's in the layout file, then of course it is configurable. That is in

Re: [PATCH] Re: Undo messages

Jean-Marc Lasgouttes wrote: > case LFUN_VC_CHECK_OUT: > - LASSERT(lyx_view_ && lyx_view_->buffer(), /**/); > + LASSERT(lyx_view_ && buffer, /**/); > if (!ensureBufferClean(view())) > break; > -

Re: Problem converting index from 1.5

On Tuesday 21 October 2008 14:15:24 rgheck wrote: > > I've looked through the code a bit, and I'm not sure what's happening > here. I do know that there are inconsistencies, where we return true to > signal an error sometimes and true to signal success other times. So it > may be that this is the p

1.6svn bug: open an included file, and the containing file gets "changed"?

Open a master document that includes a child. click the child document to open it too. Now the master document think it is changed - but it was *not* changed at all. I merely looked at the child document. Helge Hafting

external xfig inset broken in 1.6svn?

I opened an old .lyx file containing xfig insets. They did not render, and export->pdflatex failed with messages that my fig files could not be found with extensions .png, .jpg, .pdf, ... Of course they coudn't! They are .fig files, so they are not found under other names. :-( I downloaded and c

Re: resetting itemize to standard

leuven edwin wrote: if on the other hand all arguments are by definition equally valid (ie we cannot claim an argument is a sophism), well then there is no point in having a discussion in the first place (i am sure richard is highly amused by this thread) don't we philosophers make our li

Re: resetting itemize to standard

Jean-Marc Lasgouttes wrote: leuven edwin <[EMAIL PROTECTED]> writes: maybe the nesting level is not formally part of the layout *in lyx*, it is definitely layout. so i do not see why LFUN_LAYOUT should not change it... To put things differently: we already have too much code adding fan

Re: [patch] bug 5385: CJK yields a missing \end{CJK} with child documents

Jean-Marc Lasgouttes wrote: > > On Tuesday 21 October 2008 15:30:21 Jürgen Spitzmüller wrote: > >> OK to commit? > >> > >> Jürgen > > > > It seems reasonable indeed. > > +1 It turns out to be slightly more complicated -- we have to care about the \end tags as well. Updated patch attached. Jürgen

Re: rc4 release schedule

Konrad Hofbauer schrieb: Stephan Witt wrote: Currently, I'm trying to start building LyX on Mac OS X. The first experiment to configure with an Qt-dmg from Trolltech failed. So I'm trying it as described in INSTALL.MacOSX and now I'm building my privat Qt-Library. It's not ready now. T

Re: LyX on Mac using Qt 4.2.0

Konrad Hofbauer wrote: > Just to have it documented on the list, building Lyx (tested with 1.6.0rc3) > with _Qt 4.2.0 (!!!)_ on the Mac fails with LyX 1.6.x needs at least version 4.2.2. pavel

Re: [PATCH] Re: Undo messages

Jean-Marc Lasgouttes wrote: > Easy: you have 2 days to find a bug :) nice try, but i have better things to do :D pavel

LyX on Mac using Qt 4.2.0

Just to have it documented on the list, building Lyx (tested with 1.6.0rc3) with _Qt 4.2.0 (!!!)_ on the Mac fails with g++ -DHAVE_CONFIG_H -I. -I../../.. -DQT_NO_STL -DQT_NO_KEYWORDS -DQT_NO_CAST_TO_ASCII -DQT_NO_STL -I../../../src -I../../../src/frontends -I../../../images -I/Users/khofbau

Re: rc4 release schedule

Stephan Witt wrote: > Currently, I'm trying to start building LyX on Mac OS X. > The first experiment to configure with an Qt-dmg from Trolltech failed. > So I'm trying it as described in INSTALL.MacOSX and now I'm building > my privat Qt-Library. It's not ready now. Then I hope to proceed > succe

Re: [PATCH] Re: Undo messages

On Tuesday 21 October 2008 15:44:40 Jean-Marc Lasgouttes wrote: > Pavel Sanda <[EMAIL PROTECTED]> writes: > > Jean-Marc Lasgouttes wrote: > >> Since I am a nice guy, I prepared new patches just for you. > >> > >> - goodbuf-light is the one that does the useful things. It might look > >> simpler,

RE: resetting itemize to standard

> I begin to wonder whether accusing the other side of sophism at each > argument is not some kind of meta-sophism, or even maybe the Mother > Of All Sophisms. i did not accuse you of sophism at each argument, only when you referred to "it make sense because it is possible in latex", "there might

Re: [PATCH] Re: Undo messages

Pavel Sanda <[EMAIL PROTECTED]> writes: > Jean-Marc Lasgouttes wrote: >> Since I am a nice guy, I prepared new patches just for you. >> >> - goodbuf-light is the one that does the useful things. It might look >> simpler, but all the difficult bugs are in there. Note that I added a >> test for

Re: [patch] bug 5385: CJK yields a missing \end{CJK} with child documents

José Matos <[EMAIL PROTECTED]> writes: > On Tuesday 21 October 2008 15:30:21 Jürgen Spitzmüller wrote: >> OK to commit? >> >> Jürgen > > It seems reasonable indeed. +1 JMarc

Re: [PATCH] Re: Undo messages

Jean-Marc Lasgouttes wrote: > Since I am a nice guy, I prepared new patches just for you. > > - goodbuf-light is the one that does the useful things. It might look > simpler, but all the difficult bugs are in there. Note that I added a > test for the validity of "buffer". i have tested lightw

Re: [patch] bug 5385: CJK yields a missing \end{CJK} with child documents

On Tuesday 21 October 2008 15:30:21 Jürgen Spitzmüller wrote: > OK to commit? > > Jürgen It seems reasonable indeed. -- José Abílio

[patch] bug 5385: CJK yields a missing \end{CJK} with child documents

http://bugzilla.lyx.org/show_bug.cgi?id=5385 Problem: - We enclose the main text of CJK documents in \begin{CJK}...\end{CJK} - This is also done in child documents, which triggers a LaTeX error due to invalid nesting (of the CJK environment) Solution: - Do not start a new CJK environment at the

Re: resetting itemize to standard

leuven edwin <[EMAIL PROTECTED]> writes: >> I think it is wrong to have LFUN_LAYOUT do something else than just >> change the layout. > > trying the semantic arguments now? (another sophism ;-) I have to admit that I had to look-up sophism because as a poor mathematician I do not use consciously

Re: [PATCH] Re: Undo messages

On Tuesday 21 October 2008 14:58:53 Jean-Marc Lasgouttes wrote: > - goodbuf-extra is the one that does the trivial stuff. I am ready to >   bet a beer or two that there is 0 bug there (though I may regret >   writing that). It should be applied on top of the other one. I am prepared to bet with yo

RE: resetting itemize to standard

> I think it is wrong to have LFUN_LAYOUT do something else than just > change the layout. trying the semantic arguments now? (another sophism ;-) maybe the nesting level is not formally part of the layout *in lyx*, it is definitely layout. so i do not see why LFUN_LAYOUT should not change it...

RE: resetting itemize to standard

> So at least we should try to be predictable. reset = 0 always seems pretty predictable to me... > Resetting to 0 is too rude. because... > So with you proposal, I cannot set a paragraph to standard in an > enumeration easily anymore, right? that would be my M-return > Tsk, tsk, I will not

Re: resetting itemize to standard

Abdelrazak Younes <[EMAIL PROTECTED]> writes: > On 21/10/2008 15:35, leuven edwin wrote: >> i think i've made my case for >> >> 1. resetting depth to zero on a layout reset other than item/enum >> 2. bind M-return to creating a new paragraph that preserves the nesting. >> > > To enforce the cas

RE: resetting itemize to standard

> I use that :-) and you can still use it, but you would need to explicitly indent these sections (which makes more sense here i think) > I agree, however, that the expected case is non-nested for sections. my point indeed > For standard and quote and quotation, however, I'm not so sure. in w

Re: [PATCH] Re: Undo messages

Pavel Sanda <[EMAIL PROTECTED]> writes: > Jean-Marc Lasgouttes wrote: >> > i agree with the direction, but maybe its better to let the complete >> > cleanup for 1.7. i'm not in a mood to test again all the cases of >> > buffer reloading in VCS lfuns or so... for the time being i would be >> > much

Re: resetting itemize to standard

leuven edwin <[EMAIL PROTECTED]> writes: >> The convention that we have had for a long time in LyX is that >> We could change this convention, but I think some things that used to be >> intuitive will not remain so. > > and another sophism. My point is that having a behaviour that amounts to "if u

Re: resetting itemize to standard

On 21/10/2008 15:35, leuven edwin wrote: i think i've made my case for 1. resetting depth to zero on a layout reset other than item/enum 2. bind M-return to creating a new paragraph that preserves the nesting. To enforce the case (if need be) I might add: it is easier than ever to nest/un

RE: resetting itemize to standard

leuven edwin wrote: >> I understand that putting a section in a nesting seems weird but (1) >> LaTeX allows it and (2) I would not be suprised to find a class that >> uses that in some way (people do weird things). > > smells like a sophism to me... I use that :-) I have a beamer presentation wh

RE: resetting itemize to standard

> I understand that putting a section in a nesting seems weird but (1) > LaTeX allows it and (2) I would not be suprised to find a class that > uses that in some way (people do weird things). smells like a sophism to me... > Then it is a matter of educating our users, and maybe also to > make nes

Re: resetting itemize to standard

Abdelrazak Younes wrote: > On 21/10/2008 14:39, leuven edwin wrote: >> > if one resets the first nested to standard it is not immediate >> > clear what to do with the items that follow. >> >> i understand, but a standard paragraph seems to be the exception in >> the sense that one might or might

Re: resetting itemize to standard

On 21/10/2008 14:39, leuven edwin wrote: > if one resets the first nested to standard it is not immediate > clear what to do with the items that follow. i understand, but a standard paragraph seems to be the exception in the sense that one might or might not want to keep the nesting. i situa

Re: [PATCH] Re: Undo messages

Jean-Marc Lasgouttes wrote: > > i agree with the direction, but maybe its better to let the complete > > cleanup for 1.7. i'm not in a mood to test again all the cases of > > buffer reloading in VCS lfuns or so... for the time being i would be > > much happier with some light-weight version of the

Re: aspell without ispell

Stefan Schimanski <[EMAIL PROTECTED]> writes: > I think the problem is that I had installed ispell before and the > ispell command was set to ispell therefore and library mode was > disabled. But then I removed ispell from the system and recompiled > with aspell library support. If the combo box fo

Re: [PATCH] Re: Undo messages

Jean-Marc Lasgouttes wrote: > So shall I apply this flag part? yes pavel

Re: Problem converting index from 1.5

José Matos wrote: On Thursday 16 October 2008 19:30:51 Enrico Forestieri wrote: Note that \~ is always an accent. In order to get a ~ character, you should use \~{}, and indeed \textasciitilde is defined exactly so. Here José is using the italic correction \/ in place of {}, so the accent wou

Re: [PATCH] Re: Undo messages

Pavel Sanda <[EMAIL PROTECTED]> writes: > Jean-Marc Lasgouttes wrote: > i agree with the direction, but maybe its better to let the complete > cleanup for 1.7. i'm not in a mood to test again all the cases of > buffer reloading in VCS lfuns or so... for the time being i would be > much happier with

Re: [PATCH] Re: Undo messages

Pavel Sanda <[EMAIL PROTECTED]> writes: > ok > p So shall I apply this flag part? JMarc

Re: resetting itemize to standard

leuven edwin <[EMAIL PROTECTED]> writes: > i understand, but a standard paragraph seems to be the exception in > the sense that one might or might not want to keep the nesting. Another example would be an itemize in a theorem. Or anything in a theorem actually. I understand that putting a sectio

Re: aspell without ispell

That's what I am saying, you don't have to; Aspell support is compiled in, we don't use the executable. Well, then the autodetection to use the aspell lib support is not working. Without the patch, opening the spell checker dialog told me in a message box that spell checking is not activate

Re: Problem converting index from 1.5

José Matos wrote: > On Thursday 16 October 2008 19:30:51 Enrico Forestieri wrote: > > Note that \~ is always an accent. In order to get a ~ character, you > > should use \~{}, and indeed \textasciitilde is defined exactly so. > > Here José is using the italic correction \/ in place of {}, so the >

Re: resetting itemize to standard

leuven edwin wrote: This is indeed annoying but 2/ the real problem is this endframe business that is a kludge to use beamer with LyX. The real solution would probably be to use an InsetFlex instead. it is not only endframe, but if one switches from an itemize to a section, subsection, pa

Re: [PATCH-update] ProvidesModule, etc

rgheck wrote: OK, here's this patch one more time, updated to current trunk. Comments welcome. I'll commit some time Tuesday unless there are objections. By the way, does anyone know if the "by chapter" and "by section" modules should be included, excluded, or whatever from SIAM? I assume

Re: [PATCH] Re: Undo messages

Jean-Marc Lasgouttes wrote: > While the current patch is not perfect (I'll post a better one soon), it > is a step forward IMO. >I can make a light version of the patch (which > keeps all sorts of ugly code), but most of this code is harmless. i agree with the direction, but maybe its better to le

RE: resetting itemize to standard

> This is indeed annoying but > 2/ the real problem is this endframe business that is a kludge to use > beamer with LyX. The real solution would probably be to use an InsetFlex > instead. it is not only endframe, but if one switches from an itemize to a section, subsection, part etc this is not i

Re: [PATCH] Re: Undo messages

Jean-Marc Lasgouttes wrote: > Pavel Sanda <[EMAIL PROTECTED]> writes: > > Jean-Marc Lasgouttes wrote: > >> Pavel Sanda <[EMAIL PROTECTED]> writes: > >> >> This is not supposed to modify the document IMO. > >> > > >> > are you sure about the insetbibtex case? > >> > >> The way I read the code, it j

Re: [PATCH] Re: Undo messages

Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: > Uwe Stöhr <[EMAIL PROTECTED]> writes: > >>> I think anyway that the patch as I posted it is safe, but as we know the >>> devil is in the details. >> >> Why do you still think it is safe when it introduces a crash?: >> http://www.mail-archive.com/ly

Re: [PATCH] Re: Undo messages

Pavel Sanda <[EMAIL PROTECTED]> writes: > Jean-Marc Lasgouttes wrote: >> Pavel Sanda <[EMAIL PROTECTED]> writes: >> >> This is not supposed to modify the document IMO. >> > >> > are you sure about the insetbibtex case? >> >> The way I read the code, it just spawns an editor on the .bib files. But

Re: [PATCH] Re: Undo messages

Pavel Sanda <[EMAIL PROTECTED]> writes: > in such a case i seriously ask about the whole philosophy of that patch... > wouldn't be better to cache buffer only fo lfun we know that have the tendency > to switch to another buffer? reload came to my mind now, but who knows what > else can happen insid

Re: Problem converting index from 1.5

On Thursday 16 October 2008 19:30:51 Enrico Forestieri wrote: > Note that \~ is always an accent. In order to get a ~ character, you > should use \~{}, and indeed \textasciitilde is defined exactly so. > Here José is using the italic correction \/ in place of {}, so the > accent would be placed on

Re: [PATCH] Re: Undo messages

Jean-Marc Lasgouttes wrote: > Pavel Sanda <[EMAIL PROTECTED]> writes: > >> This is not supposed to modify the document IMO. > > > > are you sure about the insetbibtex case? > > The way I read the code, it just spawns an editor on the .bib files. But > please double check, I may be wrong. iirc som

Re: [PATCH] Re: Undo messages

Uwe Stöhr <[EMAIL PROTECTED]> writes: >> I think anyway that the patch as I posted it is safe, but as we know the >> devil is in the details. > > Why do you still think it is safe when it introduces a crash?: > http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg145234.html I am on the case. N

Re: [PATCH] Re: Undo messages

Jean-Marc Lasgouttes wrote: > Pavel Sanda <[EMAIL PROTECTED]> writes: > > Jean-Marc Lasgouttes wrote: > >> > this patch also touch lot of other code and i'm not sure about > >> > possible side effects. wouldn't be more clean solution introduce > >> > LFUN_INSET_OPEN for this specific task? > >> >

Re: resetting itemize to standard

On Tuesday 21 October 2008 13:00:57 leuven edwin wrote: > j-m wrote: > > I do not think so :) > > care to elaborate? It is common to have standard paragraphs nested on deeper environments. To reset to depth 0 for such cases would be a serious regression to lyx behaviour. -- José Abílio

Re: [PATCH] Re: Undo messages

Pavel Sanda <[EMAIL PROTECTED]> writes: > Jean-Marc Lasgouttes wrote: >> > this patch also touch lot of other code and i'm not sure about >> > possible side effects. wouldn't be more clean solution introduce >> > LFUN_INSET_OPEN for this specific task? >> >> As I understand it, only the changes to

Re: [PATCH] Re: Undo messages

Pavel Sanda <[EMAIL PROTECTED]> writes: >> This is not supposed to modify the document IMO. > > are you sure about the insetbibtex case? The way I read the code, it just spawns an editor on the .bib files. But please double check, I may be wrong. JMarc

Re: resetting itemize to standard

leuven edwin <[EMAIL PROTECTED]> writes: > j-m wrote: >> I do not think so :) > > care to elaborate? See me answer to the initaial message. JMarc

Re: resetting itemize to standard

leuven edwin <[EMAIL PROTECTED]> writes: > when i reset the last line in the attached document (which is a nested > item) to standard, the paragraph is still part of the itemizing > environment. Yes. > someone at work who was not aware of this behavior did something > similar and reset a nested

Re: [PATCH] Re: Undo messages

Jean-Marc Lasgouttes wrote: > > this patch also touch lot of other code and i'm not sure about > > possible side effects. wouldn't be more clean solution introduce > > LFUN_INSET_OPEN for this specific task? > > As I understand it, only the changes towards the end (startig from the > default: hand

RE: resetting itemize to standard

j-m wrote: > I do not think so :) care to elaborate?

Re: missing es/clipart images

Pavel Sanda <[EMAIL PROTECTED]> writes: > Joost Verburg wrote: >> Ignacio García wrote: >>> Uwe Stöhr wrote >>> p.s. There are several es/clipart images missing in rc3 > What is missing? Please report this critical bug to the lyx-devel > mailing list > and CC the mail to our rele

Re: resetting itemize to standard

leuven edwin <[EMAIL PROTECTED]> writes: >> Arghh, I did not have time yet to look at it... even to the initial >> problem. > > it is very simple; we should set the depth parameter to zero when > resetting a paragraph to say standard (or section etc). I do not think so :) JMarc

Re: [PATCH] Re: Undo messages

Jean-Marc Lasgouttes wrote: > Pavel Sanda <[EMAIL PROTECTED]> writes: > > except the reported crash i wonder about the change of inset from > > mutable to readonly - in the other cases we want to be inset-edit > > mutable. > > I read: > > /*! > * \var lyx::FuncCode lyx::LFUN_INSET_EDIT > * \li

Re: missing es/clipart images

Joost Verburg wrote: > Ignacio García wrote: >> Uwe Stöhr wrote >> p.s. There are several es/clipart images missing in rc3 What is missing? Please report this critical bug to the lyx-devel mailing list and CC the mail to our release maintainer Jos??(c) Matos: jamatos/at\f

Re: The tex4ht changes: please test!

Abdelrazak Younes wrote: > >> The UserGuide doesn't work for me either. I suspect it's simply too >> complex for htlatex. Does the Tutorial work? >> Here (Debian Sid, LyX SVN, tex4ht 20080701-2) it works for the tutorial. Cheers, Charles -- http://www.kde-france.org

Re: [PATCH] Re: Undo messages

> I think anyway that the patch as I posted it is safe, but as we know the > devil is in the details. Why do you still think it is safe when it introduces a crash?: http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg145234.html regards Uwe

Re: The tex4ht changes: please test!

> Do we need to add zip.exe to the installers? It should of course be added to MiKTeX. No, because MiKTeX has to ship it, otherwise tex4ht would still be unusable. I sent the MiKTeX-developer the link to the project from where you built your zip.exe, and he replied that he will use it when the

RE: the error list

it is in: http://www.lyx.org/trac/changeset/27007 edwin From: José Matos [EMAIL PROTECTED] On Tuesday 21 October 2008 07:40:38 Jürgen Spitzmüller wrote: > rgheck wrote: > > Seems perfectly sensible to me. > > +1 OK. > Jürgen -- José Abílio

RE: resetting itemize to standard

> Arghh, I did not have time yet to look at it... even to the initial > problem. it is very simple; we should set the depth parameter to zero when resetting a paragraph to say standard (or section etc). the only case where we would like to preserve the nesting depth is if we switch from an item

Re: [PATCH] Re: Undo messages

Pavel Sanda <[EMAIL PROTECTED]> writes: > except the reported crash i wonder about the change of inset from > mutable to readonly - in the other cases we want to be inset-edit > mutable. I read: /*! * \var lyx::FuncCode lyx::LFUN_INSET_EDIT * \li Action: Edit the inset at cursor with an externa

Re: Navigation Bug

rgheck <[EMAIL PROTECTED]> writes: > This seems to be because InsetText::addToToc() calls par.asString() > without the AS_STR_INSETS option. It'd be easy to add that, but is > that exactly what we want? or do we need another option? In the old times we used to have plainText() to output an inset i

Re: [PATCH] Re: Undo messages

On 21/10/2008 10:16, Jean-Marc Lasgouttes wrote: Abdelrazak Younes<[EMAIL PROTECTED]> writes: Could you try this patch? I think it works, but since it is a bit lng... The idea is to differentiate the buffer before and after dispatch. The buffer should not change for the LFUN handle

Re: [PATCH] Re: Undo messages

Abdelrazak Younes <[EMAIL PROTECTED]> writes: >> Could you try this patch? I think it works, but since it is a bit >> lng... The idea is to >> differentiate the buffer before and after dispatch. > The buffer should not change for the LFUN handled in > LyXFunc::dispatch(). If it changes this mean th

Re: The tex4ht changes: please test!

Uwe Stöhr wrote: > Adding zip.exe to the Miktex bin directory solved the problem. This is a known MiKTeX bug that will be solved in a few days, see also http://bugzilla.lyx.org/show_bug.cgi?id=4730 Do we need to add zip.exe to the installers? It should of course be added to MiKTeX. Joost

Re: rc4 release schedule

Stefan Schimanski schrieb: Am 21.10.2008 um 09:29 schrieb Stephan Witt: Abdelrazak Younes schrieb: On 20/10/2008 13:41, Konrad Hofbauer wrote: José Matos wrote: Comments are welcome, On the Mac-side of things, there would be one/three mustfix-bugs for 1.6:

Re: missing es/clipart images

Ignacio García wrote: Uwe Stöhr wrote p.s. There are several es/clipart images missing in rc3 What is missing? Please report this critical bug to the lyx-devel mailing list and CC the mail to our release maintainer JosÃ(c) Matos: jamatos/at\fc.up.pt lyx-1.6.0rc3, in the directory ..lib/do

missing es/clipart images

Uwe Stöhr wrote >> >> p.s. There are several es/clipart images missing in rc3 >> What is missing? Please report this critical bug to the lyx-devel mailing >> list >> and CC the mail to our release maintainer JosÃ(c) Matos: jamatos/at\fc.up.pt lyx-1.6.0rc3, in the directory ..lib/doc/es/clipart

Re: rc4 release schedule

On 21/10/2008 09:33, Stefan Schimanski wrote: Am 21.10.2008 um 09:29 schrieb Stephan Witt: Abdelrazak Younes schrieb: On 20/10/2008 13:41, Konrad Hofbauer wrote: José Matos wrote: Comments are welcome, On the Mac-side of things, there would be one/three mustfix-bugs for 1.6:

Re: [PATCH] Re: Undo messages

On 20/10/2008 23:32, Jean-Marc Lasgouttes wrote: Le 20 oct. 08 à 17:29, Jean-Marc Lasgouttes a écrit : Pavel Sanda <[EMAIL PROTECTED]> writes: i have the feeling it happens in more different cases. on example is opening file with include insets, edit the child document (via context menu). now a

Re: rc4 release schedule

On 21/10/2008 09:29, Stephan Witt wrote: Abdelrazak Younes schrieb: On 20/10/2008 13:41, Konrad Hofbauer wrote: José Matos wrote: Comments are welcome, On the Mac-side of things, there would be one/three mustfix-bugs for 1.6: Crash. No id

Re: rc4 release schedule

Am 21.10.2008 um 09:29 schrieb Stephan Witt: Abdelrazak Younes schrieb: On 20/10/2008 13:41, Konrad Hofbauer wrote: José Matos wrote: Comments are welcome, On the Mac-side of things, there would be one/three mustfix-bugs for 1.6: Crash.

Re: rc4 release schedule

Abdelrazak Younes schrieb: On 20/10/2008 13:41, Konrad Hofbauer wrote: José Matos wrote: Comments are welcome, On the Mac-side of things, there would be one/three mustfix-bugs for 1.6: Crash. No idea what Pixmap cache is good for, docu says