> I have attached InlineBib.py (which is a modified version of the
earlier script).
Some remarks about this script:
def CreateBbl(n): #Creates .aux and .bbl from .tex
#- argument = "latex " + n[:-4]#n[:-4] is the name of the file
without extension
#- os.system(argument)
argumen
>> And in the less usual case in which only languages are used other than
>> the document language, the document language is not in the list (which
>> I would expect of course).
>Consider this a bug..
I already did..
>OK?
Yes.
>Jürgen
Vincent
Manoj Rajagopalan schreef:
1. Is this change acceptable?
I think so.
2. This feature requires the IncludeBib.py script submitted by another
user/developer in the issue-log on trac: http://www.lyx.org/trac/ticket/4624
Can the IncludeBib.py script be bundled with the lyx distribution now? I
John McCabe-Dansted schreef:
On Thu, Feb 25, 2010 at 12:24 AM, LyX Ticket Tracker wrote:
#6553: Assert on Opening the Edit menu to the left of a Math Inset
PS. Why don't you report this on the devel-list. Especially if it concerns
on-going business.
The literal answer to
John McCabe-Dansted schreef:
I found the errors reported by cppcheck much easier to fix than bug
reports (e.g. generated by my keytest). For example:
[./development/lyxserver/server_monitor.c:173]: (error) Memory
leak: pipename
This had the obvious solution of adding free(pipename) to line 17
When modifying an inset in a document doesn't toggle the buffer dirty
anymore.
Vincent
>> I meant, why do you want to retrieve the revision number of the
>> current file, which you use in the call to svn cat. I guess that if
>> you call svn cat without a revision number, it will get the last
version. Or not ?
>
>but we want much more than the last version. inside we always call sv
>I don´t find the possibility in 1.6.5 to generate and use branches, where
>did that function move? I think, it was under "Edit" before...
>
Document -> Settings -> Branches
Vincent
>> Why do you need the revision number for revision 0 ?
>
>the idea was that user would be able to address revisions not only by
>absolute revision number but also in relative manner, ie to let him
address
>revisions like -5 for five revisions back. naturally 0 happens to be
the last
>commit.
I
Enrico Forestieri schreef:
On Tue, Feb 23, 2010 at 12:59:41AM +0100, Vincent van Ravesteijn wrote:
Enrico Forestieri schreef:
On Mon, Feb 22, 2010 at 11:17:02PM +0100, Vincent van Ravesteijn wrote:
Compiling with: "/Zc:wchar_t-" solves it for me.
In MSVC this
Enrico Forestieri schreef:
On Mon, Feb 22, 2010 at 11:17:02PM +0100, Vincent van Ravesteijn wrote:
Compiling with: "/Zc:wchar_t-" solves it for me.
In MSVC this is called "Treat wchar_t as Built-in Type : No". This is by
default set to Yes.
D'oh! And
sa...@lyx.org schreef:
Author: sanda
Date: Mon Feb 15 08:10:59 2010
New Revision: 33474
URL: http://www.lyx.org/trac/changeset/33474
-bool SVN::prepareFileRevision(int rev, string & f)
+bool SVN::prepareFileRevision(string const & revis, string & f)
{
+ if (!isStrInt(revis))
+
sa...@lyx.org schreef:
Author: sanda
Date: Mon Feb 22 03:00:40 2010
New Revision: 33528
URL: http://www.lyx.org/trac/changeset/33528
Modified: lyx-devel/trunk/lib/ui/stdtoolbars.inc
==
--- lyx-devel/trunk/lib/ui/stdtool
Author: sanda
Date: Mon Feb 22 03:01:04 2010
New Revision: 33533
URL: http://www.lyx.org/trac/changeset/33533
+ Compare * compare = new Compare(loadIfNeeded(FileName(f1)),
loadIfNeeded(FileName(f2)), dest, options);
+ compare->start(QThread::LowPriority);
+
No, Qt uses the wchar_t of the platform for the to/fromWChar functions
to communicate with wchar_t based functions of the host system. On
Windows that's a 16 bit type, on *nix traditionally 32 bit.
QString is internally UTF-16 on all platforms.
So what do you propose? LyX is currently uncompil
Compiling with: "/Zc:wchar_t-" solves it for me.
In MSVC this is called "Treat wchar_t as Built-in Type : No". This is by
default set to Yes.
Can this be changed in the Scons and CMake scripts ?
Vincent
> >class Q_CORE_EXPORT QString
> >{
> >...
> >static QString fromWCharArray(const wchar_t *, int size = -1);
> >...
> >}
> >
>The function is new in 4.2, so one possibility is that you compile
against
>4.2 headers but link against 4.1 libraries.
No, that's not the problem.
>Export mig
>> >class Q_CORE_EXPORT QString
>> >{
>> >...
>> >static QString fromWCharArray(const wchar_t *, int size = -1);
>> >...
>> >}
>> >
>> >so, I really don't understand why you get the error. Are you sure
you
>> are
>> >linking the QtCore library?
>> >
>>
>> I see the same, and I don't k
>> I see the same, and I don't know what the problem is either. The >
QString header can be found, Qstring can be used, just not this static
> function. Maybe it is not exported or something..
>Glad to hear that I'm not the only one having this problem. I'm using
Qt 4.5.3. Vincent, Enrico, what Q
>> No.
>> The above error message states that
>> QString::fromWCharArray(wchar_t const *,int) is the problem.
>> I don't understand the error message but it seems that fromWCharArray
>> needs to be linked via a header file.
>
>That header file is , which is already included. There, you
can
>find
Roger Mc Murtrie schreef:
On 19/02/2010, at 6:28 PM, lyx-devel-digest-h...@lists.lyx.org wrote:
From: BH
Date: 18 February 2010 10:58:53 AM AEDT
To: Roger Mc Murtrie
Cc: lyx-devel@lists.lyx.org, Pavel Sanda
Subject: Re: Mac SVN fails to compile
On Wed, Feb 17, 2010 at 6:14 PM, Roger Mc
Yes of course, but let formulate the problem I described in more
general terms :
- If one types a document containing "Test" with Open Office, and
export it in pdf, the pdf output can be viewed with all viewers,
including AcroRead.
- If one does the same thing with LyX, the pdf output with t
>So, please hard test this dialog and try to fix
>remaining bugs (which is now way easier than before).
I find it very strange that the Apply button changes to New if you check
auto-apply. These two functions are not related in any sense. Besides,
why would I only be able to insert a new table i
>i would like to kill more ld and unused members, but its hard to
test things because of
>http://www.lyx.org/trac/ticket/6496 .
>
>Abdel would it be possible to look on the cache metrics stuff; maybe
its just oneliner for you?
>
It's probably my 'fault'. The problem is that loadLyXFile calls
s
>>>the problem however is how to deal with external material eg.
>>>graphics files.
>>>one option is to ignore it.
>>
>> Ignore what ?
>
>differences in figures .lyx file is pointing to.
>
Yes, let's ignore it. Even if you find that the image is changed, there
is no way of showing this in LyX (e
>>
>>> It confuses many people.
>>> See http://www.lyx.org/trac/ticket/1699
>>>
>>> (of course we could also add an "immediate apply"
>>> checkbox.
>>>
>>That's what I did.
>>
>
>Did you?
>
Yes, but it didn't ever reach trunk.
Vincent
>It confuses many people.
>See http://www.lyx.org/trac/ticket/1699
>
>(of course we could also add an "immediate apply"
>checkbox.
That's what I did.
Vincent
>> GuiTabular despaghettization: pass out tabular_ instead of using it
>> directly.
>
>This dialog really needs love. It would be great if someone
>implemented a proper params handling (with OK/APPLY behaviour).
Hmm.. I tried that once (with considerable amount of effort), but I guess I got
stuc
>the problem however is how to deal with external material eg. graphics
files.
>one option is to ignore it.
Ignore what ?
>another option is to ignore it and claim that we wait for encapsulated
>format which can elegantly solve it.
What is the encapsulated format ?
>another option is trying to
Joost Verburg schreef:
Hi,
I was just typing some math and 1.6.5 crashed with the following
assertion:
lyx-1.6.5\src\support\lassert.cpp(21): ASSERTION pos < size() VIOLATED
IN lyx-1.6.5\src\mathed\MathData.cpp:56
Does anyone know whether this may be related to a known bug (I
couldn't fin
Vincent van Ravesteijn schreef:
Lara Pagano schreef:
Hi,
I was working on my Thesis document within Lyx and it crashed all of a
sudden. I got an error saying: Lyx: SIGSEGV signal caught. I am not
sure
what to do because I can go into the document for maybe 1 or 2 minutes
before it crashes
Lara Pagano schreef:
Hi,
I was working on my Thesis document within Lyx and it crashed all of a
sudden. I got an error saying: Lyx: SIGSEGV signal caught. I am not sure
what to do because I can go into the document for maybe 1 or 2 minutes
before it crashes again. I can not recall changing an
John McCabe-Dansted schreef:
I have a few questions.
1) Should I do a bisection on essentially every regression I find,
and/or are there specific bugs that you would like me to perform a
bisection on?
I don't know what to answer here. It's often easy to find out what
change caused the bug, bu
Jürgen Spitzmüller schreef:
vfr wrote:
Author: vfr
Date: Sat Feb 6 02:43:50 2010
New Revision: 7
URL: http://www.lyx.org/trac/changeset/7
Log:
branch: Fix bug #6489: Assertion triggered when deleting contents of math
ERT. (probably a stdlib assertion).
No status entry?
Jürg
>>> + const char *font_name;
>>> + switch (type_) {
>>> + return from_ascii(font_name);
>>> }
>>>
>>
>> Please use "docstring font_name;" and "font_name = from_ascii(..);"
>>
>What do we gain ? Isn't it only more overhead ? We create another
>docstring instance which then needs to be
>Author: tommaso
>Date: Fri Feb 5 10:00:40 2010
>New Revision: 33329
>URL: http://www.lyx.org/trac/changeset/33329
>
> docstring InsetMathHull::standardFont() const {
>- return from_ascii(type_ == hullNone ? "lyxnochange" :
"mathnormal");
>+ const char *font_name;
>+ switch (type_)
Kornel Benko schreef:
Hi,
this string is (in branch and trunk) used ( in Preferences->Language
Settings->Language->User interface language: ),
but is not part of po-files, thus will not be translated in the GUI.
Kornel
Then you have to do a remerge.
Vincent
Jürgen Spitzmüller schreef:
Vincent van Ravesteijn - TNW wrote:
If you now put in the constraint that Buffer::getChildren cannot return
the buffer itself as one of its children, then you fixed the problem you
were trying to fix. If that's what you was planning to do.
Yes, this
>But then there is this bug too:
>http://www.lyx.org/trac/ticket/6505
>
That's already known for a long time, but in the past we decided it was not
worth fixing it. See bug #1474.
Vincent
>> I mean you shouldn't use the isChild function from
>> Encoding::initMath.
>
> To clarify: this is not my code. Anyway, you mean this?
Yes, of course I know it's not your code. And yes, this is what I mean.
>> To fix the bugs, we should check for recursive includes when the
>> InsetInclude
>> First, Encodings::initMath should get the children like this. Please,
>> use
>> buffer->getChildren() for that.
>>
>> Now, we can avoid that getChildren() returns a list including itself.
>
>In other words, patch b?
>
No, I refrain from words that other people might understand.
I mean you
>http://www.lyx.org/trac/ticket/6503
>
>This crash is caused by an infinite loop in Encodings::initMath,
>which recursively calls itself if a document includes itself
>(we already issue a warning about that, but in the given case,
>LyX crashes before the warning can be issued).
>
First, Encodings:
tomm...@lyx.org schreef:
Author: tommaso
Date: Tue Feb 2 21:36:12 2010
New Revision: 33318
URL: http://www.lyx.org/trac/changeset/33318
Hi Tommaso,
Yet again, I don't really understand your fix.
// Compute the match length
int len = 1;
+ if (cur.pos() + len > cur.lastpos
> Yes, dvi and pdf work fine for me. But I want OpenDocument because
> I'm sending the file to another person and want him to be able to edit
the file.
I know, but don't send your answer SEVEN times ?!?
Vincent
>[examples/splash.lyx] is the document which automatically opens when
user
>runs LyX first time after installation. The problem is that the "View -
>OpenDocument" command produces empty output for me. Please help!
Don't use OpenDocument. Use dvi or pdf to preview.
Vincent
>I heard Vincent has an upcoming InsetPreview feature which I don't
exactly
>know how would relate to this, perhaps both things may be worth to
exist.
>
Well, everything inside this Inset will get previewed. So if you put
your equation into an ert into this inset it will generate a preview of
the
F&*#&#*#*##*
the relevant line for this is in Inset.h:
///
bool insetAllowed(InsetCode) const { return !getLayout().isPassThru(); }
So, no inset is allowed in anything that has a passthru layout.
In these case cur.nextInset() will be zero.
The code would then be:
if (cur.nextInset())
>hmmm, looking at the preceding line:
>
>cur.insert(new InsetMathHull(cur.buffer(), hullRegexp));
>if (cur.nextInset()) {
>cur.nextInset()->edit(cur, true);
>cur.niceInsert(sel);
>}
>
>What happens now is that the cur.insert() call is made a
Juergen,
A few issues concerning the Child documents pane:
- I can't seem to figure out how to set the "Include to Output" field to
yes. If I doubleclick the "No", the only thing that happens is that the
radiobutton selection goes back to "Include all children" (while I
explicitly chose Includ
>> More important, I'm still not sure why we forbid the REGEXP_MODE in
>> ERTs. Why does LyX crash ?
>It's happening here: Text::regexpDispatch()
>
> cur.nextInset()->edit(cur, true);
>
>simply replacing with
>
>if (cur.nextInset()) {
>cur.nextInset()->edit(cur, true);
>cur.
>Finally, for the implementation right now, I propose to mimick what is
>done for the various LFUN_xxx_INSERT and use the "code" helper
variable.
This is not really possible as the RegExps are no real insets right now,
so there is no REGEXP_CODE and BufferView::regexpDispatch(..) now
creates a I
>Which other insets would be pass_thru ?
URLs and Program Listings and possibly Custom Insets defined by the user
(see lib/stdinsets.inc).
> > Compare with :
> >
> > text3@2659:
> >
> > if (cur.empty()
> > || !cur.inset().insetAllowed(code)
> > || cur.paragraph().layout().pass_
>>> Last, why is the status of LFUN_REGEXP_MODE handled in
BufferView.cpp
>>> while the dispatch is in Text3.cpp. Moreover, I would expect it to
be
>>> next to LFUN_MATH_MODE as they seem to be related.
>> Probably should be moved to Text3.cpp.
>For example, see attachment (behaviour is apparen
>OK, I guess my question is this: If LyX were using
>LuaTex, what would my LyX document look like in Vim?
I'd rather make sure you won't need vim anymore :).
Vincent
Tommaso Cucinotta schreef:
Vincent van Ravesteijn wrote:
!dynamic_cast(&cur.inset()));
I don't understand what this means. Is this the same as:
cur.inset().lyxCode() != ERT_CODE);
? If so, I'd favor this simple notation.
Yes, it is the same (language-level type recog
tomm...@lyx.org schreef:
Author: tommaso
Date: Sun Jan 31 22:38:18 2010
New Revision: 33302
URL: http://www.lyx.org/trac/changeset/33302
Log:
Inhibits insertion of Regexp insets within InsetERT context (and fixes #6495).
Modified:
lyx-devel/trunk/src/BufferView.cpp
Modified: lyx-devel/trunk
Bo Peng schreef:
Yes, this is a very annoying bug. The Modify button of the Shortcut dialog
can actually not be used to modify existing shortcuts.
Currently you have no other choice than to delete an existing shortcut and
create a new one -> Putting it on the LyX 2.0 radar.
Is this al
Pavel Sanda schreef:
Andre Poenitz wrote:
I think it's time to use signal/slots, this time in the right direction.
The buffer emits a message, possibly with an indication that it is
temporarily and the view (or the server...) connects to it.
hmm, its very hard to debug things in signal
Bo Peng schreef:
I just disabled the possibility to put the cursor into the InsetInfo.
Will this also disable selecting and copying text out of InsetInfo?
Yes.
As far as I remember, InsetInfo at first did not get cursor/focus, which
was corrected as a bug.
Then, it was not correc
Tommaso Cucinotta schreef:
CXX GuiView.o
GuiView.cpp: In member function ‘virtual void
lyx::frontend::GuiView::dispatch(const lyx::FuncRequest&,
lyx::DispatchResult&)’:
GuiView.cpp:2997: error: no matching function for call to
‘lyx::frontend::GuiView::lfunUiToggle(const char [11])’
GuiView.h
Author: lasgouttes
Date: Fri Jan 29 11:42:39 2010
New Revision: 33258
URL: http://www.lyx.org/trac/changeset/33258
Log:
add a dispatchresult parameter to lyxview::dispatch
How do we proceed now ?
As an example, FUN_FILE_INSERT calls:
GuiView::insertLyXFile, which emits the messages
Peter Kümmel schreef:
Am Freitag, den 29.01.2010, 18:30 + schrieb José Matos:
On Friday 15 January 2010 19:42:30 Pavel Sanda wrote:
José Matos wrote:
Any other opinions suggestions?
- please do some definitive decision about version number now.
i have ask
>> Log:
>> Make LFUN_HELP_OPEN open the document in read-only mode.
>>
>> This fixes problems where Mac users can modify the documentation by
>> mistake. Note that it is still possible to open those document by
>> explicit path or to toggle off the read-only status (but this is only
>> useful t
>> * GuiView.cpp:
>> - use tabbed dock area for multiple docks (such as "source" and
"messages")
>>by default (requires Qt 4.3).
>
>it would be actually nice to have setting or some context menu for
switching this.
>currently there is (fortunately) still possible to dock it alongside
t
>* why isn't this in Buffer or BufferView? Just because it uses alerts?
> Did I already day that I do not like this dichotomy? ;)
>
No, because most of the time it had to reload the buffer. Reloading the
buffer meant destroying the current one and loading the file again.
That's why I moved the
>> updateLabels() in InsetMathNest's LFUN_CUT dispatch seems to fix the
>> crash. However, the pasted ref is not updated...
>
>OK, now InsetMathGrid joins the party. This, additional to the above, fixes
>the issue for me.
>
On a sidenote, I'm getting increasingly worried about increasing numb
>I suspect (but I am not sure) the problem is that InsetMathRefs are not
>recorded in the paragraph's InsetList which is iterated for the label update.
>If so, what do I have to do to change that?
I'm not really sure of what follows, but maybe it can give you a hint.
I think that the InsetMathR
>> Cmake shouldn't want to compile moc_* files. It shouldn't even know
>> that they exist. These moc_* files are #included in the normal *.cpp
>> files and they are now compiled twice and thus giving you the
>> "previously defined here" errors.
>>
>
>Why not? They are not part of svn, so they h
>I'm trying to get cmake to work on Mac. Here's what I've
>done from within lyx-devel/build:
>
>export PATH=/path/to/qt/bin:$PATH
>export QT4DIR=/path/to/qt
As said before, setting QT4DIR is not necessary for me (but not at a Mac
of course)
>cmake ../development/cmake -G "Unix Makefiles" -Dmerg
>First I suggest to install libqt4-dev instead of compiling
>Qt yourself. If you absolutely want Qt4.6, I suggest you
>upgrade" to KDE-4.4.
Actually.. I was using Qt4.7 :S..
>Otherwise, make sure you pass '-glib' and that the
>development package for it is installed (libglib-dev?)
Ok, I'll che
By the way, does anyone have an idea why my self-compiled Qt-apps (even
qtconfig) look very shitty on my Ubuntu 9.10. The font is very ugly and
the general ui does not resemble anything like the other apps. If I run
qtconfig, I can't for example choose the same font as when running the
qtconfig ins
> You don't generally need to do that if you're building out-of-tree.
Ah, that's what I did wrong.
Thanks.
>Abdel.
Vincent
>> Cmake works fine when it finds qmake. Did you make sure qmake was in
>> your path?
>>
>The problem is that I can't even configure properly. I get
>the "Qt libraries not found" error at the end of that. Do I
>not need to configure if I'm using cmake?
>
No, you don't.
If you make sure qmake
>Can somebody explain to me the rationale of the
>following methods? I am not even sure how that
>can work...
Yes, it stroke me once before, but I didn't have enough courage to take
on the battle.
>
>void Buffer::setReadonly(bool const flag) {
> [..]
> setReadOnly(flag);
> [..]
>}
>
>
>Tommaso,
>
>do I miss something or does the Advanced F&R dialog indeed
>not have a proper "Replace" button? All I see are the "Next"
>and "Previous" buttons, but those replace the next and
>previous matches, respectively, not the current one.
>
I'd also be happy if the replace part could be hi
> My small files still give wrong output, though (duplicated first line)
This was a last-minute clean-up, but I forgot to update the rp. This happens
before the algorithm really starts.
Fixed at r33184.
Now we have immediately a check whether the files are the same. If so, the
algorithm shoul
> "Vincent van Ravesteijn - TNW" writes:
>
>> But then
>>
>> os[kk] = k;
>>
>> doesn't work anymore, because os[kk] returns a copy and the copy is
>> then assigned the value that k has. That means that we are back at
>>
>> If you click Compare, a thread is started and the Close button
changes
>> to Cancel: to stop the thread.
>>
>> After pressing it, it will stop the thread and the button text
changes
>> back to Close: to close the window.
>
>Why not close the window right away?
>
I don't know.. Maybe becaus
>I do not like much this business of loading buffers without
>showing them, actually... And with this browse button, I feel
>the feature feels more like an additional utility than a part
>of the program.
That's why it is in the Tools menu ;).
>BTW, when I click on Cancel, the button just turns to
>> Of course, you can return a copy instead of a reference.
>
>This might be safer...
>
But then
os[kk] = k;
doesn't work anymore, because os[kk] returns a copy and the copy is then
assigned the value that k has. That means that we are back at having
setters and getters instead of the [] operat
>Other remarks in no particular order:
>
>- with my qt 4.2.x the frame "Options" appears empty
>
I don't really have a clue how to solve it. Isn't it the problem of the
"Expanding" sizepolicy that is not understood by qt4.2 ?
>- Could we have nice names displayed instead of full names?
I don'
>> Author: vfr
>> Date: Thu Jan 21 19:58:55 2010
>> New Revision: 33137
>> URL: http://www.lyx.org/trac/changeset/33137
>>
>> Log:
>> Fix the Compare feature. The compl_vector class
>>shouldn't be accessed twice in one statement as it
>>might happen that the vectors are reallocated, such
>>that t
Everytime compl_vector::operator[] needs an index that does not exist,
it does a push_back which can/will reallocate the whole vector when a
bigger memory block is necessary. I had the same mysterious bugs with
tex2lyx a few months ago.
This means that if you hold a DocIterator& of an element o
>It still crashes, but in a less evident way. I therefore
>ran it under valgrind, which complains a lot (but does
>not crash). It looks like the code refers to memory that
>has been freed already.
I'm not doing difficult memory things.. So i'm a bit puzzled.
Is this also caused by the stdlib-debu
The problem is that this routine fails for multirows:
Assume this table
a b c
e f g
i j k
by setting cell "e" and "i" a a multirow, appendParagraphs leads to
this cell content
No this is not the fault of appendParagraphs. You shouldn't be looking
into that function at all.
"efgi"
but I
Uwe Stöhr schreef:
Am 17.01.2010 01:17, schrieb Vincent van Ravesteijn:
Why not CELL_NORMAL, CELL_BEGIN_OF_MULTI, CELL_END_OF_MULTI.. these are
exclusive anyway.
It is unnecessary to determine also the end. Begin and part cells is
enough information, no?.
sorry I meant PART in stead of
But this doesn't work here: I have this enum
enum {
///
CELL_NORMAL = 0,
///
CELL_BEGIN_OF_MULTICOLUMN,
///
CELL_PART_OF_MULTICOLUMN,
///
CELL_BEGIN_OF_MULTIROW,
///
CELL_PART_OF_MULTIROW
};
Why not CELL_NORMA
we tend to write that lfun is selection-wise when it works on selected
text. i can add it myself once its committed.
I haven't seen that before.
when editing i see on console:
LayoutBox.cpp(551): Trying to select non existent layout type Plain Layout
context menu missing (very usable for
Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
Here is the patch.
thanks. the patch doesnt apply here because of wrong base dirs.
No problem here (on linux).
+#include "insets/InsetPreview.h"
this file is missing in my tree
I forgot to do "svn ad
Pavel Sanda schreef:
Vincent van Ravesteijn wrote:
+ * \var lyx::FuncCode lyx::LFUN_PREVIEW_INSERT
+ * \li Action: Inserts a new preview inset.
+(selection-wise) ?
pavel
?
Vincent
be found in the file COPYING.
+ *
+ * \author Vincent van Ravesteijn
+ *
+ * Full author contact details are available in file CREDITS.
+ */
+
+#ifndef INSETPREVIEW_H
+#define INSETPREVIEW_H
+
+#include "InsetText.h"
+
+#include "Dimension.h"
+#include "RenderPre
Pavel Sanda schreef:
Pavel Sanda wrote:
- Are there other missing features that you are working on and that you
want to have in LyX 1.7 before a beta release?
revision info under VCS is still in plan (fileformat change). but not
necessarily before beta, shouldn't be big change...
Jean-Marc Lasgouttes schreef:
"Vincent van Ravesteijn - TNW" writes:
I tried to compare the Intro from trunk and branch
and got the following. Vincent?
Can you reproduce it ? I don't see it.
It comes from gcc vector-index checks, so you may not see it.
Uwe Stöhr schreef:
I made progress with the multirow support, but there is one thing I
cannot figure out:
Where in the code are the cells merged when I e.g. select 2 cells and
press the multicolumn button? I a 2x2 table I have after this action
only 1 cell in the first row and 2 in the second
Pavel Sanda schreef:
Pavel Sanda wrote:
- Are there other missing features that you are working on and that you
want to have in LyX 1.7 before a beta release?
revision info under VCS is still in plan (fileformat change). but not
necessarily before beta, shouldn't be big change...
>I tried to compare the Intro from trunk and branch
>and got the following. Vincent?
Can you reproduce it ? I don't see it.
Are these by accident the same docs ? (The assertion is already there
before the algorithm is even started).
Maybe I should change "to.backwardPos()" to "step(to, Backwa
> - will Advanced F&R be in for this new release ? (I hope so)
Without a doubt. That's why we were slightly urging you to round up the loose
ends.
>- how does the release process work ? are you going to create
>a new branch on the repo, etc... ?
No trunk = new release.
Afterwards a new branch
>> What happens if you enter the following:
>>
>> inset-apply citation CommandInset citation LatexCommand citet key
"bla"
>> \end_inset
>>
>> And what if you enter the following:
>>
inset-insert citation CommandInset citation LatexCommand citet key "bla"
\end_inset
>
>In each case, entering this i
BH wrote:
>(I can't enter an lfun for selecting the "OK" button.)
>lyx -dbg action gives the following output when opening
>the insert citation dialog, adding a citation, and pressing "OK":
What happens if you enter the following:
inset-apply citation CommandInset citation LatexCommand citet key
>> This makes me think of the oddity that you can't open the outline
>> without a document etc.
>
>yes, also we have not nice hacks to get them displayed after start, cf
#5082 .
>
I was wondering about this. The new Progress View does get displayed
after start. The toc is only sometimes displa
1801 - 1900 of 3126 matches
Mail list logo
