Re: Multiple Indexes
rgheck wrote: > a couple minor UI things. I have recorded it on track. I'll come back to it. Jürgen
Re: r33007 - lyx-devel/trunk/lib/doc
Guenter Milde wrote: > Not all fonts will replace --- by an em-dash. Can you name an example? Jürgen
Re: [Cvslog] r28703 - /lyx-devel/trunk/src/mathed/InsetMathGrid.cpp
Jean-Marc Lasgouttes wrote: > This should eventually go to branch, but there is no need to hurry. The decision is up to you. Jürgen
Re: Context menu of some collaps insets
Pavel Sanda wrote: > btw when do you plan to release it? There is one outstanding issue which should be fixed, since it potentially results in really bad dataloss: http://bugzilla.lyx.org/show_bug.cgi?id=5813 Apart from that, we are ready. Unfortunately, I'm totally blocked by real work, so I cannot look into the issue myself (I would have time to set up the release at the weekend, though, if someone came up with a patch). Next week, I will be offline, so if we don't make it this week, the release will have to wait for one further week. Jürgen
Re: Context menu of some collaps insets
Pavel Sanda wrote: > just found box and note insets do not have open/close item in their > context menu. i'll add them unless comebody complains. You can submit to 1.6.2svn, if exactly these strings are already in the *.po files (i.e., including the accelerators). If the commit generates new strings to translate, please wait for 1.6.3. Jürgen
Re: Regression in branch
Vincent van Ravesteijn wrote: > Also for branch ? Yes, this looks good. Jürgen
Re: Regression in branch
Pavel Sanda wrote: > ert no more displays the text inside when collapsed. this must have > changed in last few days. i dont have time to inspect more atm. I think the cause is the fix to bug 4346. Now, InsetERT and others have setButtonLabel(BufferView const & bv), but InsetCollapsable still calls setButtonLabel() (without argument). I guess InsetERT's own method does not get triggered when it should. Vincent? Jürgen
Re: [Cvslog] r28596 - /lyx-devel/trunk/src/BufferView.cpp
Vincent van Ravesteijn wrote: > Also for branch ? Yes. Jürgen
Re: [Cvslog] r28593 - in /lyx-devel/trunk/src/frontends/qt4: GuiRef.cp...
Pavel Sanda wrote: > i suppose this has green light to 1.6.3? Yes. Jürgen
Re: [Cvslog] r28588 - /lyx-devel/trunk/src/insets/InsetText.cpp
Vincent van Ravesteijn wrote: > Also for branch ? Yep. Jürgen
Re: [patch] Bug 5797: Assertion in getStatus
Vincent van Ravesteijn wrote: > Is the attached fix OK ? makes sense to me. Jürgen
RE: RE: Re: Bugs 5744 and 5746 (crashes)
Vincent van Ravesteijn - TNW wrote: > Yes, sorry for that. No need for that. You made me *LOL*. (Apart from that, it's friday). Jürgen
Re: Request for backport of minibuffer stack
Pavel Sanda wrote: > Juergen? I need to have a closer look, but let us first finish 1.6.2, please. Jürgen
RE: Re: Bugs 5744 and 5746 (crashes)
Vincent van Ravesteijn - TNW wrote: > I don't understand the logic. [...] > Jürgen what do I need to say more? (my idea was that innerParagraph() calls innerTextSlice().paragraph(), so we have to check first if an innerTextSlice() actually exists. But as you correctly guessed, I probably do not understand the logic) Jürgen
Re: Bugs 5744 and 5746 (crashes)
Vincent van Ravesteijn wrote: > The attached patch 'solves' these two bugs, but it feels like a dirty fix. How about checking for innerTextSlice() instead? Jürgen Index: src/BufferView.cpp === --- src/BufferView.cpp (Revision 28566) +++ src/BufferView.cpp (Arbeitskopie) @@ -2417,6 +2417,8 @@ return true; if (a.empty() || b.empty()) return false; + if (&a.innerTextSlice() || &b.innerTextSlice()) + return false; return &a.innerParagraph() == &b.innerParagraph(); }
RE: Re: [Cvslog] r28563 - /lyx-devel/trunk/src/insets/InsetInclude.cpp
Vincent van Ravesteijn - TNW wrote: > Just try it... Sorry for not doing that. I am quite busy ATM. > I really wonder why nobody has complained about this. Looks > like Bo is the only one using it and he never removed a label. Personally, I do not need listings, so the chance it hits me is low. Jürgen
Re: [Cvslog] r28563 - /lyx-devel/trunk/src/insets/InsetInclude.cpp
Vincent van Ravesteijn wrote: > Also for branch ? Does this apply to branch or is it part of the recent fix to the child label update that is not yet in branch? If the crash is in branch as well, then apply. Jürgen
Re: Bugs 5744 and 5746 (crashes)
Vincent van Ravesteijn wrote: > The attached patch 'solves' these two bugs, but it feels like a dirty fix. I cannot say anything about the patch, but in any case, I'd like to have a fix for these bugs in, even if it delays the release for some days. Jürgen
Re: [Cvslog] r28547 - /lyx-devel/trunk/src/frontends/qt4/GuiRef.cpp
Vincent van Ravesteijn wrote: > Also for branch ? Yes, please. Jürgen
Re: [RFC][PATCH] Literate modules (noweb and sweave)
Jean-Marc Lasgouttes wrote: > Not really, flex insets with spaces in their name is not related to this > module. This is a trivial fix, really. OK, put it in. Jürgen
Re: [RFC][PATCH] Literate modules (noweb and sweave)
Jean-Marc Lasgouttes wrote: > Juergen, this would be for branch too. This is for 1.6.3, right? Jürgen
Re: r28539 - /lyx-devel/branches/BRANCH_1_6_X/po/cs.po
Pavel Sanda wrote:
> wrong,
well, the code in question (in branch) reads:
if (!fileName.empty()) {
maximize_title = fileName.displayName(30);
minimize_title = from_utf8(fileName.onlyFileName());
if (buf.lyxvc().inUse())
maximize_title += _(" (version control)");
if (!buf.isClean()) {
maximize_title += _(" (changed)");
minimize_title += char_type('*');// <-- this is
GuiWorkarea.cpp:1136
}
if (buf.isReadonly())
maximize_title += _(" (read only)");
}
I cannot see the string here.
> i have wrote about that privately, but it probably ended in spam
> folder.
Not necessarily. I do not have access to my private mailbox ATM.
> the issue is that my gettext is another version and produces
> megabytes of patch code doing only reformating. the same is with Uwe. this
> is not only wasting of space resources but also complicates resolving
> merge conflicts etc. imho only one should do the remerges or we should
> unify how remerging is done.
Both fine with me. If the former, it's probably me who has to do the job,
since I need to remerge at least while setting up the release.
Jürgen
Re: r28539 - /lyx-devel/branches/BRANCH_1_6_X/po/cs.po
sanda wrote: > +#: src/frontends/qt4/GuiWorkArea.cpp:1136 > +msgid " (version control, locking)" > +msgstr " (správa verzí, zamykání)" Pavel, I don't think this string is already in branch. It won't hurt, but it will probably disappear again with my next remerge. Jürgen
Re: [patch] fix bug 5772 for branch
Uwe Stöhr wrote: > No this always triggers, see for example the attached file. I see. Put it in then. I take it that this is tested well. Jürgen
Re: [patch] fix bug 5772 for branch
Uwe Stöhr wrote: > OK for branch? This only triggers if the caption is not in the first row, right? If so, I'd like to postpone this to 1.6.3. We have already too much major changes in 1.6.2, I'd like to focus on the crashes and very straightforward changes now. > Is http://www.lyx.org/trac/changeset/28464 also OK for branch? This one is OK. Jürgen
Re: [patch] support for \frontmatter and the like (also for branch)
Uwe Stöhr wrote: > I cannot work on complex issues like this, because I'm at finishing my > thesis. Very fair. Good luck with that (how is it proceeding?) > > I did not get any private mail from you lately, so apparently they got > lost > in cyberspace, unfortunately. To which address did you send them? > t-online? > > Yes. The mails were about your new Thesaurus feature and questions to put > a fixed installer version to ftp.lyx.org: > > - Since 4 weeks I provide a fixed Win installer (version 4.17), but on > ftp.lyx.org is still version 4.16 I'll have a look at the weekend. > - Your thesaurus description in the UserGuide contain a dead link, and one > link is only available in German, we cannot refer to in the English > UserGuide. I see. This was an English site once. So please remove that link, I think the openoffice site alone is enough. BTW as of MyThes, I think we should provide it on our server. Also, since there's only the source available (without a proper build infrastructure), we should also provide binaries for Windows and the Mac. > What email address should I use for the next attempt? try juergen at spitzmueller dot org. Jürgen
Re: [Cvslog] r28428 - /lyx-devel/trunk/src/frontends/qt4/GuiView.cpp
Pavel Sanda wrote: > of course i was expecting what Juergen offers... You'll get brunch if you show up here. Jürgen
Re: [patch] fix bug 5752
Uwe Stöhr wrote: > It is in trunk now. Do you want this for branch too? yes, please. Jürgen
Re: [patch] support for \frontmatter and the like (also for branch)
Uwe Stöhr wrote: > I see now your point. So the implementation similar to \appendix is the > only thing solving these issues. OK. If you try to have a go at this, I'll try to help where I can. > p.s. Can it be that private mails from me to you never reached you? (I > haven't got any reply yet.) I did not get any private mail from you lately, so apparently they got lost in cyberspace, unfortunately. To which address did you send them? t-online? Jürgen (note that I'm not at home for a few days now and won't be able to check my private mailbox. I'm scanning the list via gmane from time to time).
RE: [Fwd: r26668 - /lyx-devel/trunk/src/insets/InsetTabular.cpp]
leuven edwin wrote:
> patch attached. copy pasting from abdel's. cannot test it here (1.5 does
> not build with cmake for me), perhaps someone else can...
OK, this compiles. However, I wonder why we need to introduce
selIsMultiCell() in Cursor. Tabular::tablemode gives us the same
information. See attached patch.
It works for me, but I'd appreciate some testing before putting it into
branch.
Jürgen
Index: src/insets/InsetTabular.cpp
===
--- src/insets/InsetTabular.cpp (Revision 26674)
+++ src/insets/InsetTabular.cpp (Arbeitskopie)
@@ -3235,6 +3235,10 @@
setCursorFromCoordinates(cur, cmd.x, cmd.y);
bvcur.setCursor(cur);
bvcur.selection() = true;
+ if (tablemode(bvcur)) {
+ bvcur.pit() = bvcur.lastpit();
+ bvcur.pos() = bvcur.lastpos();
+ }
} else
cur.undispatched();
}
@@ -3301,6 +3305,11 @@
cmd = FuncRequest(LFUN_FINISHED_RIGHT);
cur.undispatched();
}
+ if (tablemode(cur)) {
+ cur.pit() = cur.lastpit();
+ cur.pos() = cur.lastpos();
+ return;
+ }
break;
case LFUN_UP_SELECT:
@@ -3324,6 +,11 @@
cmd = FuncRequest(LFUN_UP);
cur.undispatched();
}
+ if (tablemode(cur)) {
+ cur.pit() = cur.lastpit();
+ cur.pos() = cur.lastpos();
+ return;
+ }
break;
// case LFUN_SCREEN_DOWN: {
@@ -3415,6 +3429,14 @@
cell(cur.idx())->dispatch(cur, cmd);
break;
+ case LFUN_SELF_INSERT:
+ if (tablemode(cur)) {
+ recordUndoInset(cur, Undo::DELETE);
+ cutSelection(cur);
+ }
+ cell(cur.idx())->dispatch(cur, cmd);
+ break;
+
case LFUN_COPY:
if (!cur.selection())
break;
@@ -4003,6 +4025,16 @@
return;
++cur.idx();
}
+
+ cur.boundary(false);
+
+ if (tablemode(cur)) {
+ cur.pit() = cur.lastpit();
+ cur.pos() = cur.lastpos();
+ resetPos(cur);
+ return;
+ }
+
cur.pit() = 0;
cur.pos() = 0;
resetPos(cur);
@@ -4028,6 +4060,14 @@
return;
--cur.idx();
}
+
+ if (tablemode(cur)) {
+ cur.pit() = cur.lastpit();
+ cur.pos() = cur.lastpos();
+ resetPos(cur);
+ return;
+ }
+
cur.pit() = cur.lastpit();
cur.pos() = cur.lastpos();
RE: [Fwd: r26668 - /lyx-devel/trunk/src/insets/InsetTabular.cpp]
leuven edwin wrote: >> Author: younes >> URL: http://www.lyx.org/trac/changeset/26668 > > the same bug seems to be present in 1.5, so perhaps this is a candidate > for branch as well... Indeed. Could somebody prepare a patch? I don't have time ATM to do it myself. Jürgen
Re: r26666 - in /lyx-devel/trunk: development/scons/scons_man...
[EMAIL PROTECTED] wrote: > Can also be done for branch Jürgen? OK. Jürgen
Re: [Cvslog] r26670 - /lyx-devel/trunk/src/ServerSocket.cpp
Jean-Marc Lasgouttes wrote: > Juergen, I guess it is OK for branch too? Yes, sure. Jürgen
Re: rc4 and later
Abdelrazak Younes wrote: >> I think we should aim at fixing all the critical bugs for the 1.6.0 >> release (given that we can reproduce it and that fixing does not mean >> "wait until Abdel finds the time to do it"). >> > > That's more or less what I meant by 1.6.x ;-) > The more the better of course. OK. But then we should postpone critical bugs to 1.6.1, not 1.6.x (I'll create a target when necessary). Jürgen
Re: [patch] Tabbing in listings
Pavel Sanda wrote: >> Et voila, .. (oh no, no more french on the list...) > > i just tried this patch and seems to work correctly. > if there are no other comments, i'll put it in. > lfuns will be sorted later. I wonder if something needs to be done on reversion to 1.5.x. IOW, is this a file format change? Jürgen
Re: question 3 of x - help to update the docs for 1.6.0
Uwe Stöhr wrote: > The document settings menu has a new filed to specify a master document. I > haven't followed the development of this feature. How does it work? What > is taken from the master document and what not (bibliography, index, > etc.)? In LyX 1.5 I don't have to specify a master document, what are the > differences to the way we handle master/child document in LyX 1.5? You do not need to open the master document. Just open the child document, and you automatically have access to the master buffer. This means you have access to the citation keys of the master without having to add a bibtex inset in a note inset, to the labels, etc. Furthermore, you can directly compile the master via master-buffer-view. In 1.5, this was only possible after you have opened the child _from_ the master. Jürgen
Re: question 1 of x - help to update the docs for 1.6.0
Uwe Stöhr wrote: > In the document settings menu there is under Fonts a new field "CJK" with > the tooltip that one can enter there the font for CJK script. How is the > font name entered, is it a file name like "kanji3.pfb" or just the name of > the font like "kanji-c"? The latter (e.g. "song"). It's the second mandatory argument of the CJK environment. Jürgen
Re: question 2 of x - help to update the docs for 1.6.0
Uwe Stöhr wrote: > The document settings dialog provides under Bibliography a new option > "Sectioned bibliography". I don't understand how this option works, I mean > how and what is sectioned? The option loads the bibtopic package but its > documentation tells me that I have to use some additional ERT commands to > set up the sectionings. This is not new. 1.5 has it as well (I think even 1.4). And it's documented in Extended.lyx 3.1.2. ERT should not be needed. Jürgen
Re: Layout Combo Bug
Richard heck wrote: > Open a new file and create a table. Put the cursor into the table with > the mouse. The layout combo is now disabled. Put the cursor in a > different cell with the mouse. Still disabled. Now move it with the > arrow keys. Enabled! Now type some characters. Disabled! Fixed at http://www.lyx.org/trac/changeset/25677 Jürgen
Re: python help needed
rgheck wrote: > I finally got around to doing this. I've also re-written the latex2lyx > conversion routine so that it uses the unicodesymbols file. > > I'm not sure exactly what you had in mind for convert_subfig, as I don't > know anything about figures, but perhaps this will let you do it now? Thanks, it's fixed. While you are at it, could you also have a look at bug 5006? Jürgen
Re: Proof of concept patch for bug 4812.
Bo Peng wrote: > 1. A document without valid layout will be opened with a warning. (The > same) 2. All layouts are usable, although they all look like "standard" > (changed) 3. Save such a document will not lose data. The original layout > name will be used. (improved) > 4. Another layout can be chosen from Document -> settings, if a > correct textclass is selected, all layouts will work fine. (improved, > because the current approach will change some unknown layouts to > standard.) This looks like a sensible approach in general. Is the document class then not reset? So if I have ClassX, and this is not found, will LyX keep this ClassX unless I manually switch to another class? (This is the way it should be IMHO). Generally speaking, I'm glad to see that the hiding of the browse button finally triggered some action. Actually, this is what I intended with this rather rude step ;-) Jürgen
Re: Bug notice for Joost
Joost Verburg wrote: > Can you upload the 1.5.5-3 installers from http://www.lyx.org/~joost/ to > ftp.lyx.org? Thanks. Done. Could you please change the links od the download page? I do not have the password at hand. Thanks, Jürgen
Re: [patch] support CJK font argument
instanton wrote:
> \RequirePackage{CJK}
> \AtBeginDocument{\begin{CJK*}{GBK}{}\CJKtilde\CJKcaption{GB}}
> \AtEndDocument{\end{CJK*}}
>
> in the preamble, rather than having
>
> \begin{CJK*}{GBK}{}
>
> at the begining and
>
> \end{CJK*}
>
> in the ending.
In the cases I talk about, the CJK string does not necessarily be at the
beginning. We need to support documents that start in English, then have a
Chinese quote, switch to German, then quote Japanese, have some Greek terms
and return to Chinese. In the CJK case, the CJK tags have to be opened and
closed every time properly, and furthermore, nesting has to be taken into
account. That's why we need this kind of hardcoding.
Anyway, I think what you want can be easily implemented on a per-layout
basis (with the Provides tag).
> Yes, I meant CJK*, as this is preferred than just CJK.
We could add an option to switch on the starred version, since some users
seem to prefer CJK over CJK*.
Jürgen
Re: [patch] support CJK font argument
instanton wrote:
> These extra document classes depends on CJK implicitly which means that
> one needs not add \usepackage{CJK} in the preamble and also needs not to
> put \begin{CJK}{GBK}{} after \begin{document} and \end{CJK} before
> \end{document}. These document classes are much more popular among Chinese
> users than using the standard documentclasses with the aid of CJK, because
> better sectioning and numbering systems are implemented in the cct and
> ctex series of classes.
OK, then we should implement
Provides CJK
in the layout file.
Please file a bug report for this.
> Therefore, I strongly suggest that LyX should remove all the hard codes
> which explicitly refers to the use of CJK packages and only takes care
> that the correct Chinese characters can be imported/exported with
> appropriate encodings. If this to be the case we can make our own .layout
> files to make use of any of the above-mentioned cct or ctex series of
> classes.
This is not possible. We also want to support users who want to cite CJK
content in non-CJK documents (linguists come to mind).
Jürgen
Bug notice for Joost
http://bugzilla.lyx.org/show_bug.cgi?id=4894 Your friendly bug alert service ...
python help needed
In order to fully fix bug 4927, we need to do some LaTeX->LyX conversion, because subfigure captions can contain LaTeX constructs such as \label. Currently, subcaptions with such constructs are simply eaten (i.e., dataloss). I think we should factor out the routines of convert_latexcommand_index to a helper function which is used by convert_latexcommand_index, convert_subfig and maybe others. I failed at doing this due to limited python knowledge. I'd appreciate if someone could jump in (and maybe also clean up my really ugly convert_subfig routine). Thanks in advance, Jürgen
Re: About the filename combo in the cross-reference dialog
Abdelrazak Younes wrote: >> Opinions? > None? Jürgen maybe? If it is superfluous now, hide it. In the long term, I think we should try to implement xr support. Jürgen
Re: siam layout
Andrew Corrigan wrote: > I tried using the layout file you posted and so far it works great. I'll > report back if I experience any issues. If you can use redefinitions so > that it uses 'thm' instead of 'theorem', which I think was an intentional > change to make it work with the SIAM document class, then please let it > just include the AMS files. OK. This is what it does now. > I probably got rid of starred versions of > theorems and other theorem types because if I remember correctly they > weren't used by the SIAM document class. I can look into this more in > two weeks (after qualifiers) if it would still be helpful at that point. > > In general, please feel free to make any changes you'd like to, I don't > expect my permission to be sought. Andrew, just take your time and test it, since I have no experience with the SIAM class. We're not in a hurry yet. Jürgen
Re: floats handling on x64
Enrico Forestieri wrote: > This is a locale problem. I see it both on 64 and 32 bit machines. > I don't see it when launching lyx using LC_ALL=C. Hm. I will check that. > When using a locale where the bug occurs, I should enter 3,5 instead > of 3.5, but the validator doesn't enable the OK or Apply buttons. > It must have been written by one of those yankees ;-) I guess this would be not very hard to fix (and actually, it would be an improvement. Jürgen
Re: An advice for Lyx to support CJK.
Bo Peng wrote:
> I would add that XXX in \begin{CJK}{GBK}{XXX} is sometimes required.
> My last attempt to use lyx for Chinese characters have failed due to
> this.
BTW I read in the CJK docs that you can also use
\CJKfamily{XXX} after a \begin{CJK}{GBK}{} command. So at least there's a
workaround.
Jürgen
Re: An advice for Lyx to support CJK.
steadycookie wrote: > No need a list of fonts. You can just let user have option to configure > the commands to invoke a language. As I said above, there are options in > menu, but they are overlaid by the hardcoded commands. And is this something the user should be able to configure per-document (in document->settings) or globally (in preferences)? Jürgen
Re: Providing layout and template files to include with LyX
rgheck wrote: > I think these are generally welcome. But they should probably be updated > to 1.6 at this point, as I'm not sure whether they'll be included in > later 1.5 releases. They could be included to 1.5.6. Jürgen
Re: An advice for Lyx to support CJK.
Bo Peng wrote:
> I would add that XXX in \begin{CJK}{GBK}{XXX} is sometimes required.
> My last attempt to use lyx for Chinese characters have failed due to
> this.
What would be the possible options we should provide? A list of fonts?
Jürgen
Re: r24879 - /lyx-devel/trunk/src/insets/InsetTabular.cpp
Abdelrazak Younes wrote: > The fix looks obvious to me but maybe I am missing something? I cannot remember exactly. But if it works ... Jürgen
Re: [Patch 1.5] bug 4857
Abdelrazak Younes wrote: > Hum, it looks like I didn't send the patch :-) Here it is. This fixes it for me as well. Well done! Note that gcc complained about this: > const Index: Paragraph.h > === > --- Paragraph.h (revision 24874) > +++ Paragraph.h (working copy) > @@ -101,6 +101,8 @@ > bool isMultiLingual(BufferParams const &) const; > > /// > + docstring const Paragraph::printableString(bool label) const; should be + docstring const printableString(bool label) const; Please commit. Jürgen
Re: [Patch 1.5] bug 4857
Abdelrazak Younes wrote: > I tried many times but I can't reproduce... a glibc specific issue perhaps? > Is there any macro in the document? No. >> #7 0x08075b98 in lyx::Buffer::buildMacros (this=0x8b64578) >> at /usr/include/c++/4.2.1/bits/stl_map.h:228 >> > This doesn't give me at which line it happens but I guess it is one of > those two: > > MathMacroTemplate const & mac > = static_cast(*it->inset); > insertMacro(mac.name(), mac.asMacroData()); or maybe this 1736pimpl_->macros = MacroTable::globalMacros(); I uncommented the debug code just before the lines you cited and it gives me this before the crash: found inset code 9 found inset code 14 found inset code 9 found inset code 14 found inset code 9 found inset code 14 found inset code 9 found inset code 14 found inset code 9 found inset code 14 found inset code 9 found inset code 14 These are LABEL_CODE (9) and INCLUDE_CODE (14), so it should not get into the line you quoted. However, it looks like a loop (there are only 2 includes and two labels in the master, and no includes in the childs). Maybe buildMacros is called recursively? Jürgen
Re: [Patch 1.5] bug 4857
Abdelrazak Younes wrote: > Do you have a recipe? Open the test file from the bug report, click on one label in the master, edit, press OK. The crash does not occur regularly. The output I sent was produced after closing LyX (without previous crash, obviously). However, I managed to get a backtrace with the above procedure. It seems MacroData is involved: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb71476d0 (LWP 23509)] 0xb71b2164 in free () from /lib/libc.so.6 (gdb) bt #0 0xb71b2164 in free () from /lib/libc.so.6 #1 0xb7366a61 in operator delete () from /usr/lib/libstdc++.so.6 #2 0xb735e67d in std::basic_string, std::allocator >::_Rep::_M_destroy () from /usr/lib/libstdc++.so.6 #3 0x0808d6b2 in std::_Rb_tree, std::allocator >, std::pair, std::allocator > const, lyx::MacroData>, std::_Select1st, std::allocator > const, lyx::MacroData> >, std::less, std::allocator > >, std::allocator, std::allocator > const, lyx::MacroData> > >::_M_erase (this=0x8b63620, __x=0x8c3b160) at /usr/include/c++/4.2.1/bits/basic_string.h:238 #4 0x0808d5b6 in std::_Rb_tree to continue, or q to quit--- _t>, std::allocator >, std::pair, std::allocator > const, lyx::MacroData>, std::_Select1st, std::allocator > const, lyx::MacroData> >, std::less, std::allocator > >, std::allocator, std::allocator > const, lyx::MacroData> > >::_M_erase (this=0x8b63620, __x=0x8c3b130) at /usr/include/c++/4.2.1/bits/stl_tree.h:1323 #5 0x0808d5b6 in std::_Rb_tree, std::allocator >, std::pair, std::allocator > const, lyx::MacroData>, std::_Select1st, std::allocator > const, lyx::MacroData> >, std::less, std::allocator > >, std::allocator to continue, or q to quit--- c_string, std::allocator > const, lyx::MacroData> > >::_M_erase (this=0x8b63620, __x=0x8c3b700) at /usr/include/c++/4.2.1/bits/stl_tree.h:1323 #6 0x0808dd09 in std::_Rb_tree, std::allocator >, std::pair, std::allocator > const, lyx::MacroData>, std::_Select1st, std::allocator > const, lyx::MacroData> >, std::less, std::allocator > >, std::allocator, std::allocator > const, lyx::MacroData> > >::operator= (this=0x8b63620, [EMAIL PROTECTED]) at /usr/include/c++/4.2.1/bits/stl_tree.h:711 #7 0x08075b98 in lyx::Buffer::buildMacros (this=0x8b64578) at /usr/include/c++/4.2.1/bits/stl_map.h:228 ---Type to continue, or q to quit--- #8 0x080bf076 in lyx::BufferView::update (this=0x89f9828, flags=lyx::Update::None) at BufferView.cpp:310 #9 0x081bac64 in lyx::LyXFunc::dispatch (this=0xc28, [EMAIL PROTECTED]) at LyXFunc.cpp:1887 #10 0x08185c9a in lyx::dispatch ([EMAIL PROTECTED]) at LyX.cpp:1513 #11 0x08371a37 in loadIfNeeded ([EMAIL PROTECTED], params=) at InsetInclude.cpp:410 #12 0x083722b4 in lyx::InsetInclude::getLabelList (this=0x8b77340, [EMAIL PROTECTED], [EMAIL PROTECTED]) at InsetInclude.cpp:729 #13 0x08074617 in lyx::Buffer::getLabelList (this=0x8b64578, [EMAIL PROTECTED]) at Buffer.cpp:1350 #14 0x08076186 in lyx::Buffer::changeRefsIfUnique (this=0x8b64578, [EMAIL PROTECTED], [EMAIL PROTECTED], code=lyx::Inset::REF_CODE) at Buffer.cpp:1783 ---Type to continue, or q to quit--- #15 0x08379a5e in lyx::InsetLabel::doDispatch (this=0x8b772e0, [EMAIL PROTECTED], [EMAIL PROTECTED]) at InsetLabel.cpp:71 #16 0x0830f6fe in lyx::Inset::dispatch (this=0x8b772e0, [EMAIL PROTECTED], [EMAIL PROTECTED]) at Inset.cpp:145 #17 0x081b8302 in lyx::LyXFunc::dispatch (this=0xc28, [EMAIL PROTECTED]) at LyXFunc.cpp:1649 #18 0x08185c9a in lyx::dispatch ([EMAIL PROTECTED]) at LyX.cpp:1513 #19 0x08407263 in lyx::LyXView::dispatch (this=0x898ec8c, [EMAIL PROTECTED]) at LyXView.cpp:514 #20 0x0859c7f2 in lyx::frontend::Kernel::dispatch (this=0x8a4c13c, [EMAIL PROTECTED]) at Kernel.cpp:35 #21 0x085ad1ff in lyx::frontend::ControlCommand::dispatchParams (this=0x8b87850) at ControlCommand.cpp:53 #22 0x0859bdf0 in lyx::frontend::Dialog::apply (this=0x8a4c138) ---Type to continue, or q to quit--- at Dialog.cpp:130 #23 0x0859bf2b in lyx::frontend::Dialog::OKButton (this=0x8a4c138) at Dialog.cpp:46 #24 0x0842decc in lyx::frontend::QDialogView::slotOK (this=0x8b697c8) at QDialogView.cpp:108 #25 0x0842df4a in lyx::frontend::QDialogView::qt_metacall (this=0x8b697c8, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfc41f7c) at QDialogView_moc.cpp:74 #26 0xb77010c0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #27 0xb77013d0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #28 0xb7ec5a91 in QAbstractButton::clicked () from /usr/lib/libQtGui.so.4 #29 0xb7cb6929 in QAbstractButtonPrivate::emitClicked () from /usr/lib/libQtGui.so.4 #30 0xb7cb6df9 in QAbstractButtonPrivate::click () from /usr/lib/libQtGui.so.4 Jürgen
Re: [Patch 1.5] bug 4857
Abdelrazak Younes wrote: > Pleas find the patch attached. FYI, I did the same fix some days ago in > trunk. Excellent thanks. This fixes the crash on view->PDF. However, I still got crashes on editing the label. Unfortunately, I was not able to reproduce this in the debugger. But I got what is below on exit. Since the patch is a clear improvement, I'd say commit anyway. Jürgen *** glibc detected *** src/lyx: double free or corruption (!prev): 0x08ac5680 *** === Backtrace: = /lib/libc.so.6[0xb71364b6] /lib/libc.so.6(cfree+0x89)[0xb7138179] /usr/lib/libstdc++.so.6(_ZdlPv+0x21)[0xb72eca61] /usr/lib/libQtGui.so.4(_ZN14QActionPrivateD0Ev+0xdf)[0xb797424f] /usr/lib/libQtCore.so.4(_ZN7QObjectD2Ev+0x144)[0xb7687914] /usr/lib/libQtGui.so.4(_ZN7QActionD2Ev+0x176)[0xb7972dd6] src/lyx[0x8592272] /usr/lib/libQtCore.so.4(_ZN14QObjectPrivate14deleteChildrenEv+0x4c [0xb7682f0c] /usr/lib/libQtGui.so.4(_ZN7QWidgetD2Ev+0x290)[0xb79b2a10] /usr/lib/libQtGui.so.4(_ZN11QMainWindowD2Ev+0x31)[0xb7c93ae1] src/lyx[0x8467d0e] /usr/lib/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x216)[0xb7684a16] /usr/lib/libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0x84)[0xb79bb604] /usr/lib/libQtGui.so.4(_ZN11QMainWindow5eventEP6QEvent+0x65)[0xb7c954d5] src/lyx[0x84641d4] /usr/lib/libQtGui.so. (_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x1cd [0xb7976c1d] /usr/lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x1a3 [0xb797ceb3] src/lyx[0x845c59c] /usr/lib/libQtCore.so. (_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6b)[0xb7675d5b] /usr/lib/libQtCore.so. (_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ae [0xb767781e] /usr/lib/libQtCore.so. (_ZN16QCoreApplication16sendPostedEventsEP7QObjecti+0x2d)[0xb7677afd] /usr/lib/libQtCore.so.4(_ZN16QCoreApplication4execEv+0xe2)[0xb7677bf2] /usr/lib/libQtGui.so.4(_ZN12QApplication4execEv+0x27)[0xb79762e7] src/lyx[0x845bd28] src/lyx[0x81993e8] src/lyx(_ZN9QListView10paintEventEP11QPaintEvent+0x542)[0x8067dee] /lib/libc.so.6(__libc_start_main+0xe0)[0xb70e5fe0] src/lyx(_ZN11QListWidget9dropEventEP10QDropEvent+0x315)[0x8067cb1] === Memory map: 08048000-08819000 r-xp 08:08 3280903/home/jspitzm/lyx/lyx-stable/src/lyx-qt4 08819000-0881a000 r--p 007d1000 08:08 3280903/home/jspitzm/lyx/lyx-stable/src/lyx-qt4 0881a000-0881e000 rw-p 007d2000 08:08 3280903/home/jspitzm/lyx/lyx-stable/src/lyx-qt4 0881e000-08c76000 rw-p 0881e000 00:00 0 [heap] b6a0-b6a21000 rw-p b6a0 00:00 0 b6a21000-b6b0 ---p b6a21000 00:00 0 b6b48000-b6b4e000 r--p 08:08 3280885/home/jspitzm/lyx/lyx-stable/lib/fonts/esint10.ttf b6b4e000-b6b54000 r--p 08:08 3280792/home/jspitzm/lyx/lyx-stable/lib/fonts/wasy10.ttf b6b54000-b6b5e000 r--p 08:08 3280463/home/jspitzm/lyx/lyx-stable/lib/fonts/msbm10.ttf b6b5e000-b6b65000 r--p 08:08 3280462/home/jspitzm/lyx/lyx-stable/lib/fonts/msam10.ttf b6b65000-b6b6b000 r--p 08:08 3280455/home/jspitzm/lyx/lyx-stable/lib/fonts/cmex10.ttf b6b6b000-b6b72000 r--p 08:08 3280464/home/jspitzm/lyx/lyx-stable/lib/fonts/cmr10.ttf b6b72000-b6b7a000 r--p 08:08 3280447/home/jspitzm/lyx/lyx-stable/lib/fonts/cmmi10.ttf b6b7a000-b6b82000 r--p 08:08 3280451/home/jspitzm/lyx/lyx-stable/lib/fonts/cmsy10.ttf b6b82000-b6b88000 r--p 08:08 3280458/home/jspitzm/lyx/lyx-stable/lib/fonts/eufm10.ttf b6b88000-b6bb5000 r--p 08:07 705986 /var/cache/libx11/compose/l4_024_313cb605_00280cc0 b6bb5000-b6bee000 r--p 08:07 2087712/usr/local/share/locale/de/LC_MESSAGES/lyx.mo b6bee000-b6c39000 r--p 08:07 1958003/usr/share/fonts/truetype/DejaVuSansMono.ttf b6c39000-b6c63000 r--p 08:07 1956207/usr/share/fonts/truetype/albw.ttf b6c63000-b6c97000 r--p 08:07 1956231/usr/share/fonts/truetype/thowr___.ttf b6c97000-b6ce8000 r-xp 08:07 1830487/usr/lib/libtiff.so.3.8.2 b6ce8000-b6ce9000 r--p 00051000 08:07 1830487/usr/lib/libtiff.so.3.8.2 b6ce9000-b6ceb000 rw-p 00052000 08:07 1830487/usr/lib/libtiff.so.3.8.2 b6ceb000-b6d3f000 r-xp 08:07 1833160/usr/lib/libQtXml.so.4.3.1 b6d3f000-b6d4 r--p 00053000 08:07 1833160/usr/lib/libQtXml.so.4.3.1 b6d4-b6d42000 rw-p 00054000 08:07 1833160/usr/lib/libQtXml.so.4.3.1 b6d42000-b6d87000 r-xp 08:07 1835816/Abgebrochen
Re: Problems Compiling LyX-1.5.5 on Mac: Help please!
Anders Ekberg wrote: > If it can be of any help have placed a 10.4 compilation of LyX 1.5.5 > on PPC at: > http://homepage.mac.com/anek/Temp/FileSharing24.html > Unfortunately I don't have any 10.4 installation on an Intel Mac... Very good. Bennett, shall I upload this to the server? Jürgen
Re: [patch] new Python csv2lyx importer
Uwe Stöhr wrote: > Attached is a new CSV2lyx importer written mainly by Hartmut Haase. > It uses Python's built in CSV reader that is available since Python 2.3. I > added a method to automatically detect the correct column separator. Excellent. After the pythons have reviewed it, you can shove it in branch as well. (Since I'm no pythonist, I won't comment on the code). Jürgen
Re: Proposal for small change in the release procedure
Joost Verburg wrote: >>> "Source code files are the raw files that programmers use. If you are >>> not used to compiling source code or don't know what source code is, >>> you almost certainly need the 'binary files'. Binary files have to be >>> prepared by volunteers and usually appear on the site a few days after >>> the release of the source code files. The binary files are normal >>> programs that can be run directly on a computer." >> >> Sounds good to me, I think this could go in as an introduction on the >> page > > I don't think it's a good idea to put such long texts on the download > page. How about a link to http://en.wikipedia.org/wiki/Source_code We could link it from a "What's this?" in the source code paragraph. Jürgen
bugzilla: fixedinbranch
Some bugzilla users have been irritated by the fact that we mark bugs fixed that are not fixed yet in the current release. Following a suggestion of Jean-Marc, I have thus defined a new keyword "fixedinbranch". This might limit confusion, and I also can check the fixed bugs against status.15x before the release. Please use this keyword now instead of closing the bug. We'll see if this practice is useful or not. Thanks, Jürgen
Re: LyX webpage problem with I18n
[EMAIL PROTECTED] wrote: > I've added some manual redirections for these pages: many thanks for doing all this. Jürgen
Re: [ANNOUNCE] LyX 1.5.5 is released
Enrico Forestieri wrote: > I have placed a cygwin binary here: > http://www.lyx.org/~forenr/lyx-1.5.5-cygwin.tar.gz Thanks, Enrico. It's on the server now. Jürgen
Re: [patch] fix subfig - caption package clash
Uwe Stöhr wrote:
> What subfig caption options do you need? I'm asking because a document
> should have consistent caption formats - for all float types. There are 2
> ways of getting this: - using caption
> - using the document class caption options, like for koma-script.
I need access to the caption formatting features that require caption
without actually loading caption itself. I don't see why we should limit
this possibility just for the sake of caption.sty users.
> > IMO, people who use the caption package have to pass "caption=false" to
> the > global options.
>
> This doesn't work because this option is also a valid option of the
> caption package leading to LaTeX errors. The caption manual explicitely
> states that the option must be given to subfig and NOT to caption.
Then we have to find another solution. Load the subfig package after the
user preamble and test if caption has been loaded.
Something like
[EMAIL PROTECTED]
\usepackage{subfig}%
}{%
\usepackage[caption=false]{caption}
}
Jürgen
Re: [patch] bug 4827: apa.layout uses starred instead of unstarred sections
José Matos wrote: > My only remark is about the usage of ObsoletedBy. > > It makes sense to use that for 1.5 and to do a new file format change for > 1.6 with the same purpose. > > If we don't do this now we will have to carry this ObsoletedBy forever > while in lyx2lyx it says where it should. OK. Good point. > If you want I can code the convertion code. Yes, please. Jürgen > FWIW there is no reversion code, the same as if the file was saved with > 1.6 and the change is lost.
Re: [patch] fix subfig - caption package clash
Uwe Stöhr wrote: > OK? I don't think we should limit the subfig capabilities for the sake of a package we don't support. I don't use caption and I _need_ subfig's caption options anyway. IMO, people who use the caption package have to pass "caption=false" to the global options. A better solution, of course, would be caption package support. Jürgen
Re: [Cvslog] r24655 - in /lyx-devel/trunk/src: FuncCode.h LyXAction.cp...
Abdelrazak Younes wrote: > Why don't we just get rid of those comments? Fastidious effort that is > not worth 10 pesetas... They are really helpful while debugging. Jürgen
[patch] bug 4827: apa.layout uses starred instead of unstarred sections
http://bugzilla.lyx.org/show_bug.cgi?id=4827 Any objections to doing the attached change in branch and trunk? (the rationale is given in detail in the above report) Jürgen Index: lib/layouts/apa.layout === --- lib/layouts/apa.layout (Revision 24659) +++ lib/layouts/apa.layout (Arbeitskopie) @@ -296,15 +296,57 @@ Input stdcounters.inc NoStyle Part -NoStyle Section -NoStyle Subsection -NoStyle Subsubsection +NoStyle Part* NoStyle Chapter -NoStyle Paragraph -NoStyle Subparagraph NoStyle Chapter* +Style Section* + Obsoletedby Section +End +Style Subsection* + Obsoletedby Subsection +End + +Style Subsubsection* + Obsoletedby Subsubsection +End + +Style Paragraph* + Obsoletedby Paragraph +End + +Style Subparagraph* + Obsoletedby Subparagraph +End + + +Style Section + LabelType No_Label + Align Center +End + + +Style Subsection + LabelType No_Label +End + + +Style Subsubsection + LabelType No_Label +End + + +Style Paragraph + LabelType No_Label +End + + +Style Subparagraph + LabelType No_Label +End + + Style Itemize MarginStatic LatexType Item_Environment
Re: 1.5.5
Jean-Pierre Chrétien wrote: > Her it is: > Assertion failed : __pos < size(), fichier > /usr/local/lib/gcc/sparc-sun-solaris2.8/3.4.6/\ > ../../../../include/c++/3.4.6/bits/basic_string.h, ligne 643 > > Program received signal SIGABRT, Aborted. > 0xfeed92f0 in __sigprocmask () from /usr/lib/libthread.so.1 > (gdb) bt > #0 0xfeed92f0 in __sigprocmask () from /usr/lib/libthread.so.1 > #1 0xfeece59c in _resetsig () from /usr/lib/libthread.so.1 > #2 0xfeecdd3c in _sigon () from /usr/lib/libthread.so.1 > #3 0xfeed0d98 in _thrp_kill () from /usr/lib/libthread.so.1 Hm. No idea on a first glance. Please open a bug report on bugzilla. Jürgen
Re: Qt4.4 is released since yesterday
Abdelrazak Younes wrote: > Maybe you should advance a bit the release of 1.5.5 as I'm affraid many > people will upgrade their Qt and complain about 1.5.4? I plan to release next week, as announced on this list. I cannot do it earlier, since there are still things to do (and the translators need their time). Jürgen
Re: bug 4819 (André?)
Andre Poenitz wrote: > I already made me a note but right now I did not find the time to have a > real look. OK. Jürgen
Re: 1.5.5
Jean-Pierre Chrétien wrote: > I'm afraid I was optimistic: LyX compiles fines, but I have again > an assertion when I leave LyX, and more critically (as it aborts LyX), > when I copy a string > > Assertion failed: __pos < size(), fichier > /usr/local/lib/gcc/sparc-sun-solaris2.8/3.4.6/../../../../include\ > /c++/3.4.6/bits/basic_string.h, > ligne 643 > Abort > > I got also this when fiddling with a table and a box: > > Assertion triggered in void lyx::Text::dispatch(lyx::Cursor&, \ > lyx::FuncRequest&) > by failing check "cur.text() == this" in file Text3.cpp:380 > [emergency save message, in French] > Abort > > I could't reproduce this one. can you provide a backtrace? > I compiled with qt-4.3.4 instead of qt-4.3.3 i used for 1.5.4, > could this be the reason ? I don't think so. Do you refer to the 1.5.4 release? Note that assertions are disabled in our release versions, so this might be the reason it didn't hit you. The good news is that it won't probably hit you on the 1.5.5 release either, for the given reason. Having said this, we should of course try to resolve the problem anyway. Jürgen
bug 4819 (André?)
André, could you have a look at this (qt?) problem? I wonder if this is something to be considered for 1.5.5: http://bugzilla.lyx.org/show_bug.cgi?id=4819 Thanks, Jürgen
Re: 1.5.5
Jean-Marc Lasgouttes wrote: > Done. Note that I left some of the most boring ones. Thanks anyway. Jürgen
Re: 1.5.5
Jean-Marc Lasgouttes wrote: > The following patch fixes this, along with several other warnings. > Juergen, do you want this in branch? Yes, please. Many thanks for looking at these rather boring issues. Jürgen
Re: [PATCH] Improved arrow and brace fills, including menu accelerators
Helge Hafting wrote: >> Now with: >> * New file format version >> * Conversion back to ERT when necessary >> * Context menus > * menu accelerators - although not very logical ones as the > obvious keys r-right, u-up, d-down all were in use already. > Forgot this the last time. I'll shove it in tomorrow if no one beats me to it. Jürgen
Re: the citation dialog
Edwin Leuven wrote: > wasn't referring to the preview window either ;) but rather the > available/selected boxes... These could be shrinked with the same hack, if everything else fails. I'd prefer a proper solution, though. Jürgen
[patch] Re: [Cvslog] r24548 - /lyx-devel/trunk/src/tex2lyx/text.cpp
Jürgen Spitzmüller wrote:
> If there are changes in
> tex2lyx that do not follow this rule (which ones?), they have to be
> reverted.
I checked the situation, and there are several changes that corrupt the file
format:
- hspace
- href
- newcommandx
- nocite
I hope, I haven't missed anything.
The applied patch restores a sane file format (247). I'll commit shortly.
The patch will be attached to bug 4379, so the changes can be reapplied
once tex2lyx is able to produce the appropriate file format.
Jürgen
Index: src/tex2lyx/tex2lyx.cpp
===
--- src/tex2lyx/tex2lyx.cpp (Revision 24556)
+++ src/tex2lyx/tex2lyx.cpp (Arbeitskopie)
@@ -108,7 +108,7 @@
void add_known_command(string const & command, string const & o1,
- unsigned optionalsNum)
+ bool o2)
{
// We have to handle the following cases:
// definition o1o2invocation result
@@ -117,14 +117,14 @@
// \newcommand{\foo}[1][]{bar #1} "[1]" true \foo bar
// \newcommand{\foo}[1][]{bar #1} "[1]" true \foo[x]bar x
// \newcommand{\foo}[1][x]{bar #1} "[1]" true \foo[x]bar x
- // and the same with \newlyxcommand
unsigned int nargs = 0;
vector arguments;
string const opt1 = rtrim(ltrim(o1, "["), "]");
if (isStrUnsignedInt(opt1)) {
// The command has arguments
nargs = convert(opt1);
- for (unsigned int i = 0; i < optionalsNum; ++i) {
+ if (nargs > 0 && o2) {
+ // The first argument is optional
arguments.push_back(optional);
--nargs;
}
Index: src/tex2lyx/tex2lyx.h
===
--- src/tex2lyx/tex2lyx.h (Revision 24556)
+++ src/tex2lyx/tex2lyx.h (Arbeitskopie)
@@ -79,11 +79,11 @@
/*!
* Adds the command \p command to the list of known commands.
* \param o1 first optional parameter to the latex command \newcommand
- * (with brackets), or the empty string if there were no optional argument.
- * \param optionalsNum is the number of optional parameters
+ * (with brackets), or the empty string if there were no optional arguments.
+ * \param o2 wether \newcommand had a second optional parameter
*/
void add_known_command(std::string const & command, std::string const & o1,
- unsigned optionalsNum);
+ bool o2);
// Access to environment stack
extern std::vector active_environments;
Index: src/tex2lyx/text.cpp
===
--- src/tex2lyx/text.cpp (Revision 24556)
+++ src/tex2lyx/text.cpp (Arbeitskopie)
@@ -89,7 +89,7 @@
}
-char const * const known_latex_commands[] = { "ref", "cite", "nocite", "label",
+char const * const known_latex_commands[] = { "ref", "cite", "label",
"index", "printindex", "pageref", "url", "vref", "vpageref", "prettyref",
"eqref", 0 };
@@ -1458,12 +1458,8 @@
os << "\\bibitem ";
os << p.getOpt();
os << '{' << p.verbatim_item() << '}' << "\n";
- }
-
- else if(t.cs() == "global") {
- // skip global which can appear in front of e.g. "def"
}
-
+
else if (t.cs() == "def") {
context.check_layout(os);
eat_whitespace(p, os, context, false);
@@ -2300,32 +2296,6 @@
skip_braces(p); // eat {}
}
- else if (t.cs() == "href") {
- context.check_layout(os);
- begin_inset(os, "CommandInset ");
- os << t.cs() << "\n";
- os << "LatexCommand " << t.cs() << "\n";
- bool erase = false;
- size_t pos;
- // the first argument is "type:target", "type:" is optional
- // the second argument the name
- string href_target = subst(p.verbatim_item(), "\n", " ");
- string href_name = subst(p.verbatim_item(), "\n", " ");
- string href_type;
- // serach for the ":" to divide type from target
- if ((pos = href_target.find(":", 0)) != string::npos){
-href_type = href_target;
-href_type.erase(pos + 1, href_type.length());
-href_target.erase(0, pos + 1);
- erase = true;
- }
- os << "name " << '"' << href_name << '"' << "\n";
- os << "target " << '"' << href_target << '"' << "\n";
- if(erase)
-os << "type " << '"' << href_type << '"' << "\n";
- end_inset(os);
- }
-
else if (t.cs() == "input" || t.cs() == "include"
|| t.cs() == "verbatiminput") {
string name = '\\' + t.cs();
@@ -2452,8 +2422,7 @@
else if (t.cs() == "newcommand" ||
t.cs() == "providecommand" ||
- t.cs() == "renewcommand" ||
- t.cs() == "newlyxcommand") {
+ t.cs() == "renewcommand") {
// these could be handled by parse_command(), but
// we need to call add_known_command() here.
string name = t.asInput();
@@ -2464,18 +2433,11 @@
}
string const command = p.verbatim_item();
string const opt1 = p.getOpt();
- string optionals;
- unsigned optionalsNum = 0;
- while (true) {
-string const opt = p.getFullOpt();
-if (opt.empty())
- break;
-optionalsNum++;
-optionals += opt;
- }
- add_known_command(command, opt1, optionalsNum);
- string const ert
Re: [Cvslog] r24548 - /lyx-devel/trunk/src/tex2lyx/text.cpp
Uwe Stöhr wrote: > When the result is a LyX file not in the latest file format, then you are > right. But as said, this is the tex2lyx that comes with LyX 1.6. You can > see with the test TeX files from SVN that tex2lyx works fine on them - so > I don't see a problem. The problem is that tex2lyx is not only an included helper application of LyX 1.6. It's also a standalone converter. So if someone uses that to convert a tex file, he gets a format 247 file which actually isn't 247. If he tries to open that with 1.5 (which supports format 257), it will fail. If we do not follow this, our whole file format concept is useless. Jürgen
Re: the citation dialog
Edwin Leuven wrote: > wasn't referring to the new line, but rather that the listviews seem too > big... I forced the preview window to be smaller, which was a bit difficult (I needed some hardcoding). Feel free to jump in. Jürgen
Re: [PATCH] Add arrowfills and brace fills to the hspace dialog
Uwe Stöhr wrote: > Jürgen, could you review the patch as you have recently worked on the > InsetSpace stuff? patch looks OK (apart from missing lyx2lyx and context menu stuff; and the new combo entries look a bit weird -- I wonder if we could't use images instead of this "ASCII art"). Jürgen
Re: [PATCH] caption dialog with initial support for contcaption
Jean-Marc Lasgouttes wrote: > Now Juergen tricked you into "implement as many new caption features > as possible". I object, Sir. Jürgen
Re: r24456 [1/2] - in /lyx-devel/branches/BRANCH_1_5_X/develo...
Joost Verburg wrote: > I've added the relevant information for end-users to status.15x. thanks. Jürgen
Re: r24456 [1/2] - in /lyx-devel/branches/BRANCH_1_5_X/develo...
[EMAIL PROTECTED] wrote: > installer updates from trunk Joost, could you sum up the changes in status.15x, please? Jürgen
Re: Is www.lyx.org ready to go live?
Joost Verburg wrote: >>> Could we make the text raggedright instead of justified? It has some >>> ugly inter-word spacing (at least consider to make the headings >>> raggedright. Look at the "Special Release: LyX 1.5.3 Japanese edition >>> for Windows released." heading in news). >> >> Is this ok now? (I don't know if the problem is still here) > > This is already fixed. Yes. the headings look good now. I'd still prefer a raggedright text with consistent interword spacing over the justified right margin, though. Jürgen
Re: crash with custom export
Pavel Sanda wrote: > no Hm. Maybe something in my tree. Jürgen
crash with custom export
trunk crashes for me as soon as I launch Export->Custom... Can anyone reproduce? Jürgen
Re: Should we have a search box in the side bar?
[EMAIL PROTECTED] wrote: > mm... Just to check that we're talking about the same thing, please have > a look on this page where I activated the search field in the side bar. Yes, ugly ;-) An aligned input widget and button (as on kde.org) would improve the look already IMHO. Jürgen
Re: New www.lyx.org is now live
Abdelrazak Younes wrote: > too long sentence Split it. My point is that TeX and LaTeX are two different beasts. Jürgen
Re: New www.lyx.org is now live
[EMAIL PROTECTED] wrote: > If we change this to 'TeX/LaTeX typesetting system', > should we change the link to 'LaTeX' in wikipedia instead? LyX combines the power and flexibility of the LaTeX macro package built on the TeX typesetting system with the ease of use of a graphical interface. Jürgen
Re: About the needed Caption dialog
Abdelrazak Younes wrote: > I begun to create a dialog (see attached). Question to LateX experts: > are those options mutually exclusive? Can you think of other useful > options? Nice idea in general. However, I would do the positioning options in a combo: "above", "below", "default" (which might be above or below, depending on class options), "sideways". Later, we could add some options from the caption package. Ideally, this dialog should parse information from the layout file. KOMA for instance does not only provide captionabove and captionbelow, but also some nice extra settings. > Ideally those options will also be available in a caption context menu. Yes, at least the most common ones. Jürgen
Re: About the needed Caption dialog
Uwe Stöhr wrote:
> \caption{test\protect\includegraphics{image}}
We should do this (protect images). Then people will see the problem in the
output, and others who intentionally put a picture in the caption, are
allowed to do so.
Jürgen
"news" on web page
All the news items on maintenance releases lost the links to the announcements. For instance: New Maintenance Release: LyX 1.5.4 released. Feb 24, 2008 [...] Please find enclosed an , some sources in tar.gz format (also .tar.bz2) and ^^^ here, the link to http://www.lyx.org/announce/1_5_4.txt is missing. Jürgen
Re: New password required for the web site
[EMAIL PROTECTED] wrote: > Someone set a new password for editing the web site. It's documented in > > /home/lyx/www/pmwiki/passwords.txt > > If you can't read that file, e.g. because you don't have an account on > aussie, please ask on the developers' list and a developer should send the > password to you. I can't read (open) it, even though I do have an account. Jürgen
Re: Howto ERT that uses external files?
José Matos wrote: > Would this harm in general? Don't know. We only insert it if specific insets (graphics, external etc.) are used. Jürgen
Re: [patch] fix bug 2457
Uwe Stöhr wrote: > The attached bug adds support for \textcolor to tex2lyx. This fixes > http://bugzilla.lyx.org/show_bug.cgi?id=2457 Looks good AFAICS (but I did not test it). Jürgen
Re: [Cvslog] r24272 - /lyx-devel/trunk/lib/lyx2lyx/lyx_1_6.py
Richard Heck wrote: > Mostly, this will work. If there's a standard but not default layout, we > could end up with weird results. All the ERT could then break, if (say) > Standard output some LaTeX of its own. But there may be no actual cases > of this, and if there are, we can deal with them. I don't think we have such cases in practice, and such cases are broken in 1.5 anyway (due to the bug you fixed). > So if it seems wise, I'll go ahead and produce the lyx2lyx needed to do > the two conversions mentioned. It'll probably be next week before I can, > as I'm swamped with actual work. Thanks. Take your time. Jürgen
Re: Is www.lyx.org ready to go live?
Rex C. Eastbourne wrote: > By the way, it seems like the site looks better every time I visit it. > Nice work to whoever re-did the colors and the banner at the top of the > page! I second that. It looks very pleasing now. Just two notes: Could we make the text raggedright instead of justified? It has some ugly inter-word spacing (at least consider to make the headings raggedright. Look at the "Special Release: LyX 1.5.3 Japanese edition for Windows released." heading in news). Since I do not have a password yet, could someone add a reference to the following site to Roadmap/News, please? http://wiki.lyx.org/LyX/NewInBranch Jürgen
Re: New www.lyx.org is now live
[EMAIL PROTECTED] wrote: > I think that behaviour is ok. Anyway, the new site is now live and it > should probably be announced... If you send me a text, I can post it. Jürgen
